Notes from #MetaBrainz meeting 2017-11-20

[Freso]

MetaBrainz Meeting 2017-11-20

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

Agenda

• Reviews
• Design tickets
• INST-330: Rename “guitars” instrument

Reviews

@Freso

Making sure you're not a bot!

@Freso

The last week I reported a couple of MBS issues, I looked a slight bit into some WordPress stuff with jwf.
I also did some GCI stuff and lurked around on IRC and forums.

@iliekcomputers

Making sure you're not a bot!

@iliekcomputers

this was a pretty productive week for me.
Working on data dumps for both AB and LB
Opened a PR that should make it easier to have test dumps for dev environments in AB
AB-314: Add support for maximum number of recordings in one file for lowlevel json dumps by paramsingh · Pull Request #241 · metabrainz/acousticbrainz-server · GitHub
Then, worked with ruaok on data dumps in LB, addressing code reviews and making changes accordingly
2-3 big PRs about that
Also, worked with jwf on his PRs (thanks!)
then, added a few LB GCI tasks
more to come

@jflory

Making sure you're not a bot!

@jflory

So, three things from me:

1. New-ish blog post from me about things I’ve been up to: https://blog.justinwflory.com/2017/11/listenbra…
2. My next goals are to look more at the statistics side of LB. I’ve been playing around with one statistic to try and understand how they’re composed, but it needs me to do research with the database structure of LB.
   https://github.com/jflory7/listenbrainz-server/commit/a543d6110fd0e3dfedfbc52011495cbbbe616aae
   Once I get an idea of writing one statistic, I want to write a proposal to evaluate what statistics are helpful to collect and then try to create a development plan around those statistics (feedback will be very welcome in this process).
3. Continuing to work with Freso on new LB posts for the blog too. I have one that I think is ready, but need to look again this week. I also have the LB development environment how-to on the blog, so we can publish that there too.

@reosarevok

Making sure you're not a bot!

@reosarevok

I did https://tickets.metabrainz.org/browse/STYLE-856 and sent a PR for https://tickets.metabrainz.org/browse/STYLE-854
(the cover art style is very basic stuff on Style/Release, nothing specific about cover art sizes or anything)
I also set a couple more tickets as depending on https://tickets.metabrainz.org/browse/MBS-3993 which probably means won’t happen in ages but eh, a human can dream
Other than that, support, a lot of editing
Oh and the poll on Planning for Community Cleanup #3 (with poll!) is still open, last few days to comment on it!
Well, vote
Might be the last composer in a bit, I’m half-tempted to go with a label for the next one (either New World Records if loujine is ready with his part of that, or something like Chandos, Hyperion or the like with full booklets online)
But let’s see what people think about that after this one

@ApeKattQuest_MonkeyPython

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

Still working on gci tasks.
fixing the long wrong “Rock Furore” release (notifinished)
leaving a hecka long feedback on the artist-redesign ticket (eh sorry everyone?)

@chhavi

Making sure you're not a bot!

@chhavi

This week, after the discussion we had on Artist Overview page, I updated the mockups. More like redo it, since we are now making it more overview-y.
We have had some amazing feedback so far. Especially CatQuest yvanzo zas and few other MB community members
I also wrote a blog explaining our entities in simplest way possible. It’s a narrative by a singer version of me in an alternate reality
Here is the link:
https://medium.com/@chhavi.justme/beginners-guide-to-music-metadata-part-1-2afd514faa04
Apart from that I set up a MusicBrainz Server for front-end development with help of samj1912 and bitmap . They were both very patient.
At one time I might or might not have asked, “okay so how do I open my text editor?”

@samj1912

Making sure you're not a bot!

@samj1912

most of this week, I was busy with IRL stuff, end sem times and all
managed to sneak in a few hours to finally get Fix live indexing selections by sambhav · Pull Request #55 · metabrainz/sir · GitHub merged
nothing much apart from that
we are trying to come up with a better way to represent paths since this seems to be clearly getting out of hand
and I really want to find time to discuss the search schema
helped chhavi_ with her MBS install

@bitmap

Making sure you're not a bot!

@bitmap

I made some improvements to the caa-indexer’s error handling and logging, which hopefully means it will crash less (and have more useful messages when it does), but we shall see
I also finally finished MBS-8736 just need to submit the PR. it generates a 116MB dump currently and contains examples of pretty much every entity/relationship type
other than that I mostly spent time looking at stuff in the sir spectrum and helped chhavi_ with mbs setup
feeling better now so looking forward to being more productive again

@zas

Making sure you're not a bot!

@zas

merged a bunch of Picard website pending PRs
deployed security upgrades on all servers
worked on the backup system, but i was too busy IRL this week to finish
supervised various issues: we have to control the size of logs on our docker containers
spike is having disk problems, alastairp/ruaok/me aware of it, and on it
i added nagios alerts for bookbrainz

@yvanzo

Making sure you're not a bot!

@yvanzo

not a productive week half fighting against code again, half sick, period.

@Leo_Verto

Making sure you're not a bot!

@Leo_Verto

Last week I finished and merged a new plugin for BrainzBot: An improved brain plugin which is obviously called metabrain.
There are four new commands you can use:

1. !remember <thing> = <other thing> - Save something in the bot memory
2. !recall <thing> - Make the bot print “other thing”
3. !forget <thing> - Remove “thing” from the bot’s memory
4. !braindump - List everything currently in the bot’s memory

The plugin is also enabled in both #meb and #mb but if you just want to try it out, feel free to play around in brainzbot after the meeting
Also thanks to samj1912 for reviewing all the relevant PR even though he had a super busy week!

@Rob

Making sure you're not a bot!

@Rob

last week was the same as the few previous.
more drama fallout, speaking to attorneys, board and other soul sucking crap like that.
a couple of conference calls with potential supporters and random emails.
and not enough LB PRs reviewed, let alone deploying stuff into a new beta. this week isn’t looking to be too much better either.

Design tickets

Making sure you're not a bot!

@Chhavi

This week, it’s just one ticket.
https://tickets.metabrainz.org/browse/MBS-9536
Based on feedback, we are trying to make the overview page, an actual overview. We are still figuring it out. Feedback is welcome
Note: People joining the discussion now, can jump to read comments from my ticket headlined ROUND-2.

INST-330: Rename “guitars” instrument

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

ok so, https://tickets.metabrainz.org/browse/INST-330 is kinda blocked right now.
Well, inasmuch as we’d need to move all the all uses somewhere else before we can merge/remove it.
Do people think it is ok to move these all to guitar and if so, can we make a bot for it?

@reosarevok

I think that the amount of uses that are “an unspecified instrument of the guitar family”, rather than just “multiple guitars”, is probably small enough to be negligible in a bot move
But of course, it’s hard to prove this
Other than by checking them all by hand, which yeah no
Since the bot should make edits, if someone has used it right they will probably notice it in their subscriptions and shout to us about it

An informal vote was had with 4½ votes for (incl. both STYLE and INST leads), ½ a neutral vote, and 0 votes against, with the caveat that the bot should make sure that moved guitars should keep an “instrument credit” of ‘guitars’ and that guitars that already have an instrument credit should not be touched by the bot at all.

[Kid_Devine]

@Freso

the bot should make sure that moved guitars should keep an “instrument credit” of ‘guitars’ and that guitars that already have an instrument credit should not be touched by the bot at all.

So “guitars” has been renamed to “guitar family”, but where’s the bot?

[ApeKattQuest_MonkeyPython]

Thinking forward, it’d be useful for me to ally myself with someone with a bot, who could do these sort of things when asked (also thinking about the drums vs drumset conundrum) which would (maybe?) help alleviate some problems for people that I unintentionally might create while reordering and fixing instruments…