Notes from #MetaBrainz Meeting 2017-03-13

[Freso]

MetaBrainz Meeting 2017-03-13

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• DR: MBS-9271: Prevent usernames from being reused
• BrainzBot brain+gh plugins
• DR: CB-244: Implement a rating system

Reviews

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

I worked on my GSoC proposal for LB this week.
Also, worked with ruaok on some stuff, helping to get the beta deployed
some bugfixes etc.
not much else

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I had a cold all week (thought I was ok now, but then I got dizzy and had a three hour nap and still feel crappy, sigh)
So I didn’t get much done
Support (more MBID mail, mostly…)
Also at some point we ended up talking Wikidata, so I threw together some example queries for MB use: User:Reosarevok/Wikidata Example Queries - MusicBrainz Wiki
Which will be more useful once MineoBot is up and running properly

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I put out a blog post with the meeting minutes of the 2016 september board meeting (where I became secretary of the board).
There’s not much interesting happening at the board meetings that are not otherwise communicated, but it’s been one thing that’s previously been happening “behind the veil”, so to speak.
So hopefully this will help to make the MeB operation a bit even more open/transparent.
I’ve done a number of assorted miscellaneous tasks relating to jira and discourse too.
And responded to some MBID queries on the forums…
Until I said “enough is enough” and just passed those MBID questions on to reosarevok. (Soz… not soz. )
I created https://tickets.metabrainz.org/browse/ORG earlier today.
To have a more organised (pun kind of not intended, but not unwelcome) place for Quesito’s and my own tasks to get tracked.
And besides being around/about on IRC and forums, I think that about wraps this week up.
Tomorrow morning I’ll be headed to DK/Sweden.
And I’ll give a presentation on Saturday about open data and *Brainz: https://opensourcedays.org/community/talk?speaker_id=31

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

I spent a lot of time working with alastairp and iliekcomputers to get the LB beta up and running:
https://beta.listenbrainz.org
Status - ListenBrainz
shows the status of the system. a bit cryptic, but you can see data flowing, which is pretty cool.
I also spent time moving two supporters forward.
met Quesito for 6? 5? hours and going over lots of stuff. including getting huffy over a faux-gantt chart.
we were productive, even if a bit tipsy.
and the other, really exciting thing, is that I worked to get @yvanzo hired!
I had been working numbers to get that to work and our two prospective cust^H^H^H^Hsupporters put us over the line.
welcome to the team, yvanzo!
this is quite noteworthy – we’ve never had 2 engineers dedicated to just hacking on MB.
we’ve had 3 people, but with many more duties spead across many things, including hosting.
now we have three devs and me as a part time dev of sorts. plus all the volunteers we have now… I’m quite proud of how much ass we’re kicking right now.
and I’m off tomorrow. Not telling where I am going. I’m leaving some clues behind – some more useful than others.
if anyone wants to follow along and guess where I end up, follow mayhemcha0s on instagram.
however, if you have access to our servers and check the login logs and look at my IP addresses if I have to log in, I ask that you not spoil it.
I’m not going to go as far as installing tor, ok?
I’m back on to work on the 23rd.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

i helped Quesito on a mail in french, upgraded servers, created a bunch of new graphs for new LB on lemmy
i continued on piwik, and i have found new isssues i’m trying to solve, for now, doesn’t work reliably at all
but the sync is ok, piwik parser sometimes stops on weird log lines
i reduced the size of mb log dropping 403 on ws, dividing by 3 the actuall number of lines to parse, but piwik is still on the slow side, whatever i do
plus Picard PRs reviews/forums and of course a bunch of new releases in MB db

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I deployed the sentry PR to beta, seems to be working
did more code review
commented on schema change tickets and the sir google doc
submitted a PR to check mbs code with Perl::Critic, since we’re getting more PRs now and it saves me from having to comment on stuff
(maybe I’ll look at Perl::Tidy in between schema change work too)
started looking at the alternative tracklists UI branch again, so it doesn’t miss yet another schema change
fixed some style errors in picard-website and very briefly helped with LB docker issues

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I started implementing new trigger generator for the indexer, since we mostly figured out how it should work
set up welcome topic on the community website in the critiquebrainz section (thanks, Freso)
and created a topic for a discussion about ratings
reviewed a bunch of code
and some gsoc proposals

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

I continued my MeB education
Mid-week I welcomed a new supporter to the bronze tier!
then continued my MeB education with ruaok over 5 hours…
MeBeercation
my gantt chart did get the ax…but my plan for MeB world domination continues on…
[@Rob: now Quesito, that was not against world domination. our flavor of world domination just works without gantt charts.]
yes @Rob…so now my world domination plan will be carried out via JIRA ORG thank to Freso setting it up this am
I am now between verbiage and getting organised in ORG

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

Okay, I had a surprisingly productive week
Worked a lot of BrainzBot (am in fact even working on it during this meeting)
I signed up to help with MineoBot and improving crosslinking with wikidata

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

I have been formally hired by some foundation as you might have guessed from March 13, 2017 – MetaBrainz Blog
FYI, I unified my various nicknames on *Brainz, Freenode, and GitHub to match my BookBrainz account, yvanzo.
For the rest, my first main and still on-going assignment has been to extend dynamic attributes, currently for Work only, to all other primary entity types, but URL, and secondary entity type Medium (MBS-8393 for next schema change).
In case MusicBrainz development would not make expected progress, I will immediately blame gcilou who just stepped out.

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

I worked on my gsoc proposal and sent a couple of bugfixes to CB related to ISEs on event and place review pages. nothing much. working on improving the proposal.

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

last week a wonderful thing happened; loujine created for me an “batch add aliases” script https://bitbucket.org/loujine/musicbrainz-scripts/issues/27
it’s still in an early stages, so anyone using it must be careful!
but I’ve been using it and it’s fantastic, it’s made adding aliases for instruments a dream!
so: everybody, it’s completely ok to request aliases for instruments now; or any instruments where the WD/wp has a list of linked languages with names? make a ticket with lists or links <3
as such I’ve made a great headway in adding instruments from the hybrid ticket: https://tickets.metabrainz.org/browse/STYLE-723 (as always anyone who knows of any other hybrid instruments, existing or just ticets themselves, please link them)

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

I had jury duty during the meeting last week and family since, so I’ve just been brainstorming and not writing any code. And I’m out of town right now.
When I get home this weekend, though… you just wait and see. I might fix some whitespace.

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

Hi everyone, can’t make it to the meeting since I have an early morning flight to catch.
So Freso should most probably be posting this instead.
Worked on lots of picard PRs and fixed tickets and did PR reviews this week. Was at home so lots of free time.
Also finished up my Gsoc proposals first draft, those interested can see it here - Picard v2. 0 https://community.metabrainz.org/t/gsoc-2017-pi…
Also setup things for a 1.4.1 release.
Will be afk next week since going trekking. Might be in a region with poor network connectivity so sadly no irc and definitely won’t be able to code.
Will try to catch up with irc stuff once a day though. Will be back on 19.

DR: MBS-9271: Prevent usernames from being reused

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

we need to decide if we want to disallow people from taking usernames that were previously used

There was a brief discussion about how other sites handled this (only Facebook and LiveJournal was mentioned).

@Bitmap noted that the answer to this question might also possibly resolve MBS-9275.

@Rob

let me sum up: “We should prevent re-use in general and implement 9271. However, if someone contacts an admin with a request to re-use and that request is reasonable, it will be granted”

This was agreed on unanimously (with 9 people “voting”).

BrainzBot brain+gh plugins

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

Okay, so @samj1912 did most of the work editing the existing github plugin to fit our needs
the desired use case was looking up PRs similar to how we can currently look up JIRA issues
so assuming the repo is part of the MeB org, you can add an abbreviation using @gh:abbreviation=repo_name
and then get commits using gh:abbreviation#PR_number
for example gh:P#642
it’s still in beta and subject to sudden data wipes
the brain plugin is currently disabled until I finish rewriting some backend stuff

DR: CB-244: Implement a rating system

Deferred to next meeting, due to time constraints.

[jesus2099]

@Freso, it should be March (3), not April (4).