Notes from #MetaBrainz Meeting 2023-05-29

[aerozol]

#MetaBrainz Meeting 2023-05-29

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs
Meeting wiki page: MetaBrainz Meeting - MusicBrainz Wiki

Agenda

• Reviews
• Indicating blocked editors
• Blocking beginner voting again
• Profile Pictures

Last meeting: 2023-05-22
Next meeting: 2023-06-05

@reosarevok: Welcome to Monday Mayhem with me, and I guess also mayhem
Today everyone is being lazy (good for you!) and we have not one, not two, but three mailed in reviews!

Reviews

@kellnerd

[mailed in] Last week I’ve fixed two BB bugs before the release, one was caused by Safari’s inability to keep up with browser standards, the other was my own ; )
Time to fully get back into BBusiness this week by starting with my GSoC project, yay!

@atj

[mailed in] Last week I continued working on preparations for the consul migration with zas. This included writing a new role to install and configure unbound, resolving an issue that caused consul not to be started on boot and implementing new functionality to manage consul script checks. We also did a fair bit of testing and it looks like we’re pretty close to being ready.
I also spent some time looking for summit accommodation and discussing options with mayhem.

@aerozol

[mailed in] Bits and pieces this last week.
Clarified the auto-editor election process with reosarevok. Drafted some dataset attribution guidelines with mayhem. Tweaked some Weblate colours and icons with yvanzo.
A bit of community stuff, some more MB guideline drafting.

@bitmap

last week I was mostly working on improving our postgres cluster for high availability so we can perform switchovers with no downtime
I spent time testing and improving the (currently unused) haproxy container in the docker-postgres-cluster repo, plus the associated health checks for determining whether a node is primary or standby
this is still in the testing phase, but perhaps we could deploy it next time we ugprade pg (maybe in lieu of next schema change)
I also submitted a pr for MBS-13015 [Tracks with (only) URL relationships do not show in the relationship editor] and did a small amount of code review

@reosarevok

I spent quite a bit of time improving our JS tests
Still a lot to go
Other than that, tiny bit of code review, a fair amount of community management
Few small tickets
I also sat on the board meeting for Q2 which was uneventful

@CatQuest

Figured out some monkey stick/stump fiddle mess
Uploaded quite a few images with reo
working on adding another instrument right now
and tested the new Alias Locales!
thanks yvanzo and reo for such fast deployment
I’ll be a bit more afk in the coming weeks. But i’l be around.

@mr_monkey

Last week I merged some BB PRs, did a bunch of beta testing, some fixes, and deployed a new version of BB
Also reviewed PRs for BB, particularly working on the revision reverting
On the LB front, I worked on improving and fixing playlists
Did some ticket triage, fixes tiny bugs
And talked more about the redesign and new recommendations page

@zas

last week was mostly about preparing the most to new consul cluster
as atj said, we’re getting very close, I expect to do it this week
We had another problem after docker upgrade (this time minor version one) resulting in broken net stats
it happens last time (major version upgrade), so we thought it was because of that, but apparently something changed in docker that causes live-restore to not work well
that’s very annoying, because the only way I found to fix it is to restart containers after the upgrade, and basically that nullifies the live-restore feature
this is something we need to investigate more deeply, I keep the focus on consul upgrade for now
apart that, I detected weird things about SOLR that yvanzo have (partially) addressed, concerning missing or duplicate replicas in our SOLR cluster
plus usual Picard PRs reviews, user support, supervision, grafana alerts/dashboards tuning

@rob

last week I worked with atj to book summit lodgings and we booked one place – we’d been there before. the place with the terrrace overlooking the parc.
friendly host, he recognizes me from the barrio, so that is good.
I also worked on background stuff, trying to seal a couple of deals.
related to that aerozol and I worked on the attribution guidelines for our commercial users.
I worked with monkey and tag and release group tag radio and we moved the whole lot further along. I’m genuinely excited for this work!
I also wrote article for the 3 part article series. that was kinda fun!

@lucifer

last week i worked on implementing the login system for MeB as a part of the Oauth stuff.
i also worked on adding popularity datasets by processing MLHD+ data.

@yvanzo

Last week I helped zas with getting some servers ready to reboot.
Also did some other maintenance tasks for Jira and Solr.
Pushed and reviewed a few MBS pull requests too.
Mostly getting prepared for switching translations to Weblate otherwise.
(It includes wiki landing pages and forum category about internationalization.)
Plus usual tickets triage and support.

@arsh

So last week I spent time brushing up on some react definitions and learning about d3js
getting everything ready to start my gsoc project
And some time looking around how things work
and excited to start with my project

@jasjeet

exams over and gsoc project is fully engaged
started with visiting back my proposal, made tickets section wise and have started Phase 1
went through tickets
more people are using the app now
took care of the tickets and replied to a query on MeB community as well
did some work on Feed Listens endpoint

@akshaaatt

I revamped the entire ui/ux for profile and listens submission. We also got rid of unnecessary screens and stuff and I’ve started to work on our explore screen.
I just made a beta release today. We will focus a lot more on UX of the app from now on.
That’s pretty much it for now. I’ve just been juggling with stuff lately

@ShivamAwasthi

I’ve nothing worthwhile to report from last week. I was mostly afk, out with friends.
This week I am finally going to start the work on my GSoC project. Really excited for that.
Oh, and last week I also got to connect with ansh and we had a nice conversation. He’ll also be mentoring me during the project.

@vscode

I worked on another ticket last week to fix minor issue for Api error message
connected with my mentor
I am working with him to get me the developer key for apple that I will need for my GSoC project
Revisited my proposal and getting ready to start it.

Indicating blocked editors

@reosarevok

So right now, when we mark someone as a spammer in MB, that is visible for everyone (or well, they become non-visible for everyone )
But when we just block someone’s editing or edit note privileges, we do not show that to users in any way
IIRC the argument for that was that we didn’t want to shame-mark users who got banned
But a) most sites mark banned users clearly
b) we keep getting banned people re-reported because people cannot tell
Is there any reason you can see not to have a notice that a user is banned?

[aerozol’s summary] Discussion, mainly around how to display a user being banned (or ‘under investigation’), nobody arguing against not showing anything at all. Reasons given for wanting to display something are that we get a lot of repeat reports of users who have already been banned, and that it’s not clear that a user can’t respond to notes.
The question is raised as to why we keep these accounts around at all, it’s mentioned that it’s helpful to keep track of new ban-evading and tracking down other accounts.

@reosarevok

Nobody seems to disagree with marking them in some way at least to discourage further reporting
So there’s that, we can discuss impl details in a smaller setting

Blocking beginner voting again

@reosarevok

MBS-13100 [Re-add some sort of vote restriction for new editors]
So, turns out if you let new accounts vote, people start sockpuppeting, because people suck
(well, some people)

[aerozol’s summary] Heaps of good discussion, that is too long to fully summarize. Read the logs!

Some salient points: It’s hard to get 10 edits voted on - should new editors be allowed to vote/do they know enough - a few days wait seems to discourage sockpuppeting.

@reosarevok

Ok, thanks for the useful discussion, I got a bunch of good possibilities from here, and the conviction that we should wait a week at least anyway
Will think it through from here

Profile pictures

@lucifer

To improve the UI of the mobile apps, we want to add profile pictures for users. It probably makes sense to make it common across all our projects.
However, that comes with many issues, especially moderation.

[aerozol’s summary] Immediate agreement that we should be able to pick artwork from the CAA.

Some additional discussion around how to deal with NSFW/manipulation that goes against the CoC to get specific pictures up, but it’s agreed that can be dealt with later.
There is loose agreement that punishment will be having a Rick Astley picture permanently set on their profile for a year.

Missing: Pratha-fish (1), riksucks (1), pixelpenguin (1), jivte (1)

[rdswift]

@aerozol

riksucks (1)

Shouldn’t they be 2 (or even 3). There was no report by them in the two previous meetings.

[aerozol]

@riksucks let us know in advance that they would be absent for a few meetings

p.s. Though I’m sure riksucks doesn’t mind, it’s probably best to PM about this kind of thing in future

[rdswift]

@aerozol

@riksucks let us know in advance that they would be absent for a few meetings

In that case, I would have expected to see that reflected in the meeting notes so that they are given the benefit of the doubt.

[aerozol]

Sorry about that. I’m happy to track absentees in the casual manner I’ve been doing so far - if you have more detailed expectations you’ll have to track them yourself.