# Notes from #MetaBrainz Meeting 2024-11-11 **URL:** https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-11/723875 **Category:** MetaBrainz **Tags:** en, metabrainz-meeting-notes **Created:** [November 11, 2024, 6:42pm UTC](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-11/723875 "2024-11-11T18:42:23Z") **Posts on this page:** 1 **Page:** 1
### Author: ![aerozol](https://community.metabrainz.org/user_avatar/community.metabrainz.org/aerozol/32/116_2.png) [@aerozol](https://community.metabrainz.org/u/aerozol) #### Post date: [November 11, 2024, 6:42pm UTC](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-11/723875/1 "2024-11-11T18:42:23Z")
Meeting start: [IRC Logs for #metabrainz | MetaBrainz Chatlogs](https://chatlogs.metabrainz.org/libera/metabrainz/msg/5398130) Meeting wiki page: [MetaBrainz Meeting - MusicBrainz Wiki](https://wiki.musicbrainz.org/MetaBrainz_Meeting) ## Agenda - [Reviews](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-11/723875#reviews) _Last meeting: [2024-11-04](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-04/722709)_ _Next meeting: [2024-11-18](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2024-11-18/725070)_ _@reosarevok: Welcome to another MetaBrainz Monday Meeting!_ ## Reviews > [@yvanzo](#): > > [mailed in] Last week, I mainly worked on the upcoming - in two weeks from now - upgrade for MusicBrainz mirrors. > That includes producing/loading Solr 9 data dumps, and deploying mirrors through Docker Compose v2. > Plus code reviews, support and maintenance, as usual.2. 2. > [@akshaaatt](#): > > [mailed in] I am finally making my comeback now. Yay!! I worked on both our android and ios apps and have started to fix the road to production. Fixing some loose ends and hoping to bring both the latest updates to production soon with a blog post. Still some way to go on this front but the progress is happening! > Other than that I have fixed my schedule now finally and I now exist in the 5AM club lmao. I took good use of my jetlag to fix my schedule. But yeah this means that I now sleep by 9AM IST and it might be a while before you see me online for our weekly meets but feel free to mention me or reach out anytime on the channel! > [@lucifer](#): > > [mailed in] I worked on doing more testing OAuth on test deployments on our main infra and looked into a couple of misc. LB bugs. > [@Ashutosh\_Aswal](#): > > [mailed in] [yellowhatpro] I did check for some changes that I can make in melba. > Currently for getting edit data URLs we are using the JsonValue. Now I am working on using proper rust structs for the edit types, which is basically a better way than JsonValue > This one particular change was once suggested by rustynova earlier, and now I got the chance to implement it > [@jasjeet](#): > > [jasje] Last week, progressed on some refactor on dialogs (there are so many : ( ) > Looked at a user reported bug > Still need to investigate further > Couldnt do much else as schedule is tight for a month atleast. > [@mr\_monkey](#): > > [monkey] Last week I worked on donations and flairs on LB > Continuing this week > Had a look into the new LastFM importer and the small changes we need to make after some user feedback > Had our first LB team meeting to lay out our plans for the coming month > Had a good chat with zas as well about surfacing service status to users > And reviewed kellnerd’s work on his GSOC project, which has come to a close > And as usual some PR review, ticket triage and the like. > [@outsidecontext](#): > > Last week I did code reviews for Picard and plugins (still some reviewing open Todo, will get to this) and answered tickets. Also looked into code signing again > Looks like Azure Trusted Signing might be the easiest and cheapest solution. It’s in beta, but can be used. I wrote a bit more about this today in the Picard chat channel. > [[melatonin.dev/blog](https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/)] has some details > I’ll finally will discuss my results then with mayhem to get things setup > [@rob](#): > > [mayhem] last week was a pretty good week, save for wednesday when I was a bit… distracted. sigh. > but I managed to get technical work done, including opening two PRs for data/mapping issues in LB. I’m going to be focusing on various data bugs in the coming weeks, trying to get things in LB to be a little less brittle. > we’re planning for a new telegram channel for LB services, so that if something like stats, playlists or other things get outdated that we find out in telegram before our users complain. > and hopefully work to make things more stable over time. > last, but certainly not least, I’d like to introduce Julian Anderson, aka @julian45 . Like @atj 1. he volunteered to help us with sysadmin tasks, in particular more ansible work and probably also working on the backup of CAA. > we’ve signed the typical 1 USD/year contract, so that he can have access to our servers. > [@kellnerd](#): > > Last week I finished my GSoC blog post: [[blog post](https://blog.metabrainz.org/2024/11/06/gsoc-2024-integrating-imports-into-bookbrainz/)] > Got back to some behind the scenes improvements for Harmony (like ensuring that all MB API requests set a user agent). > I was able to close some tickets, but also created a few new ones to keep the balance 😅 > This week I will try to update the OpenLibrary importer to make use of relationships, now that they are supported. > [reo asks if we can import things yet] The pull requests are not merged yet, so you can only import into a dev server so far. > And either without rels or you have to write your own importer which already does that. > [@zas](#): > > Last week I worked on updating our docker openresty image, since they finally released a version supporting openssl 3.x > [[OpenResty - OpenResty 1.27.1.1 Released](https://openresty.org/en/ann-1027001001.html#version-highlights)] > I updated the Dockerfile since the build system changed a bit > Apart that, I did Picard PRs code reviews, investigated an issue related to zfs/linux kernel which was initially thought to be a a Picard bug > [@anshgoyal31](#): > > [ansh] Last week, I focused on adding user flairs all over the LB website. > I also worked on improving the performance of fuzzy-search for Apple Music, addressing tickets related to album art, and the donors page. > And, I spent some time to address the review comments on a couple of my PRs. > [@aerozol](#): > > Last week I made [a sneaky post](https://www.reddit.com/r/lastfm/comments/1gjyguz/listenbrainz_new_lastfm_sync_option/) over on the last.fm reddit page, which took off more than expected > I ended up doing a lot of user support/posting/making new tickets as a result, much more than usual > Apart from that, just the usual > Things are quiet so I will post the “weird releases in MB” blog post after the meeting, if nobody has objections by then > [@derat](#): > > i sent [[MBS-13806: Avoid uppercasing "mi" and "mix" as Roman numerals by derat · Pull Request #3406 · metabrainz/musicbrainz-server · GitHub](https://github.com/metabrainz/musicbrainz-server/pull/3406)], a tiny change to make “guess case” stop uppercasing “mi” as roman numerals for MBS-13806; it still needs to be merged > [[MBS-13806: Stop uppercasing Spanish “mi” as Roman numerals](https://tickets.metabrainz.org/browse/MBS-13806)] > i also finished marking all e-onkyo links as ended for MBBE-90 > [[MBBE-90: Mark e-onkyo links as ended](https://tickets.metabrainz.org/browse/MBBE-90)] > and i added support to yambs for bulk-creating edits against all recordings in an existing release, to make it slightly less tedious to add disambiguations to live bootlegs or follow the CSG. it’s not exposed through the web interface yet > [@ApeKattQuest\_MonkeyPython](#): > > [LupinIII] Have written out the outline for work on the gopi/ektar/tumbi > These are 3-4 different instruments (with the tuntuna and the khamak messed into it) > and am working on it As We Speak : D > otherwise I’ll be doing ofline stuff like painting a gorram window lol > hopefully i’ll be done with that by the end of the week > [@bitmap](#): > > last week I got our tests passing on GitHub Actions after much debugging (then broke them again) > so far I’ve converted the tests Dockerfile to a multi-stage build, and have it building as part of the CI workflow. I also have a patch that splits the Selenium tests into multiple jobs, which will speed them up significantly > other than that I helped review a couple PRs and worked on some changes to [[pull 3269](https://github.com/metabrainz/musicbrainz-server/pull/3269)] which I’ll update today or tomorrow… > [@reosarevok](#): > > Last week I spent quite a bit of time trying to fix my code for proper UX for seeing and going to write reviews after we got another duplicate ticket complaining about it > And on a schema change ticket to make it so that characters cannot have end dates, as the guidelines request > Plus a bunch of small stuff as usual, and support and whatnot absent: rimskii (3) (removed from the regulars list, please readd yourself if you want to rejoin)