Notes from #MetaBrainz Meeting 2023-11-06

[aerozol]

MetaBrainz Meeting 2023-11-06

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

Agenda

• Reviews
• Post-GSoC ideas

Last meeting: 2023-10-30
Next meeting: 2023-11-13

@reosarevok: Welcome to another MetaBrainz night! The day length is barely 8 hours, send help.

Reviews

@aerozol

[mailed in] The usual comms, moderation, socials.
Design-wise it was mainly pulling together designs for YIM 2023 - it’s not too late to feedback in the next day or so. But planning to finalize everything this week.
See the current mockups and figma link here: [LB-1178: Year in Music 2023]

@rob

[mayhem] well, last week I did some work. can’t even recall its been weeks since then.
but my mother appeared on wednesday and on friday we had the incident on LB where tests were run on the prouduction DB.
the weekend was not fun.
and there is a board meeting tonight, so things have been rough.
we’ve got lots of cleanup and preventative programming to do.
I also helped plan the delhi summit and the usual background stuff.

@yvanzo

I worked with lucifer and monkey on reviewing most of the overdue SEC tickets.
Only 4 alerts are left, requiring deeper work to get properly addressed!
Thanks also to akshaaatt, bitmap, mayhem, and zas, security reviews are otherwise up to date.

@akshaaatt

I got an eye infection and my right eye is completely swollen
Have been on bed rest for the last few days
Horrible. Surviving somehow : )

@CatQuest

[ApeKattQuest] my contention for crappy week!
I got ill last monday and spent most of hlloween just fekken sleeping
so sadly couldn’t do much
I’m still kinda ill

@snaekboi

[Pratha-Fish] This week has been suuuper fun! Probably the most productive week of my entire life with 15 hour workdays, crossing mental barriers with the GSoC project, speaking at some conferences, and pushing my limits in general. : )

1. Completed most of the goals we’d set for the Automating Area Management GSoC project!
   Some fun outcomes:
   We have a 60% (73,000 areas) Increase in the areas in MusicBrainz!
   We also updated 4,700 existing areas in MusicBrainz
2. Writing some more insights in the soon to be released blog for this project : )
3. Starting some preparation for the Delhi summit. Super excited :))
4. Spoke at yet another event, evangalized some gsoc opportunities at MetaBrainz. Collected some feedback on what barriers new contributors are facing when trying to contribute to MetaBrainz. (Hint: it’s the IRC channel)
   Lastly my laptop got cancer (water damnage). Homies slowly dying due to internal damage
   But overall still a great week nonetheless : )

@kellnerd

Hey there, the last week was also my last GSoC coding week, so I’ve worked really hard to get the essential features finished.
Of course there is still lot of room for improvements, but this means that repeated imports of pending entities can now replace previous data
I’ve also improved the logging output to make it clear what happened for each entity before I opened two final roll-up PRs.
And then I’ve tried to summarize my summer in a blog post (without sounding too negative): [blog post]
Thank you monkey and bitmap for checking it before I published it, all others are invited to read it and comment as well.

@mr_monkey

[monkey] Last week I had some GSoC discussions with kellnerd, it being the last coding week as he said
Worked on SECurity tickets and updating dependencies more generally
I worked on the LB entity pages which are coming along nicely
feelsgoodman.jpg
Also continued working on refactoring the LB test suite from Enzyme to RTL.
I also investigated instability issues with the CB websites

@lucifer

last week, i worked on resolving lots of SEC tickets for LB and CB.
on Thursday, LB database stalled for a while. we figured it might be extra load but apparently somehow tests were run against the production DB and the first thing tests do it reset the DB.
so we lost a large part of the data in it, the following 3 days mayhem and i spent countless recovering the data.
the listen data is now (except 18 hours of listens on Nov 2 :/) back.
a couple of tables still left to recover, will be working on that this week.
and also on improving the dumps/recovery mechanisms and adding safeguards to prevent this sort of thing from happening again.
also, ran some errands to find a good conference room for MeB summit [Delhi]. that’s it for me.

@reosarevok

This week I did some review, wrote a bunch of small fixes for recently-reported PRs, spent a fair amount of time dealing with reports
Looked at some style tickets
And looked through a fair amount of our strings to remove duplicates and make sure we try to use one word for each concept only
To make the life of translators easier
Probably more of that to go, every time I try to translate a bit I find something or other : )
But the main changes might be done now

@atj

last week I worked on a minor improvement to the ansible role for telegraf. alas it seems that the monitoring I was trying to implement isn’t supported by the smart plugin.
raside from that not much, reviewed a nice PR from zas and some other small bits and pieces
-r
Can I suggest we have a whip round to buy some drinks for lucifer at the summit? : )

@zas

last week I spent some time testing new version of keydb locally, and then I deploy it, it should fix the issue we had randomly with stuck process (since months)
for now, still unsure it is fixed, since the issue sometimes didn’t appear for 2 weeks, but according to changelog it should now be fixed (and apparently no side effect)
I report upstream in a week
apart that, I fixed some SEC issues (picard-website was redeployed)
and did some cleanup in syswiki, since a lot of scripts related to server setup are now obsolete (thanks to atj and Ansible)
fixed dashboards due to artwork-redirect containers name change
plus usual Picard stuff, user support, supervision, upgrades, MB edits.

@bitmap

beginning of last week I worked a bit more on expanding artwork-indexer test coverage, particularly for event art, and worked on the event-art-archive branch for musicbrainz-server
I resolved all artwork-redirect SEC issues and deployed a new version
upgraded Node.js to v20 in musicbrainz-server; as previously announced on the blog it will become the minimum supported version
at the same time I upgraded all of MB’s Docker base images to jammy, which caused a host of other issues I had to fix
later on in the week I did some code review, submitted a few PRs for issues I was looking at during the summit, and helped with setting up some python/mb-docker containers for Pratha-Fish on wolf

@jasjeet

[jasje] nothing to report in terms of work
preparing for delhi summit

@"anshgoyal31

[ansh] Last week I worked on adding pagination of fresh releases pages, to reduce the payload size and make the page loading faster.
Also worked on [LB-1264: Releases by “Various Artists” should not be included on “Fresh releases” page]. Other than that I worked on a BookBrainz ticket and opened a PR for that. I also spent time understanding playlists in LB, so that I can work a few tickets.
Couldn’t work much last week as I got stuck in some college work.

@arsh331 [arsh] removed from /regulars, as they have returned to uni

Post-GSoC ideas

@"CatQuest

[ApeKattQuest] * so I’ve had an idea, ye remember we talked about if gsoc coming to an end and us trying to maybe (if it so does) creating a replacement? and that that’s expensive and a BIG DEAL ™ and difficult and such?
but, if gsoc goes away, we can’t be the only ones who’ll miss it right?
how about an idea to partner with some other (F/OSS) projects?
atleast send out feelers to other projects we know who participate, what do they think?

@rob shared that at the 2023 GSoC mentor summit the announcement from Google was “that the 2024 program wasn’t quite ready for announcement. that they were still working on things.”

@yvanzo reminds everyone to write down their GSoC ideas in the wiki this month, and we can use those whether GSoC goes ahead or not.

@rob suggests that we should run our own program and sponsor our own students if GSoC goes away, and nothing good arises in its place, but that we should wait and see what happens.

Nobody objects to: wait and see, and we can look at partnering with friendly orgs when or if the time comes.

[rdswift]

It looks like somewhere along the line the list of absentees has been dropped. Is this intentional?

[UltimateRiff]

looks like arsh was the only one on the list, which was missing last week

[aerozol]

There just hasn’t been any absentees for a couple of meetings or so - the system works!

I’ll try remember to put ‘Absentees: none’ where applicable, so it’s clearer.

[rdswift]

@aerozol

There just hasn’t been any absentees for a couple of meetings or so

Wasn’t arsh AWOL this week? (Which resultred in them being removed from the list.)

[aerozol]

arsh’s removal is in the notes, under the Reviews section - they are back at uni

If there’s a better place to put absentees (e.g. at the start or at the end?) let me know and I will move it in future (edit: and in this one).

[rdswift]

@aerozol

If there’s a better place to put absentees

I’m not sure I really care. When I suggested tracking AWOL people and using the “three strikes and you’re out” criteria for automatically removing them from the list, the intent was to try to instill some accountability on the people that add themselves to the list for weekly reports, and to provide an open, transparent and fair mechanism for pruning inactive users from the list. Having no-shows on the list tends to waste everybody’s time by calling them and then waiting for a minute or two each only to find out that the’re not there.

[aerozol]

@rdswift

I’m not sure I really care

I ask because you missed it here

[Maxr1998]

@snaekboi

Spoke at yet another event, evangalized some gsoc opportunities at MetaBrainz. Collected some feedback on what barriers new contributors are facing when trying to contribute to MetaBrainz. (Hint: it’s the IRC channel)

Was it ever discussed to mirror the IRC to something like a Matrix/Element chat group? I believe Element is a bit more accessible than IRC, as it doesn’t require a bouncer, works on multiple devices and offers reliable background push notifications.

[aerozol]

Not in any official capacity, but if someone wants to volunteer to create mirrors to anywhere where it doesn’t require extra admin/moderation then I believe it would be very welcome (e.g. Discord, these forums).

p.s. requiring extra moderation would be probably fine too, but doing it via existing channels would probably require no discussion whatsoever