Notes from #MetaBrainz Meeting on 2017-02-27

[Freso]

MetaBrainz Meeting 2017-02-27

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Resuming meeting notes
• Picard 2.0
• Schema change

Reviews

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

This week I worked on the two PRs I sent last week for getting them merged. And started work with one more migrating :P. Nothing much due to exams

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

reviewed picard PRs, did minor PW code fixing.
Exams, so busy IRL to code much

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’ve been keeping up with forums and IRC. I came home from Sweden late Wednesday and caught up on reported editor from the last few days. Just got a reply back from one of them, so their editing rights were reinstated.
I also published my outline for a small data-adding script earlier: GitHub - Freso/freedb2musicbrainz: Submit FreeDB data to MusicBrainz. Note: Project officially lives on GitLab. Don't expect sources here to be up to date.
Oh, and I posted something on the forums, but more on that shortly.

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

was mostly dealing with support this week
Especially a lot of issues about the BBC suddenly forcing people to enter their MusicBrainz ID, and not making clear what that is
(which, to be fair, neither do we, anywhere very obvious, probably because we never expected people to come specifically looking for their own without knowing what it is)
Other than that, I made a script for nikki’s bot and ran it to do the spotify URL change we talked about last week
I think that’s mostly done, there might be a few URLs left that we could probably just change by hand
And a couple URLs that shouldn’t exist in the first place, because they don’t have any rels
And I sent a couple more fixes and improvements for the editing-username code, which IIRC bitmap merged, so yay

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

I’ve not got much to report, still looking for hybrid instruments (if anyone knows of any, please link the MB instrument link in https://tickets.metabrainz.org/browse/STYLE-723)

@Yvanz

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Yvanz

It has been a very busy week IRL, so I did not have much time for MBS unfortunately.
My main occupation was to document myself and improve my dev environment.
Will have more time this week to contribute again.

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

I started off the week with a meeting with ruaok, for further understanding of MetaBrainz foundation, priorities and goals. I learned quite a bit about our ecosystem, how it is continuously growing and how this merges with our supporters of all sizes.
I began digging into learning about each of our products, although halted a bit while attempting to update the logo on the CAA website. This seemingly simple small update, lead to an education in wiki edits and a discussion about our wiki pages in general, of which I still have a lot to learn about. I will be continuing my education on our products this week.
I spent quite a bit of time untangling the saga of zvooq and attempting to try to make sense out of a very soap-opera-drama-esque business. I have attempted at fairly deep intelligence on the matter and am hoping this gives us a positive direction at recovering the funds they owe us, which would help us immensely.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

i continued hacking on piwik stuff, without much success. Our logs are fat
discussing with ruaok tonight about it, we’ll go for snapshots (processing only each 3 days)
so we can get a general view of web service
apart that, i did usual maintainance, PR reviews, and a bunch of MB edits
also i made it to BCN
Hope to meet you all soon

@alastairp

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@alastairp

last week I was in meetings all week, so didn’t do much
although I did a bit of hacking to try and get an API using GraphQL, and getting data from a database as a quick hack
seems to work really well. reosarevok pointed me at another implementation which just hits our ws. it could be interesting to get a proof of concept going to see
nice thing is it lets you specify exactly what fields/relationships you want returned in a request
other than that, I did a bit of code review for ruaok and some AB review
a bit of planning for SoC

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week I was battling a cold so things moved slower than usual.
I spent quite a bit of time working LB and getting the PR count down. some talking about LB and general philosophy on computer science with iliekcomputers.
some shit talking to SothoTalKer and the like.
also dealing with some contracts and sending out invoices.
and plotting the evil overthrow of our russian friends. Quesito writes a mean dossier!

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

This week I’ve mainly been tidying up and modernizing code in BookBrainz
Not particularly productive, but better to set good standards now than later on

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

been working on the sentry pr more
tried to remove some of the code we had to reimplement and integrate it better with Catalyst, which is still a pain
got it to include to contents of @_ for each stack frame in the reports
fully tested it in the release editor and got it to properly report errors there for stuff we care about, with correct stack trace context (i.e. from where the error occured, not the eval/catch block)
spent a bunch of time reviewing/testing prs too, since we’ve gotten quite a few from yvanz / Zastai lately

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I spent some more time figuring out how trigger generation code works in sir
wrote some documentation, done a bit of refactoring
also started planning how to implement better trigger functions/messages

Resuming meeting notes

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’m going to resume the weekly meeting notes soon. I’ve asked for feedback on how to approach it on the forum, to give y’all a chance to decide the path forward:
Resuming the #MetaBrainz Meeting notes
Please go vote/comment there.

Picard 2.0

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

so the dev. cycle for picard 1.4 is almost at its end with 1.4.1 PRs almost merged
for Picard 2.0 I had proposed a few tickets which can be found Development/Summer of Code/2017/Picard - MusicBrainz Wiki here
and Loading...
I basically wanted to decide a rough roadmap for how we should be progressing with 2.0
and set an order/priority on the above tasks
along with the direction we want picard 2.0 to go in

Some discussion followed, mostly about some specific patches. There were some suggestions for a Picard 2.0 roadmap, but mostly the discussion was about the proposed “api v2”. Since 2.0 has not “officially” started yet and the finishing touches are still being put on Picard 1.4.1, the conclusion was to put off making a roadmap for Picard 2.0 until 1.4.1 has been released.

Schema change

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso asked about whether it was time to think/talk about schema changes, as he felt “last minute schema change hacking often gives pretty chaotic results”. @Bitmap will look into the “schema change” component and report back next week.