Notes from #MetaBrainz Meeting 2024-10-14

[aerozol]

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

Agenda

• Reviews
• AX102 server
• Offensive usernames

Last meeting: 2024-09-16 (then summit break)
Next meeting: 2024-10-21

@reosarevok: Hi, and welcome to a MetaBrainz Monday Meeting!
It’s been a while!
Hopefully everyone has had some time to relax. Or, judging from some of the reviews, to do the opposite.

Reviews

@derat

[mailed in] My fix for MBS-13757 was merged pre-summit, and I sent a little fix for MBS-13777 a few days ago.
[MBS-13757: Make it easier to update most (but not all) recordings from tracks]
[MBS-13777: Duplicate release groups warning can incorrectly check “add a new release group”]

@atj

[reo: reports that they’ve been too busy with other things to have anything to report.]

@rob

[mailed in] [mayhem] Last week I was stuck in Mom hell in San Diego. San Diego sucks, don’t go.

@outsidecontext

[mailed in] Last week I looked into several bug reports for Picard. Provided a fix for a possible crash related to settings handling and have started working on a fix for some file system permission issue resulting in the file naming options becoming unavailable. I’ll submit a PR for this soon.
I also researched code signing options for Picard, as our certificate at SSL.com expires soon. We need a new one to be able to sign new releases. We want to get rid of ssl.com due to the bad experience we had with them in the past, but alternatives are more expensive.
Also we need to move to either Azure Key Vault or a USB hardware token (requirements changed since we last ordered a certificate 2 years ago). But I’ll discuss the details with mayhem and zas in the coming days.

@bitmap

last week I started working on the branch for MBS-4501 again as we discussed at the summit
[MBS-4501: Alternative tracklists]
a lot of work was done for this ticket previously. the JavaScript/UI parts still need significant work, but I think the Perl parts (for the controller/edit system) are fortunately still usable
so it may only need a few more weeks of work for the UI and tests
other than that I was mostly looking at the WIP ESLint v9 PR reosarevok put up

@jasjeet

[jasje] Last week i was just testing listen service with battery optimisations disabled. So far its okay. But we need to pivot to another approach in sometime
Also, our dropdown was not very re-usable, so i just figured out a way to make it easily usable just by a fn call.
Also, gave KT session to a new possible contributor on LB and some things that would be a good to have in the app.

@theflash

[theflash_] Last week, I picked draft navigation pr and working on using new ways for user navigation
Hopefully will implement it soon
Other than that university sucks
Missing the summit days, lol

@mr_monkey

[monkey] I had a lovely time in India at the summit and visiting. Thanks fort being so welcoming! Have been thoroughly enjoying all the indian snacks I brought back.
Last week I worked in tandem with ansh to improve the artist pages on ListenBrainz
Better album sorting and grouping, the current iteration is on test [link]
And doing some of the usual updates, security tickets and whatnot, as well as creating tickets and organizing things after the summit discussions

@reosarevok

Last week I was traveling and resting, and I only got back to work on Friday
Friday and today I was catching up with stuff (reports, wikidata bot, genres)
And working on the eslint 9 migration
The plugins that did not support eslint 9 now do, which is great
Less great is that they’re detecting issues with guess case code (which is to this day a terrible ball of spaghetti) so I’ve spent several hours trying to make it suck less
More of that ahead
Other than that, the usual support (still haven’t fully caught up with all of it, but getting there)

@CatQuest

[ApeKattQuest] I spent the last week being fairly ill : (
but I’m feeling much better now!
I’ve been looking at the ravanahatta String instrument “ravanahatta” - MusicBrainz (if you remember the guy at the restaurant, this is the instrument he played : D)
in that vein I had completed my very first instrument image upload using github, with help from reosarevok!
so this week I will be looking into more indian instruments, and, eventually, finally finishing the “Veena” mini-version some time hopefully this month!
I also, thanks to monkey! (just earlier) had my Very First patch merged : O
in not so computer news. I’m going to have to get a move on to paint my window before it starts getting winter here. hey norway amirite?

@anshgoyal31

[ansh] Last week I spent time working on the donors page and the donors card on the LB Feed Page.
Worked on refactoring the Artist Page - Sorting and Grouping the Release Groups.
Spent time on reviewing a couple of PRs and fixed an issue causing the website to throw errors on the stats page

@zas

Last week was mostly about upgrades, support related to IA downtime, and few blocked users.
Plus a lot of edits (mainly releases I didn’t add during our travel), now with a lot of pending cover art additions…

@kellnerd

Last week I was still recovering from my four week journey around the India summit and tidying up.
I still haven’t managed to prepare an awesome masala chai, everything I tried so far was ok at most.
At least I managed to finally release the Harmony update which has been on hold for about three months.
Although I thought I had finished it during the summit, I still had to deal with some rarer cases and a bug.
This week I should be able to continue working on the BB importer… yes, my GSoC project is still running

@lucifer

it was lots of fun meeting finally everyone at the summit!
1after the summit, i went with mayhem and akshaaatt to the gsoc mentor summit. had some nice conversations there as well.
also helped mayhem with an accounting script.
i have been mostly away for the past two weeks but will be working normal hours starting today/tomorrow.

@yvanzo

Just back from my extended stay after the summit.
Thanks to lucifer, ansh, jasje and theflash for welcoming us.
Congratulations to yellowhatpro 1. for having completed his project: [blog post]
Otherwise I just dealt with maintenance issues, support, and tickets triage. Looking forward for new test servers!

@Ashutosh_Aswal

[yellowhatpro] last few weeks were about wrapping up the project
last week was more chilling and I didn’t do much, except went through a lot of sentry messages
feels good reading the comments on the blog post, seems the project melba would be really helpful.

@JadedBlueEyes

[Jade] I’ve just got back from a trip doing rock climbing in Cheddar Gorge, so I’m a bit tired haha
Uni’s been a bit stressful adapting to stuff again (and organising stuff like the trip)
Right now I’m looking for a placement for my year in industry for 2025/26
I’d also like to start making small PRs to enable MBS-13719 piece by piece so everyone can enjoy that : )
[MBS-13719: Integrate new mail service into MusicBrainz Server]

@kubrimskii

[rimskii] Honestly, havnet worked that much on project, mostly now doing my uni stuff
But I would like to stick around for a bit to finish some moments!
So will start to work from now on😄

@akshaaatt

[after meeting] Just had epic conversations with people at the gsoc mentor summit! Great experience

AX102 server

@zas

As discussed during the summit, I’ll order a new AX102 server in order to replace 3 old PX61
I was waiting for all to come back from travels, as we need to coordinate mainly with bitmap yvanzo atj to do the move
It should happen this week (depending on Hetzner)
Once the new server is there, we move stuff to it, and retire 3 old servers, and then we’ll do it again the week after for remaining 3.

Offensive usernames

@reosarevok

We haven’t really had any policing over usernames ever, but we recently got a report by somebody who got hurt by someone else’s (probably unintentionally) ableist username
We also have a fair amount of usernames which are clearly offensive, but have so far offended nobody enough to get them reported
I was wondering what people feel should happen with these. I don’t feel like we should start blocking usernames on registration (that never works well anyway)
But I’d like some opinions on what should happen if someone does get offended by a username and reports it
At the very least I guess we could contact the user and ask if they would mind changing the username since someone has felt hurt by it, and if so to let us know what would be a good name
But I’m not sure about enforcing a change if the user would disagree

It is agreed that it doesn’t hurt to mail the user and ask, for now.
Read the full discussion here.

absent: aerozol (1) ericd (2), pranav (2), twodoorcoupe (3 - removed from regulars list, feel free to add yourself again any time)