Notes from #MetaBrainz Meeting 2022-01-17

[Freso]

MetaBrainz Meeting 2022-01-17

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Martin Luther King, Jr. Monday

Martin Luther King, Jr. reads his "Letter from a Birmingham Jail"

Agenda

• Reviews
• Doc sprint

Last meeting: 2022-01-10
Next meeting: 2022-01-24

Reviews

@lucifer

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@lucifer

i worked on seeking and implementing feedback on various already open PRs last week. we deployed the long due listen user id PR. and started work on the next steps.
another long due PR to fix listen counts in LB also progressed along nicely. other than that, worked on a few improvement of the artist origins map. when hovering over the country, it now shows the artists name as well.
finally some misc bug fixes and discussions.

@mr_monkey

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@mr_monkey

Happy new year !
I just started working again today, so don’t have a lot to say about the past three weeks. I was vacationing in the US, got married, caught covid again, managed to get back after more delays.
Before the holidays, I mostly worked on the Year in Music project.
This week, docs for BB!

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

last week I was mainly working on speeding up area-related queries for the website, since we’ve been getting alerts about those pages causing excess load
my plan is to bring back area_containment, which was previously a view, but will be brought back as a materialized table. (those have worked amazingly for the artist pages)
I have most of the triggers done and am writing pgtap tests now
other than that that, I opened a couple other PRs to fix spammy warnings in our website container logs, and to remove support for Amazon cover art as decided last year (which lets us delete a ton of code, woohoo)

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I was on holiday and traveling for most of the week
Then I worked on a few easy tickets created while I was away
And now looking into some changes to the MBS-9356 script so we can run it

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

been working.
This week I will be working on documenting how I add instruments
try to work more and also do some instruments if I get the time

@akshaaatt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@akshaaatt

I had a nice week where I continued my work on MB web PR as per the guidance from @bitmap and fixed some of my open PRs in LB.
Also, I got in touch with around 5 people who are interested in contributing to GitHub - akshaaatt/musicbrainz-web-next: Web Application of MusicBrainz Revamp using Nextjs, which is good since they are helping fix some issues and adding to the revamp work by suggesting improved techniques and UI!
I am fine with it but have been pushing them to set up MB-server and contribute there as well.
My Linux machine crashed 3 days back so I had to wait a while to finish some changes, which I intend to do this week.
And yeah, I made 2 Mb android releases which drastically improve our playstore standing! Seems like a lot of new people coming in, excited!

@rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@rob

last week was spent doing accounting and invoicing and all that nonsense.
I also spoke with most of the team about raises, there are only 2 left, then I’ll be doing new contracts.
I also had to deal with some office stuff that took some time.
I reviewed some PRs for @lucifer as to get him unstuck from this mountain of PRs he hammered out.
and today I managed to get pretty far into the “oops, ED dropped off into the ocean, now what?” document. fun stuff.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

last week we released 2 versions of Picard, 2.7.2 followed by 2.7.3
those should be last 2.7.x (well…)
so we focused on preparing upcoming 2.8.x dev cycle, merging pending PRs, reviewing few more, etc…
then I battled a bit with crowdsec (I installed it to provide an extra level of protection vs log4j issue initially), but it happens it breaks on upgrades, I had to fix the mess on 2 machines using non default ports for it
I guess this will be fixed soon in new packages, but until them, messy
apart that, usual upgrades, supervision, edits, patches, bug reports.

@alastairp

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@alastairp

last week as @lucifer said we released the PR for user IDs in LB. I also spent a bit of time reviewing some LB prs to unblock @lucifer
I spent most of my time investigating the current state of the art in BPM recognition to see what options we have to improve the calculation of BPM in AB, I have 6 different algorithms working, and will run them across some collections of music to see how they differ
this morning I helped with outlining topics for pythonbrainz documentation. this week I hope to jump in and out of docs as needed, and mostly finish up on this bpm analysis

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week I got back at reviewing MBS PRs.
By the way, beta will be frozen on next Monday.
I worked on Weblate with outsidecontext about glossary, git workflow and MB OAuth2 support.
I will have a video call with a Weblate maintainer on tomorrow to see what can be done in details.
Finally, I wrote a summary of the discussion we had with @zas a month ago about system administration.
It includes a few suggestions, some of these can be (or already are) part of the current Doc sprint.
It is intended for everyone in the MeB team and mostly covers monitoring systems:
About system administration at MetaBrainz (December 2021) · GitHub

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Still trying to ween myself off of holidays mode, but I managed to catch up a bit on the forums last week, splitting some topics etc. as well as dealing with some flags and reports.

Doc sprint

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

It is just I noticed that some of the tasks being currently listed may require to gather everyone at the same time.
When do you want to do that? Tomorrow at 18:00 UTC? Or another day/time?

There was some discussion about what time suited people, who needed to be there, and what to discuss.

All MetaBrainz staff should be present—and any community members who wish to join in are also welcome.

The meeting will be held on Wednesday (2022-01-19) at 18:00 UTC (regular meeting time).