Notes from #MetaBrainz Meeting 2023-03-13

[aerozol]

#MetaBrainz Meeting 2023-03-13

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

Agenda

• Reviews
• April

Last meeting: 2023-03-06
Next meeting: 2023-03-20

Reviews

@rob

[mailed in:]
Last week I worked on the troi artist radio feature and the datasets page. Once Alastair finishes the mlhd+ set, we can release those pages.
Also discussions of UX revamp with monkey as well as various gsoc tasks and then the MeB background nonsense kept me busy.
I will be traveling until the 24th, but it is a working vacation, so I’ll still be online a lot.

@akshaaatt

I added Youtube music support to the LB android app and attempted to work with amazon music and apple music as well
Both amazon and apple are doable but will require some extra efforts
I’m planning to drop it because spotify+youtube might actually be it for us when it comes to streaming our listens on the app
Other than, lots of PR reviews and fiddling around with github stuff

@aerozol

This week I tidied up the Fresh Release mockups, bringing everything up to date and adding some stuff (mouse over/drag interactions, what happens when there’s no releases, etc)
Did a macOS icon update: PICARD-2620
Worked on the mobile navigation and subnavigation with monkey, getting there!
Got sucked into some more MB styleguide stuff, cool to see stuff happening there (even if it takes ages)

@atj

I carried on working on the ansible roles for borg and borgmatic this week. This mainly involved reading up on how the applications worked and also thinking about how best to orchestrate initialisation/configuration of remote backup repositories in a secure and usable way.

@bitmap

last week I finished the Flow upgrade in musicbrainz-server to 0.201.0, had a meeting about entity type naming and contributed to https://github.com/metabrainz/musicbrainz-serve…, and started working on MBS-12976
I also spent time on code review and looking into artwork-redirect security alerts

@reosarevok

Last week I reviewed some guidelines with derat and aerozol
I also worked with the team to improve flow types
Helped mayhem_ check and improve the datasets text
And worked on a plethora of smaller things, as usual
More of the same this week (and next), and going on a working-little break for two weeks or so after that

@CatQuest

Finished adding instrument aliases to things.
Did INST-1074: torupill
I’ll be looking at the backup of messages I’ve got this week

@zas

last week I worked on testing changes needed for MBH-581
I also read documentation of modsecurity for nginx, I’ll try to produce an openresty image for our gateways supporting it (it will be useful for new gateways)
apart that, usual stuff, upgrades, supervision, and handling few issues with servers
[yvanzo adds “You forgot to mention your early work on systemd cgroup for Docker containers.”]

@yvanzo

Last week I worked with bitmap and reosarevok on improving Flow types in MB Server.
This is needed preliminary step towards aligning terms about entity types in JS, Perl, and docs.
Also I resolved an issue with linking large images (such as DB schema diagrams) in WikiDocs.
Dealt with an incident about CheckVotes.pl stalling for more than an hour.
Finally I normalized ~20K URLs reported through MBBE tickets.
Plus usual support, tickets triage, PR reviews…
[later:] the SEC Award of the week goes to bitmap!
To be fair, monkey and lucifer have made progress too.

@kellnerd

Hey, this week I had a stab at improving BB ORM, i.e. replacing the very old, apparently unmaintained Bookshelf ORM library with something which has better TypeScript support and less outdated dependencies.
I’ve experimented with Objection (with which I had good experiences in a personal project) and started to convert a few data models (and even a test for one of them) as a proof of concept.
Other than that, I’ve improved the BB developer docs with a tip by yvanzo to make use of Docker Compose overrides.
This makes switching git branches less painful as one no longer has to stash uncommitted config changes, e.g. those to enable live reloading.
Also, my first minor improvement PRs got merged by monkey, yay
Next week I’ll have to finish the bigger Wikipedia feature PR and will probably continue with my ORM migration attempt

@mr_monkey

Last week I worked on a big refactor of all our modals in ListenBrainz, using the NiceModal react library to globally provide access to modals.
This allows us to backfill throughout the website functionality that relied on modals and was therefore missing on most pages (see LB-1170). See LB#2386 for context.
5 PRs down, one modal left to convert.
I also spent a lot of time wrestling with tests and more generally our test runner for React (Enzyme) which is pretty much abandoned and creating all sorts of issues. It’s not going to be fun to adapt the whole test suite.
On the BookBrainz front I reviewed a lot of PRs, so much activity at the moment !
And also continued following and facilitating guidelines discussions
Well, the discussions are being entirely led by @pbryan
I’m mostly just staying out of the way
And finally, lots of user onboarding, ticket triaging, etc.

@lucifer

last week i worked on fixing an issue which had blocked the listen queue. also a couple of improvements/bug fixes to mapping code.

@jasje

posted my new lb android update on community
trapped someone to use the app using my tactics :devil-face:
posted my gsoc proposal
anddd exams

@pratha-fish

This week was mostly spent in Holi and trying out whacky clothes for college festivities.
I am trying my best to catch up on the areas project too, but looks like I have been catching reosarevok at all the wrong times for asking questions lool. I’ll try to visit the IRC more often to find a suitable time to get my queries sorted I guess
Other than that I have been curiously eyeing the progress of the MLHD project that alastairp has been processing

April

@reosarevok

Only other topic in the list is the ghost of mayhem_ reminding people that APRIL FOOLS APPROACHES
So if people want to implement stuff or write stuff they should get started

Absent regulars: riksucks (2) jivte (1)