Notes from #MetaBrainz Meeting 2022-01-24

[Freso]

#MetaBrainz Meeting 2022-01-24

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

International Monday of Education

Suli Breaks - Why I Hate School But Love Education [Official Spoken Word Video]

Agenda

• Reviews
• Repo review

Last meeting: 2022-01-17
Next meeting: 2022-01-31

Reviews

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

last week I worked on updating some PRs to fix MB container warnings
and improving the MusicBrainzAlertDiagnostics.md doc in syswiki
I submitted a PR to enable logging of requests from MB website/web service containers to aid in handling alerts. that was for one of the review comments
and also submitted a patch to help the incremental sitemaps service recover from recent RG type updates. that’s already been deployed in prod
otherwise I was writing some docs about React state handling in MB, which @reosarevok mentioned was needed, and doing a bit of code review

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Among other things during last week’s doc sprint, I wrote and documented some scripts to repair SIR on queues alert.
The video call with a member of the Weblate team has been useful: lot of answers to technical questions; I forwarded hosting negociations to @rob.
@rob: (we have agreed, but communication is going slowly with them)
Plus usual maintenance, support, triage…

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I wrote a fair amount of docs for MB, also helped @CatQuest with the instrument one (still working on that) and got an area one from @drsaunde which I haven’t had time to check yet
Other than that, just updating PRs to get ready for beta release tonight

@CatQuest

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@CatQuest

I’ve been working on writing a documentation about how to add instruments
the first iteration was finished and is currently going through the @reosarevok treatement
else i’ve been looking at instruments, closing invalid ,etc

@lucifer

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@lucifer

I mostly worked on reorganizing and adding documentation to ListenBrainz last week. also updated/added tests to follow up on already open PRs.

@alastairp

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@alastairp

I did some docweek stuff, helped lucifer decide what to write in a few places, and reviewed his work. I also updated some syswiki things and cleaned up some MBH tickets
most of my time I continued looking at the BPM analysis that I was performing the previous week, resulting in BPM analysis.ipynb and BPM Batch.ipynb and I did a bit of reading about mood prediction of audio, which bought up an interesting paper which resulted in some discussions today with @rob and others about how we can collect annotations from MusicBrainz users

@rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@rob

last week was all about documentation.
I spent the bulk of the time devising a plan on how to pass the reigns of MeB to the team, should I… end up on the bottom of the indian ocean. with the banking token and my mobile phone.
what steps does the team need to take?
how does one recover passwords for all of the services we have?
What services do we have that are not already visible to the team?
What is our business dev philosophy?
I’ve devised a way in which @reosarevok and @Zas are both needed in order to take control over my accounts, the bank accounts and establish contact with our accountants.
it was equal parts depressing, a fun challenge and very tedious.
but I am very glad its done. I think our tram factor now hovers around 3.
Which is a drastic improvement from 1.
I also doled out updated contracts for most of the team and participated in another roundtable discussion for the ODI peer learning network.
boring, tedious, nearly all done.
and a big thanks to @zas and @reosarevok for taking on such critical roles in this. especially @reosarevok, since he now has to deal with our bank in cali.

@akshaaatt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@akshaaatt

My week started by brainstorming more mb revamp work and spending some time on the community forum. While at it, I got some important feedback that we first need to define a proper guideline about the design we are looking to use with detailing around the color scheme, font sizes etc. so that others can follow the same to help with the work.
This moved my attention towards the design system in place and I had a painful time updating and fixing it.
I also visited all our projects (including the likes of Picard!) and set them up locally to get started and see if there are any problems around the work and reported some.
CB took a hell of a time to get started!
Learned a lot of new stuff, which works great with what’s upcoming this week!

@mr_monkey

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@mr_monkey

Last week started with a long overdue transfer of the main BookBrainz repositories to the MetaBrainz Github organization
Then the rest of the week was working on documentation. There is so little in BookBrainz that there was ample choice.
I revived the developer docs and started documenting the schema and other aspects
Thanks to Shubh and ShivamAwasthi for giving me a hand on that
I also worked on the user guide , but haven’t polished that to commit it yet.
And finally helped a bit with the general communal syswiki/document-all-the-things effort

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

last week I didn’t do much, I was dealing with pretty bad family stuff
I kept an eye on stuff though
I fixed cert issue with wiki.mb
I fixed a nagios issue related to the removal of wiki previous VM (now totally gone)
plus various minor things and few edits, Picard PRs reviews.

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

A little bit of the usual, but also a fair bit of time working on documenting things related to Community Managing.
Also a chunk of time spent talking with @Rob and working on things related to that.

Repo review

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I brought this up during the week, but I took a look through our repo list and I listed on https://docs.google.com/document/d/1bl7xpNq3tDAbLfb6Riye_1bBa3QPNNiScK2CwCsE9MU/edit#heading=h.y5wbiakx98iw the ones that seem either to need a description to more easily understand what they are (a few) or just useless and in need of archiving away to clarify we’re not working on them at all (a fair amount)
@alastairp also contributed a list of repos (apparently mostly by @zas) that are not accessible by coreteam, and maybe should be
So if the team people have some time to take a look (no huge hurry, unless some of the hidden repos are very important to reduce @zas’ bus factor I guess) we could improve the state of the metabrainz repo a bit and make things more clear
I expect a lot of the repos need @zas, @rob and/or possibly @bitmap to check them and see if they’re indeed outdated and to be archived