Notes from #MetaBrainz Meeting 2023-02-27

[aerozol]

MetaBrainz Meeting 2023-02-27

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

Agenda

• Reviews
• MBS-9356
• libdiscid

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

Reviews

@yvanzo

Last week I kept working on beta relationship editor mostly.
Investigated release-blocking issues and addressed a few ones.
(Last issue of unknown impact is under active investigation by bitmap mainly.)
Plus support, small maintenance tasks (GoogleIndexing, Jira, Weblate…)

@jivte

So last week was pretty busy as my college is demanding attendance daily:|
And yeah I and monkey improved the add listen feature and is almost completed
Moreover had a nice conversation with aerozol about fresh releases UI/UX changes
Hope to talk today with mayhem abt the feature more if mayhem is free today

@mr_monkey

Last week on the LB front I finished maiming our Youtube player to satisfy their terms of services; hopefully we’ll get our quota increase now.
Also worked on improving the ListenCard layout and the missing MB data modal
And started working on the ListenBrainz redesign, actual CSS/visual stuff this time !
Also helped ongoing PRs
On the BookBrainz front, Helped on some guidelines and some other repo upkeep tasks
Started reviewing in depth the revision reverting PR (now on test.bookbrainz.org )
And deployed a new version fo the website
And some PR Reviews !
Lots of activity in BookBrainz at the moment, with all kinds of new contributors, both new and old : )
Nice to see !

@reosarevok

I worked a bit more on reports and whatnot, plus a lot of code review and making sure we’re ready for the relationship editor release which should hopefully happen today.
I also worked for a few hours on a kinda-sorta related issue to the relationship editor ones, MBS-12622, and on an issue to help me deal with spammers better, MBS-12902

@zas

Mailed in:
This week, I worked on setting up new backup disks and upgrading to new version of Borg. I ran multiple sanity checks, and copied all data from old disks to new ones. I also modified dashboard and alerts accordingly.
Plus usual supervision, upgrades, user support, PRs reviews and MB edits.

@CatQuest

unfortunately I got ill so I haven’t been doing much
but I did manage to add aliases for bagpipes

@Pratha-Fish

I went through some MusicBrainz projects and found the “Automate areas management in MusicBrainz” thing pretty interesting, and last week I went back and forth with reosarevok to try and understand the problem statement
Looking forward to exploring this project for a while

@bitmap

last week I finished working on MBS-12924 though the PR ended up causing some other subtle bugs and test failures I spent a few days fixing
so I think most of my hours last week were spent fixing or adding tests, working on improving the logging/build artifacts in our Selenium tests, and code review
later on I worked on a regression related to that ticket I first mentioned, MBS-12936, and also MBS-12937

@aerozol

I had my brother and niece visiting last week, and was going to ‘balance’ work with that
Not much got done and I’m definitely considering a vasectomy lolol
I did the usual stuff, a few interesting things with yvanzo bitmap and reosarevok around the relationship editor
MBS-12866 and MBS-12935 were interesting discussions and processes I thought, it’s all looking good. Really appreciating the attention to detail

@kellnerd

Hi, last week I worked on two new MB importer userscripts, mostly for my own niche (audio dramas and podcasts).
Then I started reviewing some BB PRs without being asked for it ; )
Last Friday, I’ve finally setup a BB dev server and worked on first PR today: BB-712
I plan to keep working on some small BB PRs and will probably apply for GSoC this year : )

@lucifer

last week i worked on adding release support to mbid mapper and improving the similar artists algorithm wrt to featuring artists.

@atj

Sadly nothing of substance to report from last week.

@akshaaatt

I’ve been welcoming new contributors and users to the LB android app lately!
Also, figuring things out in a more standard way. When it comes to app dev and releases, we can’t take things lightly
Besides that, I have a busy week currently because I’m planning to go on a vacation next week

@rob

last week was pretty rough for me personally so it was kinda slow on the work front.
I did some recommended track analysis to understand the results better, which was enlightening
I also did the usual biz dev stuff and helped zas with setting up a new drive array at the office.
and today I started working on a new react based explore page, so monkey and I can get the redesign underway.

MBS-9356

MBS-9356: Remove existing editors with no confirmed email and no OAuth tokens/edits/votes

@CatQuest said that it was important to check they don’t have any reviews or CB/LB accounts, @reosarevok confirmed that that was covered by checking they don’t have oauth tokens.

@reosarevok

So, we have a PR for that with a script and whatnot
I would like to run this in a week or two at most, because getting rid of a ton of potentially dormant spam accounts sounds like a good deal to me
(and then to start running it every week or two)
lucifer, mayhem, monkey: I understand that you can’t use LB/BB/CB without an OAuth token in MB, right?
Right now
So we don’t need any extra checks than “there’s a token” for that

@rdswift: Is there some sort of delay so that new users don’t get deleted if they just signed up and haven’t confirmed their email?
@reosarevok: this one runs only on one-year-old accounts
The idea was to then have a two-week grace period, but a month would be fine too really
(when we run it on cron)
@aerozol: I would maybe give it more space than 2 weeks, a month is good

@aerozol: This would clean up so much spam (do we need to add a notification for this, or change sign up text somewhere?)
@reosarevok: mayhem: should the login page mention unused accounts without an email will eventually get purged do you think?
@rob: sounds like a good idea. but will anyone read it?
@CatQuest: deff on the signup page
General agreement that we should have it and if nobody reads it it’s their fault, at least.

Conclusion:

@reosarevok

Ok, so the general idea seems fine still. yvanzo: please try to find some time to look at this in the next week or two (if you don’t manage, we can wait for you, don’t worry too much)

libdiscid

@outsidecontext

libdiscid: I’d like to put out a new release before CDs become totally obsolete Last release had been 6 years ago.
This is mostly about putting out updated source and binary packages. There have been a couple of fixes and updates to the build system over the years, but there is also added Haiku platform support.
I have made everything ready and setup the build system to produce all the release files. so basically all that is left is bumping the version numbers and tagging the release.
But I’ll need some support then to put the packages onto the MB file servers and transcluding the libdiscid Wiki page for libdiscid - MusicBrainz

@rob and @outsidecontext efficiently arranged to do this together tomorrow evening

---

Absent regulars: jasje (1)

[sound.and.vision]

@aerozol

MBS-9356: Remove existing editors with no confirmed email and no OAuth tokens/edits/votes

Hell yeah! Dump the spam into the void where it belongs