Notes from #MetaBrainz Meeting 2023-02-13

[aerozol]

#MetaBrainz Meeting 2023-02-13

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

As a reminder, we decided in the previous meeting that we’ll try to keep reviews quite free-flowing, so if you have a one-off joke (in moderation) or a brief question, feel free to ask (ideally after the reviewer is done). If it’s longer, let them know that you’d want to talk about something after the reviews end.

Agenda

• Reviews
• GSoC ideas pages

Last meeting: 2023-02-06
Next meeting: 2023-02-20

Reviews

@rob

last week I ended up going down a rabbit hole, building the lb content resolver.
its now working, but some improvements will need to be made still.
but it can already work as JSPF mime type handler, convert the playlist to local files and output an m3u.
I’ll see what it would take to automatically launch the system player to now play the playlist. which should make playlist resolution near invisible. [aerozol later asked for clarity, mayhem responded: “launching is meant that if you download a playlist file from a web page, it will open a player for you.”]
which is pretty cool.
I did the usual background metabrainz stuff as well, but a nice week focusing on coding things. 'twas lovely.

@reosarevok

This week I got rid of most of the remaining backlog of reports
Worked on some small improvements to the beta relationship editors
Worked on improving the autoselect (well, auto-restrict) options for some links, such as Soundcloud, Bandcamp, Apple Music
Added some more statistics
And other similar small bits in a reasonably large amount

@CatQuest

Working on adding instrument aliases
(oh, I helped CatQuest with some bagpipe images, too!)
will be finishing that this week as well as adding more bagpipes♑

@Pratha-Fish

Nothing special this week either

@bitmap

last week I worked on fixing various beta server issues - MBS-12874, MBS-12885, MBS-12870, MBS-12872, MBS-12882, MBS-12641
and spent time investigating some reported crashes, writing Selenium tests, testing/reviewing a few PRs
our tentative plan is to fix a few remaining beta issues that are not showstoppers but cause weird behavior, and release to production later this week
assuming we don’t get any additional reports that need to be addressed right away

@zas

this week, I most did tuning of discourse install, deployed a new plugin (listenbrainz, thanks to outsidecontext)
I also studied various approaches to centralized logging system, and I reach a point where I think there’s no good/simple solution.
This is something delaying deployment of new gateways, so I’ll run on one leg (as we do with kiki/herb), until we find a good way to centralized and merge logs, we still have enough capacity anyway
I also worked on backup system, we are lacking of diskspace, and it would be good to upgrade to latest borg version, plus adding backup machine to ansible
in short, a week with a lot of questions, and few answers, help welcome
apart that, I did usual supervision, upgrades, user support and MB edits.

@yvanzo

I worked on bugs related to big releases in the beta release relationship editor.
It also gave me some motivation to dive into the React state management stuff.
Plus SIR maintenance, PR reviews, tickets triage, support…

@mr_monkey

Last week I stayed a few more days in France because, surprise surprise, there was a big strike.
On Friday I looked into some new style guidelines for BB, reviewed some PRs, and looked into user feedback from LB users

@jasje

So last week i was quite free
i had already done part of my work
and just waiting for the merge
since i was free i started learning python
and now starting to get into flask
with the hopes of getting some action at lb server

@jivte_

So last week my wait for reviews ended
and monkey returned
I implemented the new changes in my pr and improved the codebase
Also
I was exploring metabrainz youtube channel
and encountered some amazing podcasts of monkey (link) and aerozol (link) with akshaaat

@akshaaatt

I have been reviewing PRs from jasje and another contributor on the android app
Also, learning quite a few things by myself
Taking a bit longer to make certain decisions. Also, we have been writing a doc about the app. Thanks to jasje for helping with that as well
Looking forward to speeding things for the app side. My vision is to wrap the LB android app by the end of this year. Let’s see if we can pull it off!

@lucifer

was mostly busy with academic stuff, last week so nothing to report.

@atj

not much to report as i was away for a few days, had a look at zas’ possible logging solution and errr…shot it down

@aerozol

Finished off all the tutorial videos for the YouTube channel, a big pile of them. Paused the Picard ones for now, just not knowledgeable enough
The usual stuff otherwise. Digging into some wiki/guideline pages - currently disambiguations and broadcast, gearing up for a well overdue soundtrack styleguide draft
Oh also, I wrote meeting notes for the first time, hopefully will be quicker this time

@reosarevok

I was looking at the comments on what to do with LB dupe(ish) users
And we don’t really know yet
Basically, we have a bunch of users who clearly have several accounts and listen to the same stuff (pretty much) with both
But they are not really spammers - it’s legit listens, just several accounts connected to the same Spotify or whatever
We don’t allow multiple accounts in MB unless there’s a clear reason (to run a bot or something) so technically these, by being the same people, are in breach of the MB rules [aerozol disagreed that this is in the rules/CoC, reosarevok said that this is similar to sockpuppets]
I guess for now we could get in touch with them and ask if they know / remember they have several accounts, maybe some are doing it by mistake
So the question in the document was “what happens if we cannot get in touch”
I guess we can start with getting in touch and seeing from there
So, I’ll do that and bring this up again once I know why some people do it

GSoC ideas pages

@rob

yvanzo: zas: outsidecontext: bitmap : akshaaatt: have you updated the ideas pages for your respective projects?
Development/Summer of Code/2023 - MusicBrainz Wiki
please do that soon as we might be accepted and have students invading soon.
I updated the LB one, but there might be one more I want to add, but that can wait until the meeting is done.
so, please update those pages.

Also:
@rdswift suggested we track who’s absent from meetings and remove them from the meetings > regulars list if they are away for a number of weeks and have forgotten to take themselves off the list. @reosarevok asked @aerozol to keep a list, so it will be added to the bottom of meeting notes starting… now.

Absent regulars: riksucks (1), yellowhatpro (1), vibhoo_24 (1)