# Notes from #MetaBrainz Meeting 2023-03-20 **URL:** \ **Category:** MetaBrainz\ **Tags:** metabrainz-meeting-notes\ **Created:** [March 20, 2023, 7:03pm UTC](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-20/628950 "2023-03-20T19:03:07Z")\ **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:** [March 20, 2023, 7:03pm UTC](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-20/628950/1 "2023-03-20T19:03:07Z")
# #MetaBrainz Meeting 2023-03-20 Meeting start: [IRC Logs for #metabrainz | MetaBrainz Chatlogs](https://chatlogs.metabrainz.org/libera/metabrainz/msg/5148333/) Meeting wiki page: [MetaBrainz Meeting - MusicBrainz Wiki](https://wiki.musicbrainz.org/MetaBrainz_Meeting) ## Agenda - [Reviews](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-20/628950#reviews) - [April](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-20/628950#april) _Last meeting: [2023-03-13](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-13/627961)_ _Next meeting: [2023-03-27](https://community.metabrainz.org/t/notes-from-metabrainz-meeting-2023-03-27/630125)_ ## Reviews > [@snaekboi](#): > > Last week was surprisingly productive šŸ”„ > I was able to collaborate with reosarevok and finally figure out some action steps for the areas management project in MusicBrainz > I also started a new PR with some feature additions šŸ˜ > OMW to getting all of it reviewed, and figuring out the rest of the projects throughout this week > [@yvanzo](#): > > I donā€™t remember much about last week, possibly due to the long celebration week-end. > Helped with finalizing the announcement for the MusicBrainz database schema change in May. > Worked on the Flow types refactoring and spam report WIP, plus some usual stuff: > Reviewed pull requests, debugged aliases editing, monitored security alerts, triaged ticketsā€¦ > Fin. And the SEC Award of the week goes toā€¦ monkey! > [@mr\_monkey](#): > > last week I spent entirely too much time on updating our test runner (jest) in LB, and looking at our migration path to replace the React testing library (enzyme) that we use with it. > I also finished replacing our modal components in LB. We should now have all features available on all listenCards across the website > I continued with the LB redesign, which you can get a rough preview of on [test.listenbrainz.org](http://test.listenbrainz.org/) > Ah, and along with the modal thing I mentioned, started working on [LB-1148](https://tickets.metabrainz.org/browse/LB-1148) as well > I spent a tiny bit of time looking into how we could add user avatars to LB. What do people think of Gravatar? [followed by a flood of outcry and lols from others, monkey clarifies that this is a joke, [MBS-9725](https://tickets.metabrainz.org/browse/MBS-9725) is mentioned (using Discourse avatars in MB)] > On the BookBrainz front I reviewed guidelines in progress, and reviewed lots of PRs > And finally, a bit of SECurity tickets and reviews of related PRs. In particular updating a dependency of our ORM (which is pretty much abandoned) > And a bit of welcoming and orienting GSOC participants šŸ™‚ > [@reosarevok](#): > > This week I did some more code reviews, I released beta / prod > I started working on the still not ready schema change tickets > I dealt with a bunch of user reports > And I took minutes for the MeB board meeting > Until the end of the week Iā€™m hoping to get those schema change tickets as ready as possible > And then on Sunday Iā€™m flying off to Spain, and Iā€™ll be there for two and a half weeks still doing some work but hopefully not a lot > [@CatQuest](#): > > Working on [https://tickets.metabrainz.org/browse/INST-1067](https://tickets.metabrainz.org/browse/INST-1067) > this week is also Ostara so Iā€™ll be on and offā€‹ā™“ > [@zas](#): > > last week I worked on supporting cgroupv2 on servers in order to allow better disk I/O control in docker (requested by yvanzo, added to ansible by atj) > I also upgraded discourse (and today listenbrainz plugin for it) > plus Picard PRs reviews, supervision, and usual stuff. > [@aerozol](#): > > Mainly working on the LB redesign, a bit of guideline stuff again > The usual little bits and pieces > Iā€™ve had other stuff piling up so I might take it easy on MeB work this week - as always, please do nudge me if youā€™re waiting on something you want asap! > [@jasjeet](#): > > Last week was filled with exams ā˜¹ > But still got in some work on refactoring login screen of the app > fixed all the tests > and poked akshaaatt once in a while > [@riksucks](#): > > Hey, nothing to report so far folks šŸ™‚ hope you are all well > [@akshaaatt](#): > > I was mostly improving my knowledge base last week. Looking a lot into deep linking for the app. Also, I got jealous of an app which lucifer shared and geared up for us [[Kiwi](https://www.wishroll.co/)?] > Had a look at jasje ā€˜s SoC proposal and misc stuff > [@bitmap](#): > > last week I finished working on bugfix [MBS-12976](https://tickets.metabrainz.org/browse/MBS-12976) (which was released today) > helped refactor [https://github.com/metabrainz/musicbrainz-serveā€¦](https://github.com/metabrainz/musicbrainz-server/pull/2890) to reduce some code duplication > on tuesday I hot-fixed a mess I made related to alias caching (after deploying a change to beta) > later helped write the schema change blog post, and started writing a design document for the next JSON dumps implementation > (plus worked a bit on the branch for it) > and also did some code review > [@lucifer](#): > > last week i went through sentry and worked on fixing misc bugs i found there. > also worked on fixing daily jams and migrating the listens table schema (still a WIP). > finally, switched and monitored the rabbitmq library in api from pika to kombu and it went nicely. > [@rob](#): > > on monday I spent the day cooped up in a looong metal tube. > and if you want to guess where I ended up, I post clues to my instagram: [https://www.instagram.com/mayhemcha0s/](https://www.instagram.com/mayhemcha0s/) > monkey already found me, I made one bad screw up in one of the pictures. > [private/PM guesses only] > then I did some PR reviews, eating local food, answering emails, local drinks, prepping for the board meeting. > the board meeting was really good ā€“ weā€™re getting very good feedback and questions from the board. > Matthew suggested that we put all of our data sets behind a sign-up page so that we can track more of the people who are using our data. > and that is not a hard sign-up page. weā€™d still have the datasets on the ftp sites and what not. > but all the links to download data sets should ideally point to the [new metabrainz data sets page](https://test.metabrainz.org/datasets) > and from there, we capture the info for the people and immediately green-light non commercial customers. > and commercial customers may need to get approved first. > this way we gain more insight as to who is using our data, and not just for the MB live data feed > if anyone sees any problems with this, please ping me after the meeting. > I also started working on a new MBID mapping detuning engine, getting my regexp chops up to speed. > [@kellnerd](#): > > Last week, Iā€™ve been working on [SEC-999](https://tickets.metabrainz.org/browse/SEC-999) / [BB-731](https://tickets.metabrainz.org/browse/BB-731), thatā€™s the one which monkey also mentioned. > Currently weā€™re stuck on a horribly outdated version of that, because our ORM (Bookshelf.js) forces us to use knex \<0.22 and hasnā€™t received updates for three yearsā€¦ > So we have created our own fork ([Update Knex to v2.4.2 & Run npm audit by kellnerd Ā· Pull Request #1 Ā· bookbrainz/bookshelf Ā· GitHub](https://github.com/bookbrainz/bookshelf/pull/1)) to give us more time to migrate to a different ORM ([BB-729](https://tickets.metabrainz.org/browse/BB-729)). > And today Iā€™ve finally continued working on [BB-530](https://tickets.metabrainz.org/browse/BB-530) and started to implement caching of Wikipedia API responses in Redis. > [@atj](#): > > last week i worked on adding some grub configuration to ansible so we can enable cgroupv2 indocker > i also continued working on the role for deploying borgmatic, hopefully will have something usable this week > [@jivteshs20](#): > > So last week was busy with my exams ā˜¹ > Apart from that was cooking some mockups for add album ## April > [@](#): > > April is still coming, it turns out Absent regulars: nobody!