Notes from #MetaBrainz Meeting 2023-06-05

[aerozol]

MetaBrainz Meeting 2023-06-05

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

Agenda

• Reviews

Last meeting: 2023-05-29
Next meeting: 2023-06-12

@reosarevok: Monday is back!
So it’s again time to congregate and spread the good news of us not being total slackers

Reviews

@Vishalftw

I have started working on my project by exploring support for expressing inputs and outputs of DSH queries in form of pydantic classes.

@aerozol

Long weekend here, the week went so quick!
I did bits and pieces. Mainly sending out ~40 press releases, and scheduling follow up mails.
This was a bit of a test run of the new Marketing/Comms request form, and the press release template.
When we do new things from here on in I’m going to bug you to fill out the form, which should only take a few minutes.
I hope everyone will get used to doing a cool dev update/thing, filling out and sending me the form, and then being able to relax and move on.

@CatQuest

With the help of reo, fixed Quite a lot of Alias Locales!
(and also images from IROM)
This week I will be afk mostly, but I’ll be starting to finish up adding all the accordions

@ShivamAwasthi

last week I finally started working on my GSoC project
made the required database schema changes
since it didnt really involve a lot of brainstorming, so I started working on creating the frontend for Admin Panel too
Overall, good week 1 progess

@kellnerd

Hey all, I did the same (started my GSoC project).
Admittedly it was less exciting, I had to update npm dependencies which were last touched back in 2018
Now that I’ve done that and setup RabbitMQ I can finally start with the real work™

@mr_monkey

Last week I implemented aerozol’s designs for the new “Created for you” page on ListenBrainz that will replace the current recommendations page
With the help of mayhem as well. That took most of my time, but I think we’re pretty much done
I investigated listens submitters and updated our list.
Also worked on small tickets related to the “Missing MB data” page
Some discussiosn around listens submission and the ListenBrainz app, and the interplay of various submission strategies.

@yvanzo

Last week I completed balancing search indexes replica on MB SolrCloud nodes.
Then reviewed some MBS PRs for beta and some docker admin PRs for our systems.
Improved docker server configs documentation and applied it to all servers.
Further worked on setting up Weblate and migrating data from Transifex, it should be up this week!
Thanks a lot to outsidecontext for setting up Picard-related projects and for his data migration scripts.
Thanks also to aerozol who made a logo for our upcoming Weblate instance.
Here is the logo (second version)
(Note that the image size will be reduced to a square for use in favicon, navbar, bot, and email.)
It distantly derives from http://languageicon.org/ by using the Korean consonant Chieut - Wikipedia
Please send some feedback to aerozol on this channel after the meeting, he will check the chatlogs.
I will be off next week, until the 20th included.

@zas

this week we released Picard 2.9 Beta 1
I also worked on the consul migration preparation with atj
I made multiple big patches to Picard, mostly cleaning up / simplifying code
rudi server crashed on Saturday, and we got RAM replaced today, it seems to work fine now
plus usual MB edits, user support, and supervision.
[added later] we also switched to new gateways last week.

@rob

last week was hectic.
I’m negotiating two unicorn contracts right now, which is freaking amazing news.
also, the UK government excreted this turd [United Kingdom Industry Agreement on Music Streaming Metadata]
the Byta folks and I are working on a hit piece to talk shit about their ideas.
which are wildly unrealistic.
here and there I pretended to do some tech work with monkey, but too many interruptions.
also, spank^H^H^H^Htalking with the LIdarr team, and they awol community project dropped MB support from their project after we blocked them, so everyone is happy.
I’m sure there are things I am forgetting, the week was rather long with many many interruptions.
but overall with the marketing work from Rassami and Simon and these articles, we’re getting more visibility now.

@akshaaatt

I worked on the listen submitter, fixed it, and included submitting the playing now to LB on the app.
Kudos to jasje for fixing the submission metadata as well!
I got rid of all the legacy code we had in our repo and polished the app to only use jetpack compose.
yay!
Other than that, I have been constantly learning new things and cutting-edge tech along the way.

@snaekboi

I just got back home from a trip (a little later than expected ) and have started tackling issues as per the original GSoC proposal timeline (although I am running a little late, hopefully I’ll be back on track soon :))
Also started my daily journal as suggested by alastairp last year (and I’d highly recommend it to this year’s new GSoC joinees as well!)
Insult to injury I might have to travel AGAIN for a couple of days starting tomorrow (although I am trying my best to avoid it).
But overall, today involved setting stuff up and working on the new PR requirements on the MusicBrainz-Bot as suggested by bitmap

@jasjeet

last week was blurry
I completed unit tests and gave a deep thought of how to proceed with certain things before writing code
and that really took a toll on me
so after fixing listen metadata
i started playing games to relax myself
and now that im relaxed, im starting out to plan more stuff which will benefit the developers

@vardansaini

I don’t have any major updates this week, starting up with GSoC stuff and fixed the tests of tickets I was working on
will be finishing up more work by the end of this week

@bitmap

last week I was mostly on hosting-related tasks; helped with downtime for rebooting pink, floyd, & aretha and executing a primary database switchover
fixed some issues in our docker-server-configs scripts that prevented me from updating some MBS configuration during the switchover
fixed some barman configuration and cleaned up stale backups from the old primary
there was a weird issue with WAL files increasing over the weekend, but it resolved itself (possibly after I made some changes to replication slots)
other than that, I spent more time profiling JSON dumps, performing docker-postgres-cluster tests, and doing some code review

@lucifer

last week, I worked on churning out popularity datasets from MLHD data.
other than I worked on MeB OAuth stuff and some misc fixes.

@reosarevok

I wrote a fair amount more tests for our JavaScript functions (found at least one bug while doing that)
Also updated a bunch of React conversion PRs, rebasing them on current master since they were out of date, and testing them again more carefully (which found a couple bugs in the code for the PRs, and two or three old subjacent bugs)
Had our usual MBS team talk and submitted some changes to finally get rid of the mostly not-defined CoreEntity term (almost) everywhere
And dealt with autoeditor election stuff, including a PR to stop showing the list of voters updated as the election is happening
(since that’s kinda giving away who votes what if you make an effort to tell)

@arsh331

Last week was the first of the coding week for my gsoc project.
I spent time tinkering with the nivo library and was a able to put together a simple prototype for the same. Right now, I am exploring the artist similarity endpoint and getting the data from it.
I was looking at examples from the project itself and found some exciting uses. I am also working on processing the recieved data to build a network visualisation using nivo.
Overall, I believe am on the right track for my project and will be able to show a prototype for the network graph in a couple of days. That’s it from my side.

@atj

last week i worked with zas on the gateway migration, as well as a lot of testing and bug fixing for the consul migration
this involved lots of small updates to various roles and writing a new playbook to manage deploying the final configuration updates, stopping docker containers and restarting various daemons

@riksucks

recently caught up with vscode and helped him give him apple developer’s key so that he can work on his gsoc project

Absent: jivte (2)