Notes from #MetaBrainz Meeting 2023-09-11

[aerozol]

MetaBrainz Meeting 2023-09-11

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

Agenda

• Reviews
• New social channels

Last meeting: 2023-09-04
Next meeting: 2023-09-18

@reosarevok: A duck walked up to a MetaBrainz meeting
And he said to the man runnin’ the meeting
“Hey! Got any grapes?”

Reviews

@arsh331

[mailed in] It was my first week of university and busy with my classes. So couldn’t make any useful contributions. I guess it may take a couple of weeks to settle in and make some time.
But on the bright side a saw some activity on my PR and the project will soon be deployed on the beta site. That’s all from my side.

@yvanzo

[mailed in] Last week, I fixed an issue with the logger of MB background task containers.
Reviewed and released a CB update by ansh - thank you - to Node.js current LTS 20.
Updated MeB.o website to Node.js active LTS 18 and released it.
Reviewed a few MBS pull requests and updated beta.MB.o with those.
Plus some usual support and tickets triage.
I’m on vacation until the 19th of September.

@aerozol

[mailed in] Hi! I will still be busy with another job this week, but you can always ping me anyway.
Last week I stayed on top of the socials. Started another LB playlist to share. Worked on a LB release blog post with akshaaatt. Drafted a design form.
Someone else already had already done a bunch (outsidecontext?) <3 but I went back further through the blog, a couple of years, and added ‘read more’ buttons to break up long posts.
Please let me know if it bugs you if I mess with your posts like this.

@alastairp

hi everyone
just a comment to let everyone know that I’ve decided to move on and no longer be a contractor with MetaBrainz
however, not goodbye. I’m still in IRC! please say hi and talk to me whenever you want!
thanks for putting up with me everyone : ) Looking forward to seeing the contractor team in Barcelona during the summit anyway!
that’s it for now, but please say hi when you feel like it

@CatQuest

[ApeKattQuest] Figured out a duplicate ticket [INST-401: Tamboril]
Now working on [INST-1094: cobla] (and the necessary sub tickets) which also involves re-updating some of the earliest instruments I added back in '16
Then I’ll set about adding the remaining bug pipe tickets and writing a blogpost on that!

@snaekboi

[Pratha-Fish] Last week O ran some benchmarks to come across the fastest ways to fetch data from wikidata for our bot
Currently, I am OMW to standardize this process a little bit, and hopefully we’ll be closer to our project Target
I also tackled some old PR comments left by bitmap on PR 3 and 4

@bitmap

last week I mostly did some code review for musicbrainz-server and musicbrainz-bot
I also had to spend time setting up mb-solr natively on my laptop 'cause the docker setup broke
with that working, I was looking into [MBS-13021: Recording title changed to recording MBID url] again at the end of the week and trying to write a Selenium test that reproduces it

@zas

last week I was working with outsidecontext in order to get Picard 2.9.2 ready to release (we’ll release it tomorrow)
We also decided to do a 2.10 release soon after (maybe 2 weeks), because we had to fix an issue related to deprecated imp module for Picard to work with Python 3.12 (this will be the default Python in October in Fedora)
I also ordered and deployed a renewed certificate for *.musicbrainz.org
plus usual supervision, upgrades, MB edits, user support.

@rob

[mayhem] last week was my first week back from holidays, so there was a lot of catching up.
then I spent time on PRs, some summit planning and working LB-radio.
while LB radio is working well, it doesn’t scale well, so that is my current task.
I’ve worked out a plan for how to get lb-radio into local collections, which could be a huge. : )

@reosarevok

Last week I worked on a bunch of small tickets, including showing whether a user has been banned so that people don’t re-report by mistake
And I dealt with a few style issues, in an effort to deal with most recent tickets in some way or another while getting my inbox to zero again : )
Plus the usual support and reports
I also recovered from covid, which is nice - no long term effects so far
And talked a bit with Pratha-Fish about the GSoC project and Wikidata : )

@jasjeet

[jasje] last week i was figuring out testing
wrote some tests
refactored some code again

@akshaaatt

mayhem, jasje and I discussed the future of the app
Other than that, I am amazed by theflash_ who has been working on the LB iOS app!
Great stuff cooking there
Normal reviews and figuring things out

@mr_monkey

[monkey] Last week I finished the summit t-shirt design and started placing the order. Last step is mockup approval, and then they’ll be printed and shipped!
I worked on the stats art creator in LB which is now out in beta (alpha?): Art Creator - ListenBrainz
Feedback welcome : )
I also worked with mayhem to add a finite state machine to the ListenBrainz player to try and improve its stability.
It’s a bit more complicated than we thought at first, but we made some progress and it does have the potential of helping with unexpected failure cases. The jury is still out.
I also reviewed PRs and had a bit of GSOC discussion.
Hung out with alastairp for a bit
And finally I helped mayhem test LB Radio after-hours at the office, which was pretty fun!

@kellnerd

Last week monkey and I have decided that we rather want to have more frequent PRs and npm releases (if necessary) for my changes across multiple repos.
So I’ve revisited my previous working branches and cut two new PRs for bb-data (requires a new npm release) and bb-utils.
Unfortunately my productivity was slowed by Payoneer suddenly starting to annoy me with requests for “additional information” for a few days, luckily that seems to be resolved now.
As a compensation, I’ve finally upgraded my loyal old laptop from an HDD to an SSD for the summit, otherwise working on BB in BCN will be no fun

@atj

nothing to report again due to a full time work engagement.
I will hopefully have some time later this week to look at stuff that has been building up.

absent: ShivamAwasthi (1) vscode_ (3, removed from regulars list, please re-add yourself if you want to rejoin)

New social channels

@aerozol

[channelled by reo] I’ve been getting comfortable with managing the MeB social channels, and would now be happy to add more Twitter-likes to the list.
I am usually VERY wary of creating new comms channels, but in the current ’new sites everywhere’ climate I don’t think there’s much risk (e.g. I don’t think people will care if we close them again because there isn’t engagement or we can’t maintain them)
The benefit is giving people options to follow us for quick updates with having to use X.
ONE: How do people feel about me making, specifically, bluesky and fediverse MeB accounts? They and X would all post the same content/messages.
TWO (if the answer to 1 ‘yes’): If you want to be involved/have input in their creation please let me know this week. If you don’t then you are not allowed to complain later, please and thank you

Nobody minds so @aerozol is going to go ahead and make these channels.
It was additionally suggested by @akshaaatt that we should have an Instagram channel as well. Was encouraged to follow it up later/ask aerozol.

[UltimateRiff]

a lot of stuff in here I’m looking forward to in here~ I’ve already been using the art creator (thanks @aerozol for the early link~), and I believe I’m looking forward to ListenBrainz Radio in local collections? @rob does that mean like, getting Radio in local media players, like MusicBee, Foobar, Kodi, etc?

@aerozol

I am usually VERY wary of creating new comms channels, but in the current ’new sites everywhere’ climate I don’t think there’s much risk (e.g. I don’t think people will care if we close them again because there isn’t engagement or we can’t maintain them)
The benefit is giving people options to follow us for quick updates with having to use X.
ONE: How do people feel about me making, specifically, bluesky and fediverse MeB accounts? They and X would all post the same content/messages.
TWO (if the answer to 1 ‘yes’): If you want to be involved/have input in their creation please let me know this week. If you don’t then you are not allowed to complain later, please and thank you

an addendum to point one, I might recommend adding the Fediverse video hosting service PeerTube to the list? might be good to have that as a secondary to YouTube, in case something might happen there… (I guess it’s a pretty small chance, but then again, we all probably know what happened to X née Twitter)