Notes from #MetaBrainz Meeting 2024-01-29

[aerozol]

#MetaBrainz Meeting 2024-01-29

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

Agenda

• Reviews
• Dropping MB Commons Code
• IRC alternatives
• Summit 2024

Last meeting: 2024-01-22
Next meeting: 2024-02-05

@reosarevok: Welcome to a slightly delayed Monday Meeting!

Reviews

@Pranavkonidena

[mailed in] Last week I mostly worked on giving final finishes to YIM on LB android. Fixed 1-2 issues.
Got feedback from mayhem and monkey reg YIM today. Will try to have a meet with Akshat and see what all needs to be done further.
Apart from that I am working on getting all the features from the feed to the profile screen in the app as was suggested by jasje. By this weekend I should be done with that.

@rob

[mayhem] last week was the usual background stuff at MeB, but we did sign a new - the contract isn’t counter signed yet, so its not official yet.
I also worked with gcrk (he/him) from Funkwhale on the various packages that needed to be made to release troi and the content resolver.
this also meant that we renamed pylistenbrainz to liblistenbrainz, since we lost access to the pypi account. alas.
I made lots more progress on the content resolver, which is doing a good job… resolving playlists. feels great to get here.
I also wrote a new parser for lb-radio since the PyParsing error messages could only ever be loved by geeks.
so now we have a simpliefied syntax and a new parser that was made possible by the simpler syntax. with much better error messages.

@mr_monkey

[monkey] Last week I finished some Docsprint taks I had in progress for BookBrainz
I helped ansh finish up the music neighborhood feature for LB, which is now out in beta (and pretty cool !): Music Neighborhood - ListenBrainz
Had some chats about LB development
And reviewed PRs for BB and LB.
And finally worked a bit on improving our (absence of) retry strategy in LB, currently we have some never ending loops of retries in a few places.

@CatQuest

[ApeKattQuest] Did [INST-1078: cimpoi], [INST-1014: Cabrette], [INST-988: Veuze] (with [INST-1028: Veuze] closed as a dupe)
Have also fixed some old transliteration errors with the help of [Transcription into Japanese - Wikipedia] and reo making queries
oh and also [INST-1085: piva]
Today I have basically worked on a single task: a lot of research about hungarian, polish, croatian, latvian bagpipes, wikipedia is a mess! but I think I have sorted out dudy vs duda vs dükozadas now I think.
more research is needed ot figure out how the german “bock” fits in
anyone reading this or the post after is welcome to tell em anythig they might know about such folk bagpipes
Still have a bequest for the frenchies: zas, yvanzo, monkey, anyone else lurking?
s’il te plait, a translation of Cromorne — Wikipédia ? the information here is more detailed and actually explains what it is, rather than the english one which basically just says “idk man”
no time limit, but please put it in a paste/snipplet/link and not directly in the chat.

@zas

Last week, we released Picard 2.11
We can now focus on Picard 3, which is a port to PyQt6, with new plugin system (WIP)
I also reviewed PRs for listenbrainz-content-resolver
plus usual system upgrades, supervision, user support, and minor tasks. fin. yvanzo?

@yvanzo

Not much to report about last week as I didn’t feel well, just a bit of PR reviews, background tests, tickets triage, and maintenance.

@anshgoyal31

[ansh] Last week I finished off the work for refactoring the frontend folder structure. I spent a good amount of time fighting with merge conflicts.
I had a wonderful meeting with monkey, where we discussed some of the pending PRs.
Then worked on some final changes for profile page SPA. I also worked on user dashboard SPA.
And worked on introducing ambient queues to BrainzPlayer.

@reosarevok

Last week I spent a lot of time banning around a thousand spammers from a file chaban sent of old unreported spam
Finished that today
I also helped ApeKattQuest with some instrument images, put out a beta server, started reviewing the existing Spanish lines for MB (to make them consistent before translating new ones)
Plus the usual small tickets, a lot of which are in said beta release
This week: more translation, tickets, testing the Event Art Archive, at least

@bitmap

last week I opened a pull request for the Event Art Archive to musicbrainz-server, and worked on a bunch of related changes in the artwork-redirect / artwork-indexer services
it is currently running on test.musicbrainz.org, if you’d like to test uploading event artwork (it doesn’t upload to archive.org)
if you find any issues just yell at me
I also worked on [MBS-13465: Prefer non-raw images when displaying front release group cover art] and did a small amount of code review

@akshaaatt

I’ve just been doing the usual stuff related to apps
Other than that, have a really busy life these days, which I don’t at all like, huh!

@lucifer

worked on diagnosing misc mapping related issues last week, helped a few new contributors get started and did some PR reviews.

@Sophist

Whilst there is a lull, can I give a plaudit to Philipp [@outsidecontext] for this work he just did on Picard - a user reported an issue, and within a day or so Philipp had fixed it. Of course this is not that uncommon in Metabrainz, but in the wider open source movement IME it is.

@kellnerd

Last week I wrote a Spotify Extended Streaming History importer for my elbisaur CLI.
It is not yet released as Spotify’s timestamps are not reliable and the dumps also contains partial listens which are not marked as skipped etc.
Since Spotify’s JSON does not include the track duration to compare the listening duration against, this probably requires some API lookups to solve realiably…
Using what I have so far, I have carefully imported my history for 2023 in small batches, making use of elbisaur’s filtering, preview and statistics features a lot.
I also did a new implementation of a broken older userscript feature to set recording dates in the MB release relationship editor (for all selected recordings).

@theflash

[theflash_] I’ve been restructuring yim on ios side.
Refactored some code and worked on suggested changes.

@snaekboi

[Pratha-Fish] Nothing much from me this week either
Building some playlist tools tho
Oh also, I realized I might have ADHD
That explains a lot of my behaviors. (Anyone aware about that stuff can help me maybe)
[reo: probably half the channel, but after the meeting : )]

@jasjeet

[jasje] last week was usual
fixing issues related to concurrency
released my own lib for preferences that lb app will be using!

@aerozol

Still very busy with other stuff, but staying on top of socials and a few other things
Lucy got covid so doing a bit of nursing at home, but I’ve dodged it so far (knock on wood)
Made a LB local logo
A few mockups for [LB-991: Listen card options are hard to click on mobile]

Dropping MB Commons Code

@reosarevok

So, while reviewing bitmap’s EAA code, I saw that we’re still keeping around all the Commons image display code
We just have it disabled
It seems fairly clear we’re not going to start using it again, if we haven’t yet
Any reason it shouldn’t just be dropped?

@yvanzo queried why we should remove it if it’s not causing any trouble - reo and yvan to discuss after the meeting.

IRC alternatives

Summary: Barring any unforeseen events, we will be moving to Matrix ‘officially’ (IRC will keep working).
@lucifer will install it properly on the new domain that @rob bought for our chat, and then we can update the wiki etc.

Summit 2024

@rob is waiting for a few more travel details and then can start executing.
Sightseeing and public toilets are discussed briefly.
See also: Summit 2024 wiki page

absent: atj (1)

[yvanzo]

@aerozol

Dropping MB Commons Code

For more context, see https://doctorow.medium.com/a-bug-in-early-creative-commons-licenses-has-enabled-a-new-breed-of-superpredator-5f6360713299