Notes from #MetaBrainz Meeting 2023-01-30

[aerozol]

Hola! I will be taking over meeting note duties while Freso is on break. Feedback welcome.

MetaBrainz Meeting 2023-01-30

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Draw a Dinosaur Monday!

Improve Your Kids Vocabulary With The Dinosaur Song

Agenda

• Reviews

Last meeting: 2023-01-23
Next meeting: 2023-02-06

Reviews

@mr_monkey

mailed in:
I did’t do a whole lot last week as I’ve been AFK.
I did finish up on some docweek tasks on Monday, closed a couple more SEC tickets and reviewed some PRs.
On Tuesday on the train I opened a couple of PRs for the very first tasks of the ListenBrainz redesign (only structural for now, combining some of our tabs).
I’m still in Paris dealing with a lot of family drama, grief and funeral. That’ll be the case for at least another week. Please hold the line.

@lucifer

I was mostly away last week. did a couple of PR reviews and small bug fixes for LB.

@aerozol

I spent a little bit making my late contribution to the doc sprint, creating a bunch of tutorial videos, which was going to take a day
[narrator: it did not take a day]
Turns out I knew much less than I thought about Picard, so those videos are still happening

@reosarevok

I spent most of last week looking into the documenting the artist API thing
Which is now kinda done at the basic level? I think? But more to go to make the schema and examples better
I also worked a bit on small patches for the relationship editor
And on improving my PRs by following the actual PR template to make them clearer and easier to review
(some done, a lot to go)

@CatQuest

continued looking at backlogs and such.
I’ve added several bagpipes and will continue doing that.
Another reminder to everyone that if you are interested in a bagpipe (esp ones listed under “IROM”) now’s your chance to create a (sub)ticket: https://tickets.metabrainz.org/browse/INST-773
make sure it’s not already in mb or already has a ticket in jira
also don’t add novelties or ones with no info available, but else. go wild!

@Pratha-Fish

I tried updating the IRC logs this week, but nothing more than that unfortunately
Trying to balance a ton of things at once, but I’ll be back soon

@alastairp

last week I was continuing on some docsprint things which turned into yak shaving. I wanted to write some sysadmin docs about brainzbot and chatlogs, and noticed that we didn’t have any backups for the logs database, and after a quick discussion with zas decided to go ahead and migrate the chatlogs app to the main metabrainz infra
along the way I pinged bitmap and he wrote a nice guide about how to create a new db in the main postgres cluster (thanks bitmap!), and Freso also wrote a brainzbot admin guide from the point of view of a moderator/admin (thanks Freso!)
that’s mostly done, and I should finish tomorrow. also on the weekend we had a dodgy listen break the LB queue, which I debugged with lucifer’s help, and started writing a help document to follow in case it happens again

@zas

last week, I did an attempt to upgrade discourse, which ended in an heavy mess, causing a downtime for few hours
I managed to restore the forums
but I couldn’t achieve the upgrade
so, I ordered a new server (mingus), in order to move discourse to it
the server is now configured, and I did a test today, which was successful.
With the help of bitmap, we cleaned up the production postgres db used by discourse, which had various issues preventing the full upgrade (many inconsistencies)
also I got rid of unused plugins that are incompatible with new version (those also caused a lot of issues)
the reason for the new server was to be able to test the new version upgrade, and move discourse to it afterwards to save money, and because current VM struggles at peak times since a while
apart that, I did usual supervision, PR reviews, user support, etc…
I plan to move to new discourse & server tomorrow

@rob

I spent time learning react and working on troi daily jam improvements.
I also started working on artist radio style recommendations – I think we have enough data now.
and the usual background MeB tasks.

@bitmap

last week I finished writing the React state management docs for musicbrainz-server & submitted a PR for that
I also documented in syswiki how to add/configure a new database in our postgres cluster, which was tested by alastairp
other than that I worked on resolving the issues/improvements people reported in MBS-11847, plus a few other related tickets (MBS-12834, MBS-12849, MBS-12850)
hoping to release all that to the beta server today
oh, and also briefly helped clean up some broken indexes in the discourse database

@yvanzo

Last week I kept up the Documarathon about MB Solr and MB URL mainly.
Also completed and sent a review of Weblate ToS after they resolved technical issues.
bitmap, reosarevok and I had a video call about getting the MB dev team back together.
It was informal, mostly about communication and common expectations.
We will have our first development meeting here on Thursday.
It will focus on delivering the relationship editor obviously.

@atj

not much to report, i assisted zas with some issues bootstrapping the new discourse server
and wrote a pr which zas had already created

@jasje

Last week i fixed 1 bug
1 Ui fix
and if we count 1 hour before this meeting as last week
2 bugs in total
not much going on since sentry is helping alot
and looking forward to implement ui tests (akshaaatt?)

@freso

So I dealt a bit with answering questions about BrainzBot as well as writing up some docs for some of the basic administration of it via its admin interface. I sent them to alastairp earlier, so hopefully they will go into syswiki or somewhere? Idk.
Also cleared up some uncertainties about the Discourse upgrade.
Spent some time looking at reports and flags etc. as well as just generally keeping an eye on IRC, forums, e-mail, etc.
Finally, I will hopefully start treatment next month, and I will be taking a longer leave of absence until the end of the year to give me time to try and focus on this, so this will be my last meeting for the foreseeable future.
If you have any process or thing that you would like me to document or grant access to, please e-mail me and I’ll do my best to get it dealt with tomorrow.