Notes from #MetaBrainz meeting 2018-03-12

[Freso]

MetaBrainz Meeting 2018-03-12

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Code of Conduct/Privacy Policy/Social Contract
• Summit date
• Picard beta releases
• Design ticket
• MBS-1159: Add support for 3-point relationships

Reviews

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

This week and the previous, I worked on removing old WS access code in CB. Also, sent a PR to show reviews of entities deleted in the MB database.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

Worked a bit on helping Rob release the new LB beta.
Did some work on deleting old dumps from the MusicBrainz FTP, which we’ll need really soon, I guess.
Helped rsh7 a bit with her GSoC proposal for AB, cool ideas there.
Been trying to find how our listen counts have regressed, they don’t get updated as quickly. Think this is a problem with the new caching
(Addendum: I went through dpmittal’s GSoC proposal too)

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

I spent far too much time last week dealing with banks.
so, one of the problems that our tax attorneys identified is causing problems with our bank is our tax id. they’ve straightened that out and I should be able to submit this new ID to our bank to unblock our account.
but they are no longer taking online document submission (quite a few hours of drama sorting that)
and they closed the local office and our manager doesn’t seem to ever find time for us.
which, led me to goign to open a new bank account.
and they said we’ll call you tomorrow.
that was tuesday.
so, I’ve paid everyone from the US account (more or less) and even then one payment is stuck and three banks are scratching their heads wondering whom to blame most effectively.
but we get the LB beta out with 100M listens, that was the high point.
today I worked on the CoC, and privacy policies, more on that in a bit.

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

In the last week I’ve spent way too much time trying to get my backup phone working after my main phone stopped working.
I’ve written with the organisation consultant I’ve mentioned before (backed up by ruaok), but haven’t heard more from her since.
I also poked the Arch packager of Picard on behalf of samj1912 about picard’s packaging.
(On Arch.)
And keeping and catching up with IRC and forums.

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

worked on couple of Picard PRs and more than a couple MBS PRs, picard reviews, and managing my travel bookings for the rest of the month

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

worked on the release group page, will continue working on it this week and prolly move on to the release page!

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

mostly worked on the same stuff as last week, reviewing PRs, testing react changes and fixing test failures
nearly finished rebasing my react sidebar PR into reviewable commits
also made some progress on the webpack PR, reduced our dependence on lodash to make the bundle sizes smaller
hopefully will wrap up the sidebar stuff this week and work on converting more templates that depend on the sidebars

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I did support
Also talked with CatQuest and opened this:
Add an instrument type for standard groupings [STYLE-936]
Please give feedback etc

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

I worked on Markdown for *Brainz, did reviews, and got in touch with potential GSoC applicants. Otherwise, I was mostly on vacation.

@drsaunde

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@drsaunde

okay well first off apologies to anyone who was waiting for areas
had my largest backlog i’ve ever had there
a combination of it being tax season and our friends at kexp taking up all of (and more) of my precious free time
anyway I bore down last night and closed a couple dozen so those should now be up to date
the issue i am having is that i keep collecting active editors that don’t care/don’t respond but keep adding stuff that needs major fixing
before we could punish/force new behavior by no-voting additions…now i’m at a loss and can’t keep up
i would love some help/suggestions there

(@Freso requested that this kind of extended discussion should happen in its own agenda item for the meeting rather than being discussed during reviews.)

@visichoudhary

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@visichoudhary

Hi everyone, i was not well in this week. visits home after a long time.
but open up some tickets in picard
and worked on some of ticket PICARD-1220
PICARD-1213
and working on a bug right now.
Will make a pr in 1 -2 days

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

usual stuff, maintenance, improved some grafana graphs
and manage bug reports/fixes after Picad beta 1 release
i’m planning a bunch of upgrades, that may need server reboots

@kartikeyaSh_ircc

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@kartikeyaSh_ircc

Mostly I’ve been working on my proposal for the project “A way to associate listens with MBIDs”
Got most of the write-up done. Now I’m having a hard time creating the timeline for the project and I’m worried that due to some anomalies we will end up disturbing some data in the LB database.
Hopefully by this time tomorrow I’ll be able to submit my initial draft. And I took a look at LB-310, I’ll start working on it after I’ve submitted my proposal.

@akhilesh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@akhilesh

This week I completed an initial draft of my GSoC proposal on BookBrainz web API project and posted for review. Which can be seen here:
GSoC 2018: Web API for BookBrainz in Node.js - #2 by mastcoder
Community suggestions/feedback would be greatly appreciated!
I worked on the @LordSputnik suggestions in the PR and other 3.
I also created PR to resolve BB-246 and another PR to resolve BB-245.

@manofcode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@manofcode

I’ve been working this whole week on the initial draft of my SoC proposal on the CB idea “Add support for reviewing and rating more entities”
I’ve been trying to dive deeper into the codebase and learn as much as I can.

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

This week I did some more work on the relationship editor. The UI is now working and seems to be bug free, so I’ll be moving onto the server side next. You can now add both forward and reverse relationships between any two entities during creation and editing (in the client)
I also reviewed some PRs, and will be doing some more after the meeting
Thanks to bukwurm and akhilesh for your work this week

@uditgulati0

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@uditgulati0

This week I mainly worked on LB-255 and LB-322
Also, I have been spending time in understanding the listenbrainz codebase a bit more.

@rsh7

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@rsh7

Last week I worked mostly on writing GSoC proposal for AcousticBrainz. And today I uploaded the initial draft.
Would look into other tickets to work on this week.

@bukwurm

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bukwurm

So this week this happened
https://usercontent.irccloud-cdn.com/file/yJVS82na/screencast.gif
Users now will be warned if they enter an entity that already exists
It took a lot of time
So practically the week went in this only
I’d hopefully be discussing with LordSputnik today about data imports

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

first: sorry for being late everyone and disrupting the meeting, I’ve set an iCal reminder now so it should work from now on
Working hard on instruments, did quite a bit of reordering on the strucken idiophones
i.e. INST-630
gave reosarevok a wacky idea​​
finished up the Baltic psalteries, added caixa, clapper and something called the hyoshigi
closed a few as dupes/not done.
welll I updated the mac and now everything is super unstable. I’m going to have to find some way to move the stuff from this thing onto something else and perform a complete re-install since things are totally shit right now.
moral of the story: Never Update ANYTHING!
in other related news, i’m up to FF 44! that’s an improvement right?

Code of Conduct/Privacy Policy/Social Contract

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

everyone: here are my proposed fix-ups for the Code of Conduct, the Privacy Policy and the social contract:
https://github.com/metabrainz/metabrainz.org/pull/299
overall, no real changes except for consolidating it into a MeB set of policies and updating them for our current setup.
the PR has links to the test.metabrainz.org site with the changes up.
please have a look and leave a comment for anything amiss. typos or whatnot.

Summit date

IRC Logs for #metabrainz | MetaBrainz Chatlogs

A bit of discussion about whether to hold Summit 18 in Barcelona or India, but it was decided to keep it in Barcelona for at least this year again.

For dates, September 8/9, 15/16, and 29/30 were thrown around, with 8/9 being discarded. Since it seems like most people would be good with 29/30, that was decided for a tentative date pending any objections or other input at meeting next week.

Tentative decision about next summit: September 29th–30th, 2018 in Barcelona.

Picard beta releases

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

We’ll release beta 2 this week, we need people to test and report issues (including related to packaging, win/mac), volunteers to help to debug on those non-free platforms are welcome…
please think about installing / testing latest Picard 2 beta

Design ticket

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

Release group mockup is up here. Feedback, comments, chocolates welcome
https://tickets.metabrainz.org/browse/MBS-9652

MBS-1159: Add support for 3-point relationships

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

So, people in the style topic I mentioned earlier wanted us to wait for that to be implemented before we do it, so we can say X played Y in band Z
I assume it’s actually not happening anytime soon (i.e. in years probably) and I should just override the request in order to get this change in in a reasonable timeframe
But wanted to make sure if we have any sort of place for MBS-1159 in our future plans timeline
(to know what to tell them about it, mostly)

@bitmap noted that there is «nothing currently planned» and @yvanzo added «not 2018 for sure». @bitmap continued to mention that there was some previous discussion he would have to dig up, and gave a very tentative ETA of «2019 maybe?».