Notes from #MetaBrainz Meeting 2018-08-13

[Freso]

MetaBrainz Meeting 2018-08-13

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Song of the week (“The weather here suggests we’re having a bit of a”):

New Order - Blue Monday

Agenda

• Reviews
• Membranophone discussion outcome

Reviews

@CatQuest

https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/4235110/

@CatQuest

I said quite a bit last week about what i was gonig to do
so
This week I’ve given @chhavi feedback, I had a meeting with @freso and @reosarevok ang the drums and I finished the last GCI related instrument ticket! yay!
Therefore I’ve also released the gci version!
Now I’m working on OTHER-327 , there are 2 blogposts that will eventually be added also I’m really sorry it’s taken this long, but well, stuff happened™
also, I seem to be uhh. still ill so I feel pretty crummy :C
//hopefully/// (omg) I’ll get properly better this week!

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

This week I did the drum talk and otherwise enjoyed the slightly better wetter weather.
Dealt with support, edited, and went cycling and camping to disconnect a bit

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I was generally catching up on things and being around and about.
Reading lots and lots of spam, following Freenode’s discussion about the situation too (not much is new).
Reviewed GSoC blog posts and added GSoC students to the blog so they could post them.
Talked with @CatQuest and @reosarevok about instruments (if you hadn’t got that one yet :)).
Oh, I also got an e-mail from Google.
As GCI org. admin I can send one GCI mentor to the GSoC mentor summit. See the Hangout for more information.

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

just traveling, fixing mum’s house, BBQs in the bay area and just a modicum of actual work this week.
but, the work that was done was pretty cool.
we signed both QNAP and Microsoft as unicorns in the past week.
which is a pretty big deal in the grand scheme of things. QNAP took almost a year to land, but we finally did it.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

Last week, I started going to the library for set amounts of time to work on MeB things

But then, I got stuck on a few things
I’m working on two things rn, setting up spark for LB and moving AB to hetzner
Hit blocks on both of them, but I think I’ve got enough now to move forward.
Other than that
I’m sitting in my aunts house in delhi
Applying for the visa for the gsoc mentor summit
Interview tomorrow, I have loads of documentation, let’s see what happens.
(oh and I reviewed @little_rsh PRs and work product post

@Bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Bitmap

spent more time futzing with react, finally managed to submit a pr for the artist merge forms and finished support for html in translated strings
looked more at @chhavi’s work and merged some this morning
probably more of the same this week

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week, I pushed a new beta for MusicBrainz Server (with small bugfixes and templates converion to React mostly) to be released on tomorrow.
I pushed another beta for MusicBrainz Slave Server Virtual Machine, final version (with old search server still) to be released on tomorrow too.
Plus usual stuff

@little_rsh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@little_rsh

This week, I’ve opened a PR for evaluating both the MB database access methods (AB-357).
Right now, I have completed the GSoC project work from my side and 2 PRs are left for review.
I am planning to work on more integrations of AB with MB after gsoc.
So, last IRC meeting before GSoC ends.
Thank you @iliekcomputers and MeB team for the help and support throughout the gsoc program. Looking forward to work with you all again
I am still gonna work on AB and looking forward to work on other projects as well.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

Usual stuff, pr reviews, editing, Picard release

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

Last week I finalized the SpamBrainz model and wrote a Jupyter Notebook to evaluate it’s accuracy on data it hasn’t been trained on and I’m happy to say that it is 99.9% accurate in identifying spam editors while only misidentifying 0.2% of real editors as spammers!
I’ve also been working on my GSoC blog post which I’m a bit anxious about after seeing the great two ones that already went up.

@shivamt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@shivamt

This week I finished off most of the code on the bookbrainz site and related chunks on bookbrainz data
I am completing finishing off the blog post, which I will hopefully be able to get reviewed tonight

@kartikeyaSh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@kartikeyaSh

This week I created PRs for LB-385, LB-356, and LB-388 and worked on reviews of LB-381 and LB-382.
I did write GSoC 2018: A way to associate listens with MBIDs – MetaBrainz Blog for the GSoC final submission. And completed the final evaluation.

Membranophone discussion outcome

https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/4235287/

@reosarevok

Basically, everyone’s been using the wrong “drums” for years
So, we have a huge mess
@CatQuest recently changed our drumset instrument to actually say “drums (drum set)”, in hopes people will actually select it when they mean that
But all of our existing “drums” credits are stuck in the old instrument called “membranophone” now, which is confusing people, because wtf is this membranophone some famous drummer plays and whatnot
So @Freso will write some bot stuff to change the instrument in those rels to either drumset (and the few wrong ones that were meant as some generic bunch of drums will need to be moved) or drum[s], generic (and then the drum set ones can be moved to the specific instrument by people who know for sure)
We’re planning to ask the community which one they’d prefer with some poll, and then let FresoBot deal with it, maybe even slowly enough that people can review them and see if they make sense, but we’ll see
Anyway, we’re hoping to make most of those odd membranophones disappear