Notes from #MetaBrainz Meeting 2023-07-31

[aerozol]

MetaBrainz Meeting 2023-07-31

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

Agenda

• Reviews
• Discourse update

Last meeting: 2023-07-24
Next meeting: 2023-08-07

@reosarevok: It is Monday, and you are likely to be eaten by a grue.

Reviews

@CatQuest

(ApeKattQuest) Started sorting out the shawm/chalumeau/skalmeje mess
it is kinda a mess with terms being used all over the place and some instruments we do have and some we don’t. always it’s a bag of worms :D♋

@snaekboi

(Pratha-Fish) Worked on PR #3 and #4
Also working on creating scripts for actually fetching data for our project!
Finally fixed all the docker issues thanks to yvanzo
Also, had a short interview with Mayhem for a presentation at my university!
It’s all about metabrainz, our work culture, and how to join metabrainz : )
Hopefully sent to all 20k students in my batch
So expect some traffic probably : D

@rob

(mayhem) yes, I had a chat with Pratha-Fish and we recorded our call, since the last time doing a skype with india didnt work so well.
I also worked on lb-radio adding the user and recs elements and making various other improvements and refactorings.
a few PRs reviewed, some accounting stuff and the usual emails.
and today I started a react project to make a better UI for lb-radio. much thanks for your help monkey!

@mr_monkey

(monkey) I continued reviewing and discussing the ongoing GSOC projects. Some good progress being made.
I did some final touchups and merge conflict resolution for two big ListenBrainz PRs: the new Recommendations page and the vote tagging in Listening Now.
Finally I spent a good bit of the week working on the summit t-shirt design ! It’s the season

@bitmap

I worked on fixing how ssh keys are managed for docker-postgres-cluster, so that they’re copied into the container correctly after moving to bind mounts
I also ran some more query performance comparisons of pink and jimmy after some zfs changes. here are some examples if you’re interested [link]
the summary is that most of the slow queries I pulled from the pg logs are 20-25% faster
I also spent time on code review for musicbrainz-server and musicbrainz-bot

@zas

I handled yet another cpu fan failure on zappa, hetzner fixed it very quickly once again
I also upgraded discourse, there’s a new warning about a change we’ll need to discuss about → [link]
We released Picard 2.9, and I worked on reported issues related to this release
I re-deployed Picard website after we fixed few picard plugins to work with 2.9
The issue I reported about keydb is making some progress to a fix, as more and more people complain about it… but I still had to restart those processes last week few times
apart that, usual supervision, user support, upgrades

@lucifer

i worked on getting the popularity datasets PR ready for merge, ironed out an issue regarding lb radio tags dataset and worked on getting soundcloud player ready for testing.
also some PR reviews and discussions about pixelpenguin and vscode_'s GSoC projects

@reosarevok

I did a lot of dealing with user reports
Since chaban found a lot of spammy spammers adding spam edits
Other than that, I released beta (twice, since first yvanzo made a lot of reviews before his holiday and then we had a team meeting where we reviewed even more)
Dealt with a few style issues, updated PRs, stuff like that

@akshaaatt

I’ve been reviewing PRs and thinking through the next features we should work upon other than those already discussed
Been doing some research and been reading some papers behind the scenes
I’ll discuss more once my thought process is done

@kellnerd

I’ve addressed monkey’s feedback for my initial importer project PR.
Now we also try to extract the configuration for RabbitMQ from the config file (previously only configurable via command line args).
I’ve also ensured that the consumer can be force-quitted cleanly while the queue still contains pending imports. (There was no data loss, but the process could hang if a callback tried to confirm a message for an already closed queue).
Then I had to find a workaround to get Deno (whose npm compatibility is quite new) to use my locally checked-out version of an npm package.
Since npm link and soft linking did not work, the best solution was to simply copy my local build folder into Deno’s cache after each build step of the package : O
I’ve also started to improve the type definitions of our BB ORM, which included publishing a new version (with monkey’s help) of our Bookshelf (ORM lib) fork which includes (fixed) type definitions now.
Expect more of that stuff (and shuffling around currently duplicated code) next week : )
And I finally integrated the new features of Picard 2.9 into my tagger scripts and reported a bug related to that.

@jasjeet

(jasje) I covered the basic building blocks of feed ui
all the little quirks of feed were collected
and thrown into if else conditions
and rest
embodied peak polymorphism
this week feed ui should be stitched up and ready

@ShivamAwasthi

I worked on the Relationship Type Editor
I also created a Relationship Types Page, which lists all the existing relationship types

@arsh331

(arsh) I spent most of my last week fixing my code for the artist search feature
Quite a few things which were not so straightforward
But luckily it’s in a lot better shape
Began some work on the artist info panel and artist wiki part is all done
Hopefully will finish it up this week

Shared after the meeting, after briefly getting lost in the community-manager inbox:

@yvanzo

[mailed in] Happy Last Day of July!
I mostly reviewed some MBS PRs.
Also worked further on the registration form.
Debugged a few issues during the MB team meeting.
Plus maintenance, support and tickets triage.
(Reminder: I’m off this week.)

@aerozol

[mailed in] Kia ora koutou. I had a great time away, thanks for asking! Missed you xo
I stayed on top of general duties while I was on holiday, e.g. writing meeting notes, CB moderation, and monitoring and sharing to social channels.
I also sent some press releases, worked on a couple of tickets and mockups, had a few IRC discussions, and started a rather time consuming tidy of a guide doc (MBS-13146) [this was the wrong ticket, the correct one is MB-13176].
I have a bit of other client stuff to catch up on, but if you need something done give me a ping. Catch me while I’m still feeling re-invigorated and motivated

Submitted after:

@vardansaini

(vscode_) I worked on test and collecting data from apple music
to be a little more descriptive I worked on adding tests for Apple Music Player and started working on a standalone python script for gathering Apple Music Catalogue using their API.

Discourse Update

@zas

Discourse 3.2 will remove a feature we are currently using, changing the navigation a bit
Removing the legacy hamburger navigation menu option - announcements - Discourse Meta
“Your Discourse is currently using the ‘legacy’ navigation menu which will be removed in the first beta release of Discourse 3.2. Migrate to the new navigation menu by updating your navigation menu site setting to ‘sidebar’ or ‘header dropdown’.”

It is agreed that zas will ask the community for feedback in a thread, which now exists here: The legacy hamburger navigation menu option will be replaced