Notes from #MetaBrainz meeting 2018-03-19

[Freso]

MetaBrainz Meeting 2018-03-19

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Summit dates
• ListenBrainz user survey
• DST notice

Reviews

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

We released a new version of LB this week
Had to fix a couple bugs for that
Anyways, now was planning to move forward to newer features, but we came across a bug in our data
That i plan to start on today
Other than that
We have started regularly releasing CB dumps again
Check it out on the MusicBrainz FTP
Thanks @ferbncode for the help on that!
And I worked on a page on MeB.org listing all our data dumps
discussed gsoc proposals for AB and LB and CB a bit too

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

This week, I sent in CB-283: Add support for dumping and importing rating tables by ferbncode · Pull Request #192 · metabrainz/critiquebrainz · GitHub to add avg_ratings table and the rating column in revision to the dumps. Thanks to iliekcomputers for fixing the cron job in prod. Also, sample-musicbrainz dumps (mbdump-sample.tar.xz) can also be used with the review dumps with no errors.

@alastairp

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@alastairp

I’ve been moving towards doing some AB PRs in a roundabout way
made a suggestion to uditgulati0[m] on an LB PR for the same issue (user menu on error pages)
and on the way I made a handful of other small bugfixes to LB
now I’ll pass the AB version of this task back to rsh7
as ruaok mentioned a few days ago, I have a working spotify importer for LB
just polishing some edges and I’ll submit that

@kartikeyaSh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@kartikeyaSh

I worked on my initial draft of the proposal and posted it. Got a few reviews from ruaok. And will work on them asap

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

This week, worked on the second version of Release Group page. Going smooth and nice there!
Apart from that, helped ruaok a bit writing a blog about our redesign
Our next major challenge: Fixing the MusicBrainz site design for an improved user experience – MetaBrainz Blog
Also looked into LB graphs, which we plan to discuss this week. Created a short user survey to see what our users will like to see.
How do you Listen?
My laptop is acting up, so I plan to give it for repairs tomorrow. Hopefully, the issue isn’t big and doesn’t affect much work.

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

Worked on picard bugs, planned beta 2 release with zas, reviewed picard PRs, cleaned up pending jira tickets for picard, reviewed lots of bitmap’s mbs PRs, worked on my own MBS prs, patched an upstream mbs dep.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

Usual server maintenance, i upgraded influxdb & grafana (v5)
Picard PRs & fixes (beta 2 soon)

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

Support. Another wave of people who need their IDs, for whatever reason
(not sure why they come in waves but eh)
Other than that, nobody complained too much at the stuff I shared last week about instrument groupings / ensembles so I’ll add that in a bit I think
And we need to officially close the hyperion cleanup soonish, and I should write a post, but I’m waiting a bit in case loujine finds time to throw some visualizations at me
Well, the tools are going to stay there and are still useful

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I did some reviewing or ruaok’s PR to move our policy documents from MB wiki to MeB.org as well as bring them up to date a bit. (They look good to me now, for anyone wondering.)
I also had a report about a feature missing from our Discourse instance that apparently “every other Discourse” install has. Turns out that it is “as intended” since we have Discourse’s internal messaging disabled, due to not wanting a lot of different ways to do this.
https://tickets.metabrainz.org/browse/MBS-8721 is the relevant ticket.
I also found out that apparently IA’s Wayback Machine doesn’t properly archive forum topics, so I also looked into this. Seems like it’s a bug on IA’s, but no known way of letting them know where they seem to be responsive.
I also added otter71 to the Auto-Editors group on the forums, per their request.
And talked a bit with ruaok about the EU “right to be forgotten”, resulting in him posting on the forums:
MusicBrainz and the "right to be forgotten" - #6 by rob
Other than that, IRC and forums pretty much.
Note: next week I’ll be volunteering at a folk music camp, so I will likely not be around for meeting.

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

most of what I did has already been reported on, I feel.
I did however cause massive travel chaos in our little group for meeting up in india.
I’ll try to actually make it india tomorrow.
later this week, thursday and friday, @ferbncode, @iliekcomputers, @chhavi and I will meet in Delhi and chat about LB, graphs for LB and recommendation engines and the like.
and we also had the kick off meeting with the consultant who will review our organization’s hiring process and conflict resolution.

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Discussed the project SpamBrainz with 3 potential GSoC applicants, whereas many other GSoC task ideas for MusicBrainz have not been discussed at all.
Worked mainly on debugging the MB WS memory usage issue which sometimes happens (like right now) and reviewing PRs.
(Addendum: The issue is we won’t be able to mentor more than 1 GSoC student for SpamBrainz.)

@vishichoudhary

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@vishichoudhary

this week i worked on issue PICARD-1226
and now working on PICARD-1228
but got some reviews on my proposal
and now updating that proposal.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I mostly did code review and fixed my react prs
tested the search results one more and fixed several bugs I found in it
it’s super easy to introduce 20 new bugs in every conversion, so I’m trying to test everything more, which slows down the process a bit
worked on adding types to our most oft-used components and functions (EntityLink/i18n stuff) to avoid more bugs creeping in. opened a PR for EntityLink
cleaned up my sidebar conversion branch more, I just need another day to split up a large commit and then I’ll push

@mastcoder

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@mastcoder

In this week most of my time got consumed in the second draft of GSoC proposal.
Thanks to @LordSputnik for reviewing and merging my pull requests.
I have pushed all the changes as needed.
Currently, I am working on adding more stats tables on statistics page of BookBrainz website.

@shivamt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@shivamt

Ok, so this week I started off working on some userscripts.
Then I wrote my proposal
GSoC 2018: Importing data into BookBrainz
I would love reviews from @LordSputnik and other members of the community.
I opened a pull request feat(handleDelete): Upon deletion, delete the entity from ElasticSearch also by shivam-tripathi · Pull Request #190 · metabrainz/bookbrainz-site · GitHub few minutes ago.
Presently I am working on analysing the structure of the dumps so that I can explain more about them in the proposal.

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

Last week I started work on my SpamBrainz proposal, talked with yvanzo about it and should be able to get my first draft done this week.
I also finally managed to get my ListenBrainz dev setup running, thanks to ruaok and iliekcomputers helping me with a really weird permission error. Already sent a minor PR for LB and working on more.

@CatQuest

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@CatQuest

Been doing some huge instrument editings, that is, I haven’t really been closing a lot of INST tickets, but I have been reordering and fixing instruments we already have, esp replacing the obsolete “child of” relationship with "type of " or “related instrument” or just changing links to more appropriate instruments.
Work is not done and, should your favourite pet instrument need some love, go ahead and create an improvement ticket! (however keep in mind that the more information you give on that ticket the easier it is for me to work on it.)
created a feedback for chhavi!
had some connection issues (sorry everyone) I phoned my very helpful ISP and we reset stuff.
seems to not make much difference however, so maybe it’s my router

@uditgulati0

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@uditgulati0

This week I worked on my GSoC proposal. Did some research on plugin structures of different media players
Worked on LB-325. Also, alastairp helped me with LB-322

Summit dates

IRC Logs for #metabrainz | MetaBrainz Chatlogs

It was decided last week to keep the summit in Barcelona, but the dates were still somewhat undecided. 29th and 30th was proposed. After some confusion, 29th and 30th was decided upon.

ListenBrainz user survey

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

Helo again. Nothing much, but we are going to ideate on potential graphs for ListenBrainz. It would be cool if everyone can take a minute and fill this form to give us ideas on what graphs will actually make sense.
How do you Listen?
(I swear it’s less than a minute-long form)

DST notice

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

This is just a friendly PSA: Europe will switch to “summertime” on Sunday, so for non Europeans, the meeting will be an hour earlier for the next ~half a year.
(Unless you also switch to summertime, it’ll be 17:00 UTC from next week anyway.)