Notes from #MetaBrainz Meeting 2025-04-07

[aerozol]

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

Agenda

• Reviews
• ChatBrainz downtime
• Jira upgrade w/ downtime

Last meeting: 2025-03-31
Next meeting: 2025-04-14

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

Reviews

@derat

[mailed in] I finished my change to add a bunch of documentation bubbles to the release editor for MBS-5944. It’ll hopefully go in soon (if it hasn’t already). : -)
[MBS-5944: Release editor: add documentation bubbles for extra fields]
I started working on similar updates to the artist form for MBS-13980.
[MBS-13980: Add more doc bubbles to user-facing forms]
(it hasn’t gone in already but I expect it will be in the next beta update, possibly tomorrow)

@RustyNova

[mailed in] * Last (two) weeks I tried to chase down the rabbit hole of a buggy test in the archiving part of Melba… And accidentally rewrote the whole thing.
I turned the notifier/listener into two polling tasks, an archiver that submit URLs to IA, and a status watcher that wait for finished archives
It should allow the process to be killed and resume from where it was, as well as doing multiple archiving requests concurrently.
A third task also handle cleaning up the timed out jobs so that the other tasks don’t pick a job just to reject it
I still need to restore the metrics, but I need to look into Prometheus first, and restore the tests, but the current mock server framework seems not able to properly mimic IA… So I need to dig into it

@reosarevok

Last week I worked on MBS-2349 and MBS-8668 and hopefully got the schema change ticket MBS-13768 more or less ready
[MBS-2349: Option to merge release groups when merging releases]
[MBS-8668: Adding duplicate entities to a series is still allowed]
[MBS-13768: Add MBIDs to mediums]
(I’m quite excited about recovering merging RGs with releases because I’m half of the time too lazy to do it at the moment)
Other than that, I looked at some style bits with aerozol who has been working on updating the podcasts / audiobooks guideline somewhat
(and might not be here despite sending no review since it’s 5 AM there, so consider this a bit of an aerozol fixup)
That’s about it for me, aside from the usual community bits

@rob

[mayhem] last week was a lot of finances and paying people. we finished the first quarter of 2025 in the black which is great, but its really just breaking even. I’ll continue to try and find more money in the next few weeks to see if can make a miracle happen.
then some managing gsoc proposals, but my favorite student has disappeared and I doubt that they will submit a proposal.
the new C++ based MBID mapping is making progress in strides. as long as you measure strides in millimeters, its perfect!
at least I think I have passed the worst of the work that needs doing. I think. I hope. please!

@anshgoyal31

[ansh] Last week, I was wrapping up work on upgrading LB to bootstrap 4. Started with upgrading LB to Bootstrap 5
Reviewed some PRs, and was mainly busy with GSoC Proposals

@mr_monkey

[monkey] Last week I was mainly busy reviewing PRs and proposals for GSOC
I also went over the Bootstrap4migration with a fine toothed comb
While testing each button and modal in the website it has given me time to reflect on the progress of ListenBrainz over the years. Feelsgoodman
Fixed a couple of issues in the user feed related to the new thank you events, which I’ve seen people using straight away which is quite nice
also helped mayhem with setting up LB mapping test cases

@kellnerd

This weekend I’ve created a settings page for Harmony to finally allow a bit of per user customization.
For starters I’ve made the behavior of the seeder configurable, whether it opens in a new tab and whether it should redirect to the Release Actions page after the import.
I’ve also integrated the already existing provider checkboxes and region input there. Now I wonder whether I should make these inputs not remember changes anymore on the home page?
Also read through a couple of GSoC proposals
Somehow I still only find time for MeB over the weekends, but research paper submission is this week, so it hopefully will get better.
I also contributed a few LB mapping test cases

@jasjeet

[jasje] Week was very good
Got a couple things done
Posted this yesterday:
Hey everyone, just published a 2.8.4-beta release that:

1. Fixes login.
2. Reduces app size from 28 MB to 11.4 MB! More than half a reduction in apl size, which is now less or aligns with any app that is of our category.
3. With this reduction in app size, we have enabled a bunch of bytecode optimisations, which should result in an overall performance boost.
4. Sentry is now integrated with our app, which should help in debugging some cases.

That summarises it. Also did gsoc proposal reviews.

@JadedBlueEyes

[jade] Hi everyone! I’m back from the grave university!
I’ve been writing up my GSoC stuff these past few days. I think most of the proposal is pretty solid
I’m still not sure if we’re going to use Rust or Python
Probably a topic for after we’ve done the updates?
Also planning my final year project out a bit, that may be very MusicBrainz themed! However, prioritising GSoC over that for now

@lucifer

last week i worked on generating similarity data from MLHD+, got a first cut of the data ready. reviewed a bunch of gsoc proposals. and also participated in the LB meet earlier today.

@bitmap

last week I was mostly finishing up some open PRs for the beta release, and doing code review for the same
there were a lot of JS changes on beta which caused a few bugs, but I deployed some fixes already (thanks to all who are testing)
also marked several thousand spammers in the DB (stumbled across them via the Sentry events we added for IPs creating multiple accounts per day)

@julian45

last week i looked at jira docs some more to gear up for a hopeful migration this week, which will require downtime - added to the agenda for a bit of discussion after reviews
in doing so i also converted some one-run-only-per-migration scripts yvanzo had made to idempotent ansible; although said scripts haven’t been maintained in a while, there was still some use to them. spending some time this week firming up playbooks for the migration and then doing it (hopefully)

@zas

Last week I reviewed some nice Picard PRs (pull 2613 was merged)
[PICARD-2287: Copy and Paste multiple Tags #2613]
Plus usual stuff, supervision, system upgrades, user support, blocking/unblocking, etc.

@ApeKattQuest_MonkeyPython

[ahvalmissaamine] This week I’ll be working on the toc, have working on a community post asking for examples and finally having a meeting wth monkey
I have finished the zine post and the spanish course (but will start sp2 later this month)
next week I’m taking time off!

@Ankit_Matth

Last week, I completely refined my GSoC proposal based on mentor’s feedback. Also updated BookBrainz PRs (#1163, #1162, #1160, #1159) as changes requested by the mentor.
[BB-843: Implemented new footer design #1163]
[BB-842: Display full BookBrainz logo on Home Page #1162]
[BB-841: Converted Promises to async/await in component pages #1160]
[BB-840: Refactor Promises syntax to async/await in forms components #1159]
Currently working on the prototype for the new CaliBre plugin.

@Gautam_coder

[GautamShorewala] This week I’ll be working on the toc, have working on a community post asking for examples and finally having a meeting wth monkey
I have finished the zine post and the spanish course (but will start sp2 later this month)
next week I’m taking time off!

ChatBrainz downtime

@lucifer

hi! i am planning to upgrade chatbrainz this week, most probably on wednesday unless a blocker comes up so expecting a downtime of 30-60 mins.
we don’t have a test environment to test the deployment before directly updating chatbrainz in prod so need to be a bit careful.
[some discussion clarifies that Matrix will be down, with IRC and Discord temporarily unbridged. Only IRC will be logged, with the Discord bridge possible backfilling (but unsure)]
i’ll post an update here on wednesday a few hours before starting the process.

Jira upgrade w/ downtime

@julian45

because the current jira server is on a quite old version of ubuntu and its java version (8) is too old for the version of jira we want to go to (17), my thinking was that it would be best to just migrate db/data to a fresh install of jira on a fresh ubuntu server
while this upgrade maybe could be made to happen in place, i think it’s less trouble than doing ubuntu 18 → 20 → 22 → 24 and jdk 8 → 17 in place
either way, this will require downtime since, even if transferring data and db from one server to another, activity on data/db must stop before the transfer begins
i’m thinking maybe a couple of hours of “downtime window”, even if not all of that ends up being used, is a good idea to take

@yvanzo

So for everyone, let’s say that Thursday might be without tickets for some hours.

absent: aerozol (1), outsidecontext (1)