Notes from #MetaBrainz Meeting 2021-09-13

[Freso]

#MetaBrainz Meeting 2021-09-13

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

R U OK? Monday

Tate McRae - r u ok (Official Video)

Agenda

• Reviews
• MBS-11938: Separate most autoselectable websites into their own relationships
• Invoices

Last meeting: 2021-09-06
Next meeting: 2021-09-20

Reviews

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

I finished the deployment of node exporter (metrics collector for prometheus), and tuned some alerts & graphs
I did usual maintenance, supervision, patches, and worked on Picard PRs (2.6.4 stable will be out soon, 2.7 alpha too)

@yyoung

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yyoung

Nothing much, just looking at some tickets, regular editing and making userscipts
Just finishing a project, new term is starting, and hopefully everything will come back on track this week

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I’ve mostly been working on a bunch of small URL cleanup changes (new URLs, better cleanup, plus a method to actually better match the favicons to the url so that she-ra.com doesn’t show the resident advisor logo because it contains “ra.co”)
Plus just updating a fair amount of open PRs based on comments / suggestions to put them on beta, since we have started using an actual milestone method again and getting a fair amount of reviews in

@CatQuest

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@CatQuest

not much this week, was in a slump… but things are looking up now!!
figured out that i actually can use atisket! so
!m @atj for that
otherwise trying to figure things out about a New Browser™:sparkles:

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Dealt with more reports, incl. a lot of spam (in MB and forums and a bit on LB all), did some forum admin stuff toggling options and looking into new features that turned out to not be available in our current version. I’ve set a reminder to look into it again for when we update to next version.
Other than that, being around and about.

@lucifer

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@lucifer

i worked mostly on sir debugging last week. followed up on some LB PRs, some spark debugging and misc stuff.

@alastairp

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@alastairp

last week seemed to run by really quickly
I tried a few times to upgrade sentry (our release is about 2 years old, and has some deprecated github integrations)
due to the way that our docker setup works, this was much more complex than I expected, though once I learned the right incantations things seemed to go better.
we’re currently upgraded from 9->10, though we still need to upgrade to the latest v21 release (in 2020 they moved to year-based versioning). I didn’t want to waste any more time on that so I’ve put it to the side for now
I did some LB reviews, and am finishing off a LB frontend PR that I opened before summer

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week I released a new version of musicbrainz-docker (ft. indexer’s bugfixes and improved development setup) at
Release v-2021-09-06 · metabrainz/musicbrainz-docker · GitHub
Also tried to address biweekly load issues on aretha due to MB dumps compression (will see next Wednesday if that worked).
Resumed reviewing MBS PRs using the new approach to milestones reosarevok mentioned.
Worked on SIR: Debug, Dockerfile, and service maintenance.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

last week we released a new MBS with @yyoung’s GSoC work (thanks again to @yyoung!)
I spent time debugging some out-of-memory errors in the MB webservice containers and found a nasty issue in the /ws/2/isrc endpoint that I hotfixed
& I also started working on MBS-10896 and MBS-10238 which are kinda related because they both require moving the email-sending functionality to ModBot (which would run more frequently, probably every 15 mins or so)
this is a schema change (since we need a way to track when edits were last processed in order to know whether to send out emails) but at least it only involves a non-replicated/internal-only table
other than that, I did some code review for the next MBS milestone

@rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@rob

last week was mostly catching up from vacation. loads of emails, random discussions, that stuff.
I also continued working on the MBID release mapper, which I asked feedback on here – it seems to be on track.
I’ll have to push that one forward this week, after I ponder how to continue.
today @mr_monkey and started working on a page that allows an LB user to see their feedback (love/hate)
because with similar users working well now, I’ve been listening to collections of my similar users and there is some good stuff. so discovery is starting to work, but once I find something, I can’t even <3 it or even find my <3s
so over the next few weeks I want to pick off little features here and there that allow us to close the loop making LB useful for music discovery – we’re quite close, so this is exciting.
and I’ve also been seeing more people talking about LB and tweeting that they have moved from last.fm to LB. which is a nice milestone to see.

@mr_monkey

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@mr_monkey

Last week I worked on a few improvements for ListenBrainz: submitting listens when played on the LB website, showing a play button on hovering over listens, and helping @lucifer with the LibreFM import page.
I also reviewed PR (mostly for LB) and did some testing of @akashgp09’s Series project for BookBrainz, as well as some general repo and CI tests housekeeping.
Finally I sat down with @rob to discuss summit t-shirt ideas. Excited to work on this again
Also got my 2nd vaccine jab over the weekend, so that’s done.

@akshaaatt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@akshaaatt

This week I realised I needed to code more so I dived in and worked on building components which we can use across all ours applications
I even completed two advanced courses on React which I feel was much needed.
I skimmed through the documentations for bootstrap and react very properly
Hopefully I can start making PRs to all projects this week and get our work going
Other than that I had a lot of college exams this past week. So that’s about it. I see amazing changes upcoming and it is really exciting!
And yeah,
The Android app now supports Light mode along with Dark mode!

MBS-11938: Separate most autoselectable websites into their own relationships

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

So, @yvanzo gave his reasoning there [on the ticket, —Freso]
I’d like people to take a look and see what they think
(I personally feel that bundling everything is not ideal, but I would be ok with that too if people prefer it - the current half-and-half seems like the worst of all 3 options)

There was some talk about technical implications of splitting out vs. combining and it was generally agreed that there were pros and cons for both and not a clear winner for either.

It was decided that the MusicBrainz team would discuss potentional implementations further to see if it’s be possible to get the “best of both worlds” for the downstream users.

Invoices

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@rob

we have some contractors who have a habit of not submitting invoices on time.
letting 4-5 of them pile up, and then submitting them in a batch.
which makes my life really difficult.
there is very little I can do to compel people to submit their invoices on time.
not like I can threaten to not pay it, can i?
@mr_monkey suggested putting the offenders into the meeting agenda as a reminder. they would have until that topic comes up to avoid being put on the spot.
that seems workable.
thoughts on that? other suggestions?

@reosarevok suggested “you could probably have a rule in contracts that says “for each day after X, 0,5% is discounted from the payment””, to which @rob responded “that’s evil. no.”

@Freso had some suggestions:

@Freso

My suggestions would be

1. explain why not getting the invoice in time is an issue organisationally (ie., how it’s more than just a nuisance for you personally),
2. either remind or ask contractors to set a reminder on the last day of the month that it’s (almost) invoice time, so they can either do it before the 1st or set time aside in their mind for the following day to do it,
3. recognise (e.g., thank) people when they do submit on time. (for positive reinforcement, rather than negative reinforcement of being shamed.)

@rob retorted that he’s “made it clear on a number of occasions why submitting invoices on time is important. and I really don’t want to be nagging people. do the contracts want to nag me to get paid?”

@rob then suggested that “if submission of invoice is X days late, payment will also be X days late.”

The item was left without resolution and postponed to next meeting, to see whether people would come up with additional ideas.