#metabrainz

"""

is all the update I have for last week.

"""

(«Quesito conflict update»)

(Quesito has a document with the communications between them, which I will make public if ruaok gives his 👍, so people can make up their own minds, rather than just getting ruaok's side.)

And still no word from ListMyCDs or anyone else that they're up for reviews.

So.

Freso: AcoustID on forums!

As said before, I've reached out to luks: https://groups.google.com/forum/?fromgroups=#!t...

And he said «This mailing list is not a good place for discussions, so I'd be happy to use the MB Discourse as the "official" forum.»

So if no one has any objections, I would like to make an "AcoustID" category on the forums in addition to our current acoustid tag.

+1/-1 ?

+1

+1

+1

+1

+1

+1

(Since we get a fair amount of AcoustID questions on the forums, and having its own category would make it easier for people to note that it's a separate project to *Brainz and we could make a category description that notes that it's now a Brainz project etc.)

Seems like we have a consensus then. :)

Thanks!

it is a brainz project now?

Just make it clear it is not an MeB project.

samj1912: Search schema and output

CatQuest: It's not.

yvanzo: Yep.

"we could make a category description that notes that it's now a Brainz project etc.)"

s/now/not/

aha

Just a short topic (i was hoping rob would be here today)

samj1912: We can do it next week if that'd be better?

yes

Alright.

just as an aside, LB reached a 1000 users and 60M listens last week :)

Freso: Google Code-in

iliekcomputers: :D

iliekcomputers: \o/

🙌 🎉

So.

Yay iliekcomputers

https://wiki.musicbrainz.org/Google_Code-in/201... still has a lot of room for more task suggestions.

And tomorrow is the last day for org. applications, which means they may start looking at task suggestion pages tomorrow.

where would I put a "create an instrument ticket" task?

So we should really get as many new tasks on the page as possible in the next 24 hours.

or a "take a picture of an instrument that doesnt have a picture already in commons"

(though that maybe too wikipedia org )

CatQuest: Put them under MusicBrainz. :)

alright :)

Also, any one who thinks about being a mentor that are not already listed at https://wiki.musicbrainz.org/Google_Code-in/201... please let me know!

And if anyone's listed at https://wiki.musicbrainz.org/Google_Code-in/201... and haven't been added to the 2017 mentor hangout, also let me know!

Change the redesigned footer for musicbrainz?

^this works?

is something that inwoles wikicommons an acceptable task?

chhavi_: All suggestions work!

IMO yes if it's MB usable

We can filter the suggestions when we actually move them to the GCI system.

can i add spesific "edit/create" musicbrainz releases type tasks too?

Freso: ferbncode isn't added to the mentor hangout, I think

ferbncode: Please e-mail your Google login to freso@meb :)

Freso: Does “Give some love to the data of your favorite artist” stand for an acceptable task too?

Freso: sure, on it

yvanzo: Sure. :)

+1 yvanzo

but uh, maybe define "love" o it can get weird

:D

yvanzo: I mean, it wouldn't be a good task in actual GCI, but it's a fine suggestion for further fleshing out.

I will try and get some more task suggestions based on previous years added tomorrow (european) morning too.

Any other questions/thoughts/suggestions?

If not, let's call it a night!

I guess we'll do that.

Thanks for your time everyone!

</BANG>

Thanks Freso !

thanks Freso

Thank you Freso :D

bitmap: Can you just check MBS-9519 description? I'd like to complete tests and merge it in next beta as well.

MBS-9519: Hide biography, homepage, and collections description of limiter users from not-logged-in users https://tickets.metabrainz.org/browse/MBS-9519

yeah, was looking right now actually

chhavi_: Sorry I haven't been around over the weekend. :)

We're currently having a friend over for his birthday, but I should be more available tomorrow (my/european) morning. :)

yvanzo: the ticket description looks 👍

looking at the PR now

Thank you, I was a bit dubious because it basically reverts the two previous tickets.

Freso: No problem. Happy to let your "head" be free for a while :)

yvanzo: actually, I did not consider allowing limited users to edit things again, but I'm not against it either

though there is a contradiction if it's only hidden for limited accounts and they can't edit things anyway

so yeah, I guess that makes sense :)

I know you initially suggested the opposite and I am among those who suggested to do it.

(to do it = to allow it again)

[acousticbrainz-server] alastair closed pull request #237: Fix docstring of data dump function (master...docs-fix) https://git.io/vd17f

Well, the worst that can happen is that we will set up a neat honeypot. :)

I think it would be nice to allow limited users to edit their info at some point.

Since we want proper users to write a bit about themselves.

And they're more likely to do that right after making their account than after 2 weeks.

[picard] samj1912 closed pull request #785: PICARD-1143: Prevent loading .smbdelete* files (master...picard-1143_always-hide-.smbdelete-files) https://git.io/vd4MU

(Or maybe the UI could nudge them to completely their profile once they become non-limited? (chhavi_-ping) E.g., an e-mail which could also say something like "Congratulations! Since you've been around for a bit, have made your first few accepted edits, … your limited account is now a full user account - welcome (again)!")

(Which could also say something like "If you didn't come across it already, be sure to also check out our IRC channels, forums, and blog.")

yvanzo's PR let's them edit their info right away, as long as they have a confirmed email :)

their website and bio will be hidden from not-logged-in users, until they are no longer limited

I actually do that kind of positive confirmation mail thing.

I should make a ticket about that.

*do like

Freso: is it alright to have a Q/A task to categorise say 10 tickets in JIRA into respective components/ do a clean up

samj1912: I... don't know?

Maybe ask in #gsoc ?

hmmm

(Which is also the official GCI IRC channel.)

samj1912: You can put it as a suggestion anyway and we can just not port it over when the time comes.

cool

ferbncode: iliekcomputers: I was just reading your comments about pxz/python zipfile support

<Freso> (Or maybe the UI could nudge them to completely their profile once they become non-limited? ... Or perhaps allow them to edit their profile right away, but not make it public until they become non-limited?

Freso: https://wiki.musicbrainz.org/Google_Code-in/201... not sure if that makes sense

just so you know, are you aware that we're specifically using pxz because it's parallel (uses multiple cores)? - to compress dumps faster

metabrainz/picard#2839 (master - c2f2282 : Sambhav Kothari): The build passed.

Change view : https://github.com/metabrainz/picard/compare/5c...

Build details : https://travis-ci.org/metabrainz/picard/builds/...

Oops, I didn't read bitmap's comment about yvanzo's PR. Looks like it's already in the works. Sorry about that.

Freso: reosarevok can you link me to the presentations page on wiki?

https://wiki.musicbrainz.org/Presentations :p

nvm got it :P

alastairp: ah, okay.

bitmap: in MB, are schema changes to non-replicated tables only done at schema-change time, or are you free to make these changes whenever you want?

I'm thinking about dumps/backups of non-replicated tables, do you include the public schema sequence numbers in these files?

we occasionally do those whenever if they don't break standalone servers either

bitmap: when you have time , please take a look at https://github.com/metabrainz/sir/pulls

alastairp: I believe we always include a REPLICATION_SEQUENCE file in every dump, regardless of whether any of the tables in it are replicated

samj1912: I have them open already :)

hehe :P

right; I'm thinking about how we can do these in AB - I suspect our private tables are going to have much more schema changes than the public ones, so I'm wondering if we could have two separate schema numbers

though, your comment about standalone servers reminds me that we also have to work out how to handle the upgrade process for our standalone servers too

ah, I meant SCHEMA_SEQUENCE. though we always include that too