Notes from #MetaBrainz Meeting 2025-02-10

[aerozol]

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

Agenda

• Reviews
• Summit Dates
• Staff/admin SSO

Last meeting: 2025-02-03
Next meeting: 2025-02-17

@reosarevok: Hi, and welcome to another MetaBrainz Monday Meeting!

Reviews

@derat

[mailed in] I finally dug into MBS-13920 and sent two small PRs that I think will fix it. I also started working on a few URL batch edit tickets (MBBE-91, MBBE-92, MBBE-93).
[MBS-13920: Make it harder to skip warning about feat. artists in track titles]
[https://tickets.metabrainz.org/browse/MBBE-91]
[https://tickets.metabrainz.org/browse/MBBE-92]
[https://tickets.metabrainz.org/browse/MBBE-93]

@aerozol

[mailed in] This flu is hanging around : (
Still sick… did a bit of socials and support, tickets, stuff which I could do in bite size portions, but no energy to progress bigger tasks
Sorry ansh!! (who is waiting on something from me)

@kellnerd

Ehm, let me check my notes, but I don’t think I have anything to report this week…
Right, that’s it : D

@julian45

This week I finished writing up a proposal that I’ve added to the agenda for later in the meeting, as well as discussing some ways to mitigate an open Ansible-related issue with zas

@bitmap

last week I opened a PR for adding rabbitmq metrics to the musicbrainz-docker monitoring setup
and another PR for MBS-13925
[MBS-13925: supporting instruments relationship displays instrument name in place of “instruments” erroneously]
started working on moving postgres-aretha to selda, which should speed up test.mb significantly and resolve some load issues there
made some updates to [#3430] to fix building pull requests, though it involved completely changing how the docker images are cached and used (again)
[Migrate tests to GitHub Actions #3430]
unfortunately the selenium tests are still very flaky in that branch, so I’m still working on debugging on that (and some improvements to help aid debugging, like taking a screenshot of the page when a tests fails, and uploading that to the build artifacts)
other than that, did a bunch of code review

@reosarevok

Last week I worked on a few ISEs and bugs, yearly stats for editors, tested prometheus/mb-docker PRs and ensured the monitoring doesn’t die when the database comes down temporarily
Other than that, the usual style / community stuff

@zas

Last week, we (with outsidecontext) released 2 versions of Picard 2.x (latest stable + hotfix)
I worked on the DNS move, that should be start soon, I’ll migrate domains slowly depending on their renewal dates.
(btw, mayhem let’s talk about MeB account for that, later)
I also worked on haproxy + LE + DNS-01 + DNS API, in order to solve a long standing issue related to a lua lib we use on current gateways setup. Still trying to figure out all moving pieces.
Plus usual supervision, user support, MB edits, etc.
Also discussed with julian45 about various things (notably auth & ansible)

@yvanzo

Last week, I mostly worked on retrieving and exporting the MusicBrainz Solr 9 backups.
Also I did set up a meeting with bitmap and reosarevok to discuss GSoC ideas for MusicBrainz.

@outsidecontext

zas already said it all : ) We did the Picard release, and had to do a bugfix release due to a crash introduced in a new feature. Otherwise all went fine

@ApeKattQuest_MonkeyPython

[Jigen] Week continues to be fullspekka.
had Yet Again a very productive discussion with mr_monkey
spanish proves to be está tardes lol
Continued working on the TOC of Book(z)
and some “every day of february redraw a classical painting of people kissing with other characters(fanart)” thing on bluesky which I’m enjoying immensely.

@rob

[mayhem] last week I dusted off the notifications spec and made it ready to be implemented by a gsoc person.
overall gsoc work in general – our ideas pages should be done by tomorrow when the application deadline comes.
(I’ve applied for us already, but they’ll start looking at our ideas page)
I also reviewed PRs, followed up on some failed cron jobs, worked on the BBC contract renewal
finally I worked on making typesense searches faster and my primary test case? looking for exact matches in the data – because that was the easiest starting point.
and I managed to get those searches FAST – about 10ms or so.
but when you’re searching for stuff that doesn’t exist, or has typos, the speed is 6 or 8 times SLOWER.
ok, time to have see if SOLR can beat that, lol.

@mr_monkey

[monkey] I started last week with security updates and tickets
I then finished working on the new My Network feed page, deployed today on LB: ListenBrainz
I worked with Jigen (IRC) on the BookBrainz docs some more
Reviewed PRs right and left
Improved some edge cases in loading cover art for LB
And generally reviewed user feedback, opened and closed tickets, kept users up to date with fixed bugs, etc.

@jasjeet

[jasje] Last week was fun
Release v2.8.1
Fixes bugs related to brainzplayer
everyone: shift to that one if you have LB Android installed
Apart from that
Did some PR reviews

@anshgoyal31

[ansh] Last week, I finished my work on revamping the playlists page.
Integrated LB Radio with the upcoming genre-explorer page.
Reviewed couple of PRs, and make some POCs for evaluating GSoC projects.

Summit Dates

@rob

[mayhem] this is just following up from last week.
15 - 19 Sept.
anyone have any objections or should we make that the date?

@mr_monkey

[monkey] Going once
Going twice

@rob

[mayhem] SOLD for a bushel of bananas!

Staff/admin SSO

@julian45

basically: one infra security gap that would be great to close is that account management for staff/admin level resources is really disparate, and would benefit from being centralized in one identity provider, with single-sign-on (SSO) being used for all service providers that support it
i typed up a doc here that the team should read (anyone with an @MeB.org email should be able to read it and comment, let me know if you can’t), and i would like for us to hopefully come to a decision on what to do by next weekly meeting
https://docs.google.com/document/d/104GkkrAw3w3eBKX9vQICpafUEC5MpAI2ClwHJKfdl4Y/
doesn’t need to be read in full within the current meeting, but at the very least i hope we can collectively understand justification and options on the table
and yeah, it’s going to be a bit complicated to get set up, at least initially, but in the medium & long term it should significantly ease managing user accounts & access to services that we rely on to run MeB projects
i welcome comments in here & on the google doc!

Absent: Gautam Shorewala (1), lucifer (1)