Notes from #MetaBrainz Meeting 2017-04-10

[Freso]

MetaBrainz Meeting 2017-04-10

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• DR: MBS-9248: Don’t show the artist name in the tool-tip if it’s the same as the sort name
• Picard v2.0
• Picard comprehensive tags

Reviews

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

In the last week I handled some reported editors, poked a bit more at the KEXP (they seem to be behaving better now).
Kept up with forums and IRC.
Prepared to go to https://musicbrainz.org/event/1412f700-e9cf-452…
And then on Saturday I went to https://musicbrainz.org/event/1412f700-e9cf-452… and am here now.
Tonight I will have just given a talk about “metadata and MusicBrainz for musicians and music fans”, which I hope to inspire a couple more Danish (and maybe non-Danish) contributors. I guess we’ll see. (I know at least a couple of the people here are already MusicBrainz fans, so I’m not in the toughest crowd.)
(I also earlier today talked with a music manager that’s involved with the Irish Traditional Music Archive who will put me in touch with some people there who are about to start a metadata project of their own. We’ll see what (if anything) comes from that.)
I’ll be going “home” Friday (to Cph/Lund – ~1½ week then until I go home).

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I did support, mostly, and I’m currently finishing a draft of the new and very short feat. artists guideline
Once that’s done, I’ll write a blog post too, in case some other tagger makers or whoever want to know about the changes and adapt to them
(Picard is already there, thanks to samj1912)
Once that’s out, I’ll dedicate this week at looking properly at the events guideline discussion, and hopefully having a complete proposal for that by the end of the week
And Friday to Sunday I’ll be in Latvia waking up way too early to take nature photos at dawn, and seeing giraffes and stuff. And Spanish flamenco, because of course the main folk bar in Riga would have that the day I’m there

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

so this week I got a ton of work done (100+ commits), first off was the mega PR gh:P#664
apart from that, I updated the plugin endpoints on PW to allow it to serve plugins for various versions, specifically gh:PW#59
and gh:PP#79
and fixed other py3 porting bugs
proud to announce we have an almost working qt5/py3 port

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

well, a lot of code review, thanks to samj1912
we released first version of Picard 2.x, work in progress, but it works mostly
apart that, i did a bunch of security upgrades
plus working on goaccess webstats container, almost finished
and went a bit further with grafana alerts, enough to say it has some annoying limitations atm
plus a bunch of MB edits of course

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I fixed up & submitted MBS-8736 prerequisites by mwiencek · Pull Request #503 · metabrainz/musicbrainz-server · GitHub since it contains some work useful to extending last-modification date calc. to our main WS
the rest of the week I mostly worked on debugging unix socket issues and cleaning up Add a plugin to embed React components within TT by mwiencek · Pull Request #502 · metabrainz/musicbrainz-server · GitHub though tests are still failing
it renders the sidebar external links with react now too
seems stable so maybe it’ll go on beta this week after I fix tests
but this week I’ll be focusing on finishing up the schema change work now that that’s done

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I’ve done some changes in meb
mostly related to payment stuff

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was accounting and cleaning up invoices so that Quesito can help me with them.
then her and I met with loujine and discussed graphs and beautiful data.
aside from that I spent a lot of time on listenbrainz, chasing iliekcomputers around a lot to do my bidding.
the important thing he did was create a stress tester script that allows us to figure out where the scaling bottlenecks are.
I found one serious problem that would’ve really screwed us later. I got that fixed up and deployed today.
there are two other problems where things are slow, but they are not as pressing right this second.
as long as we address them in the next 6 months we should be fine.
I’m now setting my focus on getting things critical before a beta release done.
I also spent some time grooming our gsoc applications and the results are so far not terribly surprising.
the people who have been part of our community for a while submitted great proposals. those who wandered in in the last days before the deadline, less so.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

This week I worked on LB as always, specifically LB-125 and LB-147. LB-147 involved breaking the listenstore file into three parts, which was something I had wanted to do since some time.
Also, I wrote a script to stress test influxdb for the usage that we expect from it, but ruaok already mentioned that. Nice to see that it was helpful in finding bottlenecks
Not much else, I’ll probably be away this week mostly (a hackathon), but I think I’ll be sporadically online for sure.

@CatQuest

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@CatQuest

if I may have all your undivided attention for a second:
for the first time in… a very, very long time, we now have more closed INST tickets than open ones!! Instrument Requests - MetaBrainz Tickets
jippi!
this week is easter, and I will be taking a well deserved break! \o/

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

last week I got to talk lots of data visualization with loujine
welcomed a bronze supporter!
and then started the long and winding road of invoicing and accounting with ruaok
I am trying to implement a fixed quarterly billing cycle that follows the fiscal calendar. We’ve begun, and by reaching out to our supporters we’ve gotten some good and interesting feedback.
Thus far I’m at 50% up to speed…so still more work to be done
other notes–need to get back into web verbiage–it’s getting close
and if anyone want to vote on ORG-10 please voice your opinions!!! thank you CatQuest for yours!

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

I took a look at GSoC proposals and had some discussions with LordSputnik. I also played fiddle a lot.

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

I worked on code to create CB database using raw sql so that the ORM models are not used for creating databases.
CB-230: Create database without using ORM models by ferbncode · Pull Request #96 · metabrainz/critiquebrainz · GitHub
was busy in organization of some events in the Technical Fest of our college.

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week, I mostly worked on entity attributes, should be up for code review within this week. I wish we would get it live on test.musicbrainz.org during next week.

@loujin

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@loujin

after discussing with ruaok and Quesito I continued working on data visualizations with MB data
but didn’t do much
played a bit with d3js + python over the weekend
hope to show you something soon

@Sophist

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Sophist

Stopped work on the UI responsiveness PR - and will pick it up again on Py3 when I get the time.
A couple of PRs to provide iTunes Movement tags support - 1 for master 1 for 1.4.x
A couple of tiny bugs fixed.

DR: MBS-9248: Don’t show the artist name in the tool-tip if it’s the same as the sort name

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok made a PR for this ticket a while ago, which @chirlu voiced dislike of.

There was agreement on rejecting the current PR and continuing discussion on how to handle the issue on the ticket.

Picard v2.0

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

I wanted to ask the direction we want to take with picard v2 and wrt to plugins, as I have mentioned earlier, I would like for picard to be more modular and move more things to plugins and introduce more plugin hooks along with having officially maintained plugins

There was some discussion about which plugin hooks might be needed and pros and cons of moving current core functionality to plugins. Slightly/briefly touching on “official plugins”.

In the end, it was decided that people invested in this should think about it some more and make some more concrete plans which can be reviewed and discussed at a further meeting. As @reosarevok said: «let’s talk about it further with a more clear idea on the table».

Picard comprehensive tags

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Sophist is asking about whether we want Picard to support more tags that might be specific to one or more formats (ie., not something like “Artist” that’s universal).

There were objections to introducing new/obscure formats that would increase the number of dependencies for Picard, but @Sophist assured that his idea is only about extended tag support for already supported formats.

In the end, it was generally agreed that it was something we wanted and @Sophist is free to pursue this.