#MetaBrainz Meeting 2018-05-21
Worked on summit artwork with invat (yeah, I know it’s too early, but was excited to get started). A bit on setting up the design system, not as much as I would have liked though. Looking forward to catch up this week.
This one was a rough one (got sick and family mishaps).
As expected, I didn’t get much done this week, however it was mostly due to a sudden elevation of temperature!
To our esteemed indian colleagues it is probably not much, but if you consider that a mere month-and-a-half ago there was snow on the ground with minus 5˚, a plus 28˚ is indeed a lot! (in july one would be more used to something like this temperature :D)
However, I did mange to do some fixing of gong and gongs (merge the latter into the former)
Edited a few releases, added a ticket for suggestion of a new report: MBS-9712
Considering splitting up our “mbira” instrument which makes sense since we differentiate between very similar other instruments, but this will be an undertaking, as it will require reorganising a lot of different wikidata pages as well, anyone who knows anything about all lamellophones like mbiras, likembes, kalimbas, sansas and the ilk are welcome to talk about this! Please make some INST tickets with different “thumb piano” instruments that are your pet thing. (yes, people reading the community “Notes from” posts, this means you!)
see INST-647 for the accompanying ticket!
This week I worked on schema related work for imports
It has been reviewed and I am working on the changes
I worked on functional query based methods to access the methods
Had a discussion in my weekly meeting with @LordSputnik regarding bb-data interface for this setup
I am a bit behind my schedule for this week, trying to catch up.
This week I worked on direct connection scripts for artist and release entity and opened the PRs in BU.
I also added the test script for helper function.
And a separate MB direct connection setup PR in AB.
Updated the AB documentation for setting up MusicBrainz server in AB.
and worked on removing caching from release, artist and recording entity in BU.
I started working on the website and management part of SpamBrainz, helped
@samj1912 testing and tweaking newsearch (which works extremely well already).
I’ve also been looking into data science stuff to run on the spam data, I’ll probably end up making a couple jupyter notebooks (and hopefully a bunch of cool graphs).
Oh and I also found a great location for our 2019 summit
the time has finally come to say
…its time to remove the probation from the KEXP editors
they’ve stop forcing all their volunteers to edit
those were the really crappy ones because when you’re forced to do something you don’t care
so we are left with 3-4 kexp editors, but they were the best, they actually care about the database and take suggestions are involved etc
so i’m officially lifting my probation i had on them, they don’t require watching anymore
[ @Freso: Thanks for all your work and time dealing with them.]
no worries…someone had to do it
and because i’m a masochist, i’ve started another SXSW festival…yikes!
and i hope most/all of you had a chance to read the mentorship doc
A bit of talk back and forth and some suggestions about the .
@chhavi suggested looking at the GSoC mentor/mentee expectations.
@drsaunde asked for potential mentors to step up.
There were some discussion about working together, with GCI being brought up as a comparison.
@Freso noted that GCI’s time sensitivity does not really apply to the proposed mentorship program. Obviously, mentors will be free to ask for advice about something from other mentors, and even community members outside the program, but likely no need to organise in the same way that GCI is.
@drsaunde will revise his proposal and include some initial mentors and return with more updates later.
There was widespread consensus that 3. is the way to go, even if it will take a bit longer and be more cumbersome to implement initially.
@Rob noted that «this isn’t the critical path for GDPR, so it is fine to let it run out a bit. as long as we stay on it.»