Notes from #MetaBrainz Meeting 2018-02-05

[Freso]

MetaBrainz Meeting 2018-02-05

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Google Code‐in
• Anti-spam policy

Reviews

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

so this week, I worked on picard/libdiscid packaging
which basically involved me getting frustrated with windows/osx
also, phw helped with libdiscid windows builds since picard now requires 64 bit libdiscid
apart from that, did a minor sir upgrade to add release rels to urls
and picard reviews

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

mainly picard stuff, a lot of code rework, mainly to make things just work
in-app search dialog revamp
ratecontrol fixes and rework
and PR reviewing
plus usual supervision, upgrades, and helping people around on various tasks
the plan is to release picard 2 asap
to clear the path before the GSoC

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

So, other than usual support stuff (which keeps arriving in my spam inbox, together with all the Russian ladies who allegedly find me very hot)
We started the new classical cleanup:
Community Cleanup #4: Hyperion
(thanks chhavi_ for the banner!)
It’s a label this time, and since they have booklets available on their website, I’m hoping for a lot of new high-quality releases
loujine also did some great work with a nice dashboard that shows what needs to be done
And I really need to (convince someone to) write a blog post
Other than that, just the usual editing
Oh!
And the cleanup discussions meant that I finally split that absurd meaningless “design/illustration” relationship
https://tickets.metabrainz.org/browse/STYLE-903 - if people have comments (like, “should design and graphic design both exist”) comment away

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

GCI Finalists Hype!
Finally started working on instruments as added by our lovely gci students!
of course the first I try is not one but two!
Here Grove has helped me already! :​D
(un?)fortunately I have (finally) started playing BotW, so maybe I’ll be afk a bit in the futures :​p
STILL no info about my macomputer :​/ I don’t know what to do :​c

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’m still trying to catch up on backlog, being sick on-and-off (I love Scandinavian weather!), as well as still trying to get the last few things in order with the official side of Sweden.
I did a little bit of GCI’ing too, incl. answering an e-mail from a student that unfortunately didn’t make our top 5. I’ll take a bit more about that in a moment though (GCI, not the e-mail).
(Oh, also, in my off-time, I also convinced whipper to make a 0.6.0 release, so @naiveaiguy’s GCI contribution to them is now released. )

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

No specific updates this week. Just stepped back a bit and did a lot of thinking on the overall navigation and other details for MusicBrainz.
Will hopefully have something concrete by next week.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I was working on fixing tests in Add a selenium test for /work/create, add more flow types, and remove Immutable.js by mwiencek · Pull Request #606 · metabrainz/musicbrainz-server · GitHub but it’s still a bit broken
helped test some picard osx builds from samj1912
worked on my entity sidebar → react conversion branch from a couple months ago which I think is almost done
fixed up https://github.com/metabrainz/musicbrainz-server/pull/595 and helped spellew with other react work
looked into react-boostrap and experimented with creating a thin bootstrap v4 layer for react

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Past week I continued the developement of MB spam reporting/hiding tools. It is fortunately coming to an end soon. I will give more details after the reviews.
I worked a bit on React, with spellew’s help, and looked into plans for design system, bootstrap, and all.

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week I did a lot of admin stuff, like paying people.
a couple of phone calls, loads of emails.
I also finished tweaking the GSoC ideas page and our application.
then I spent a bunch of time finally getting the LB containers/cron squared away.
zas made a new graph for me.
hopefully tomorrow I can finish deploying the rest of the containers for the beta on LB.
its beeen a loong road. sigh.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

i spent the past week working on LB and AB as usual
there was a small stats bug stopping calculation that I fixed
we now have stats on beta.listenbrainz.org btw
other than that, I setup Jenkins for AB and worked with alastairp on making use of flask cli in AB
and some research on how to get LB dumps to williams for ftp downloads

@vishalchoudhary

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@vishalchoudhary

mostly worked on PICARD-1177 and PICARD-1184
and other PICARD related stuff

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

This week I did a lot more work on the BookBrainz relationship editor
Everything works within the UI now, just need to add the editing/deleting stuff for existing relationships
But I want to clean up the code a bit before I move on to the server processing of relationships from the form
I also did a schema change, and added over 40 new relationship types
(locally - this will go live when the relationship editor goes live)

Google Code‐in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

So Google Code-in is now officially over and all winners and finalists have been published.
Congratulations to @naiveaiguy and @haruute for the grand prize winning!
And congratulations to @spellew and kartikohri and Enjeck for the finalist spots!
And congratulations to all the other students that completed tasks for us too!
I feel like this year was the toughest one to pick out the top 5 from so far, so sorry to all the really close contenders, but in the end, we could only choose five.
In all we have had 741 tasks done. A lot of these were data entry ones, and a lot of these were handled by MajorLurker who stepped in at the beginning of the contest to help us out as we realised we were getting into deep waters.
All our mentors have done great jobs, but I really want to highlight @MajorLurker in particularly for stepping in and providing breathing room for the rest of the team.
GCI was also a bit crazy for me, as it happened right on top of me moving country as well, so everything was kind of disruptive. Thanks a lot to @caroline-g for acting as co-general-org. admin as well. She’s really climbed the ladder.
I think that’s about what I wanted to say. I hope GCI students haven’t been too disruptive.

Anti-spam policy

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Actually “Spam Wars - Teaser”
For months there are malicious users/bots abusing the MusicBrainz database to broadcast advertisement, scam, and other unsolicited content.
The most commonly used spam vectors are editor profile, then URL, Artist, Release and other MusicBrainz entities. There are other potential vectors that will need to be addressed, another day.
This spam should be hidden/delete/blanked from the MusicBrainz database.
(This is part of our world domination plan)
Since unappropriate deletion and blaking can make irreversible damages, such operation should not be in the hands of everyone. At Summit 17, we proposed to create new privilege “spam ninjas” for editors allowed to take action against identified spam.
Identifying spam entities (URL, Artist, Release, and so on) relies on public data. On the contrary, user accounts have private details such as email address. Spam ninjas won’t be allowed to read it, but SpamBrainz will.
To sum up, spam ninjas will have some admin capabilities (hiding/deleting/blanking illegitimate content) but won’t have access to private user details.
It does not challenge Privacy - MetaBrainz Foundation at all. (Freso was worrying about that.)
Any question, concern, remark, suggestion is welcome now, but applause.

There was a bit of discussion/questioning about clarification, namely that all users will be able to report spam, but only spam ninjas will be able to take action on the reported spam. SpamBrainz will initially not do anything in an automated fashion, but rather spam ninjas will feed SpamBrainz with reported positives so that SpamBrainz can learn to begin with.