Notes from #MetaBrainz Meeting 2017-03-20

[Freso]

MetaBrainz Meeting 2017-03-20

Meeting start: Making sure you're not a bot!

Agenda

• Reviews
• DR: MBS-7133: Diacritics shouldn’t be an auto-edit
• DR: MBS-7108: Editing Medium tracknumbers shouldn’t be an auto-edit
• Picard feat. plugin

Reviews

@samj1912

Making sure you're not a bot!

@samj1912

Nothing much to report this week, did PR reviews and just submitted my Gsoc proposal draft. Was out most of the week for vacation.

@Freso

Making sure you're not a bot!

@Freso

I facilitated a Google Code-in mail and apart from that mostly kept up with IRC and forums.
I came to Sweden on Tuesday and also got my passport renewed on Tuesday. Should be able to pick up my new passport this week.
I’ve spent a fair amount of time this week working on the slides, and my presentation in general, for my talk at Open Source Days this just-past Saturday.
And then I spent this just-past Saturday at Open Source Days in Copenhagen, giving a talk.
I’m trying to get a link to the slides on Google Drive right now, but it’s being slow.
Open data on my Brainz.odp - Google Präsentationen
I will add it to the Presentations WikiPage later.

@ApeKattQuest_MonkeyPython

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

I asked and was told that it’s ok for me to create “Fix Versions” so now I can group instrument tickets into batches. This will let me group things and set aside the “hard” ones from the “easy” ones so I can get those done faster and hopefully whittle down the list of tickets so only the actual difficult DR ones remain.
also creating “do all these in this group” groups which are decidedly smaller than the entire list helps things from feeling too overwhelming.
So if you’ve got a INST ticket that’s _straightforward_ and important to you, you can put Fix Version as “next” on it (I reserve the right to alter it, of course :D)
also if Instrument families and variants interest you: Instrument Family and Variants Discussion

@yvanzo

Making sure you're not a bot!

@yvanzo

I started with grasping a variety of MeB accounts and tools.
Then, I mainly worked on extending dynamic attributes for the next schema change.
I also made auto-edit issues archaeology and implemented MBS-8134.
On @reosarevok’s request, I coded a small enhancement with a bugfix to change artist credits in the relationship editor.

@reosarevok

Making sure you're not a bot!

@reosarevok

mostly dealt with even more MBID questions
hopes the BBC makes that clearer on their side soon
Other than that, I’m right now answering [STYLE-747] Event guidelines and hoping to get some proper discussion on events up with that
That’s about it I’d say, other than just editing

@ferbncode

Making sure you're not a bot!

@ferbncode

nothing much..opened a quite big PR for migrating reviews off ORM. Part of CB-230.also, working on more migration
I am trying something with the docker setup for the musicbrainz database. hope to get something basic done

@Quesito

Making sure you're not a bot!

@Quesito

Mostly verbiage work on the MeB site last week for me. I’ll be needing some help this week, as far as other eyes reading/editing/commenting.
I’ve come up with a general workflow of verbiage edits for the project pages (upcoming), mostly to be time efficient for the developers involved.
More learning of the ins and outs of jira, which will also continue this week. Worked a bit with Leo_Verto on the MB user survey, in hope we get some really good feedback.
Chatted with iliekcomputers about his gsoc proposal, but I didn’t explain my idea very clearly at the time–so I quickly gathered my thoughts together and posted it to the forum.
So far that’s crickets, but I’m holding out hope for some feedback.
And I’m continuing trying to open up my workflow to make it more transparent

@Leo_Verto

Making sure you're not a bot!

@Leo_Verto

I spent the last week continuing working on Botbot and took up work on the survey again (thanks CatQuest and Quesito)
I spent the last few days doing IRL stuff after getting home again but will continue what I started this week

@Gentlecat

Making sure you're not a bot!

@Gentlecat

I finished implementing trigger generation for SIR. Just need to test them now.
tested imports in listenbrainz and opened some tickets related to that
and reviewed some things, as usual

@bitmap

Making sure you're not a bot!

@bitmap

mostly worked on the alternative releases/tracklists UI
still a lot to do there, actually
also fixed some issues I saw with sentry in production, and that dreaded release editor bug that submits stub releases

@alastairp

Making sure you're not a bot!

@alastairp

PRs this week
finally getting on top of stuff from SoC students, only 1 more to look at seriously
we’ve had some good submissions, but no movement on proposal drafts yet
they open this week I think, so hopefully we can start some discussion on that

@iliekcomputers

Making sure you're not a bot!

@iliekcomputers

I worked on a couple bugs for lb this werk
Also discussed about visualizations in MeB with Quesito , will have more on that later

@zas

Making sure you're not a bot!

@zas

not much to say, usual stuff on Picard PRs, lazy hacking on Piwik mess, listenbrainz/ruaok debugging, and usual server maintainance

DR: MBS-7133: Diacritics shouldn’t be an auto-edit

Making sure you're not a bot!

There was wide consensus that editing diacritics should be autoedits, so the ticket was decided to be “won’t fix”.

DR: MBS-7108: Editing Medium tracknumbers shouldn’t be an auto-edit

Making sure you're not a bot!

There was also wide consensus for marking this ticket as “won’t fix”.

Picard feat. plugin

Making sure you're not a bot!

@reosarevok

So. The only thing between me and a “let’s no longer standardise “ft.” and whatnot to “feat.”” guideline change is the lack of a Picard plugin to re-standardise it for people who want that
I probably could learn to write Picard plugins since it sounds like an easy one, but tbh I have a huge amount of things to do as it is, so it’d be very nice if someone else volunteered

There was some talk and some people tentatively maybe volunteered. It was decided to look at it again next week to see if someone had gotten around to doing the plugin.

[Freso]

Thanks to @ApeKattQuest_MonkeyPython for providing missing chatlogs and @Leo_Verto for fixing up the chatlogs after some IRC netsplitting during the meeting!