Notes from #MetaBrainz Meeting 2023-04-24

[aerozol]

MetaBrainz Meeting 2023-04-24

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

Agenda

• Reviews
• Community Logos/Icons
• Next Meeting
• 2023 Summit Date

Last meeting: 2023-04-17
Next meeting: None next week, returns on 2023-05-08

@reosarevok: Welcome to MetaBrainz Monday Madness

Reviews

@aerozol

[reo: Today we have one mailed in review, from aerozol who still doesn’t love us enough to wake up at 5AM (boo!)]
Another quiet week on the MeB front, but did a few bits.
I had a very productive meeting with monkey, where we followed up on LB app discussions I had the week before, with akshaaatt and jasje, as well as looking at the state of the LB web beta, which monkey is doing a blazing job on.
Then back to the LB app, jasje now has the sign-off needed to make some design/icon changes, and some new stuff as well. The app and the website are starting to align!
I got sucked into a ‘if I change this then I have to change this…’ hole with [MBH-542: Replace wiki favicon with updated MB logo]. I’ve completed new logo/icon sets for MetaBrainz Community / MetaBrainz Wiki / MetaBrainz Tickets.
We want to sanity check these new logos/icons with you, which is on the agenda for todays meeting. In my absence, my pretty assistant will lead that discussion.

@mr_monkey

Last week as aerozol mentioned I continued work on implementing the new LB desing. Some great feedback on the forums, now (I think) all addressed.
ast chance if you want to leave feedback !
I’m fighting with our test suite that’s preventing me from mergin a PR for [LB-1148: Listen Card: Distinguish ‘not mapped’ vs ‘mapped but no cover art’]
Had a productive planning discussion with mayhem about our roadmap for LB, continued today online
I looked into some details of the Youtube player and youtube APIs, trying to improve our search results. They have an internal YT Music API that gets us exactly the data we need, but we can’t really access it. A dead end I fear.
Also reviewed some PRs
On the BB front I continued discussing guidelines and started implementing some of the required changes
Reviewed GSOC documents and discussed with the team
And finally deployed a new version of the prod and beta websites

@yvanzo

Last week, I reviewed a fair amount of MBS PRs and updated beta MB.
I worked on fixing HTTP support for downloading search index dumps.
The bugfix release for musicbrainz-docker should be published today.

@rob

as already mentioned, we did some roadmap updating for LB, which was overdue.
I did the usual background tasks and a lot of coordination on a lot of fronts, including getting our GSoC proposals lined up, which we finished today. all ranked, ready for the slot allocation. glad to have THAT sorted!
I also made some progress on artist-radio work, where I implemented a python list called plist. instead of integer indexes, you can your percent indexes and percent slices.
which seems odd at first, but I can request the middle of a list by doing my_list[25:75].
totally unacceptable in just about anything other than recommendations for sloppy humans.
I also did more work on the datasets page and have gotten help from yvanzo, reosarevok, and lucifer, which is really saving my life on this life-force draining sort of project.
hopefully I can now finish that this week.

@zas

Last week I fixed a tricky issue with error pages on LB API service
I also fixed an issue with HTTP frontend to our FTP storage
pink & floyd are starting to lack of disk space, so I spent some time looking for hardware options, and plan the upgrade path
the cost of Intel servers of this class at Hetzner increased a lot, so I ponder moving to AMD, but Hetzner doesn’t provide hardware RAID option for those
that said, CPU / RAM / SSDs are much faster on those, and we don’t use much disk I/O (caching / memory)
apart that, Picard PRs reviews, user support, general maintenance & supervision as usual

@kellnerd

Not much to report for last week, mostly that the Wikipedia extract feature is finally in beta testing :0
Random example from the most recent revisions
Other than that, I’ve finished my userscript repo reorganisation process with the help of atj (see GitHub - kellnerd/userscript-bundler: Node.js tools to build userscripts and bookmarklets from ES modules if you plan to reuse code to write your own userscripts ; )

@reosarevok

Last week I ported another page to React (artist search when attaching discids), and looked into a bunch of PRs and updated them to be hopefully ready for merge
I had two discussions about GSoC projects
And helped mayhem a bit with datasets stuff
Today I fiddled with the font size in MB at the suggestion of aerozol (and santiagofn, and probably a lot of other people because the current default sucks) and tested it at 14px that seemingly does not break anything - feel free to play with it at https://test.musicbrainz.org
We might put it on beta soonish for more proper testing
And during the weekend I trampled through the muddy forest in rubber boots looking at animal poop and it was fun

@CatQuest

Been getting Dirty! : D
well with planting and shovelling dirt
In MB terms I’ve been working on adding aliases and images to things we added 1-2 week ago, getting at the end of that so expect great things this week!.
also I will be looking into Bookbrainz things since it’s About Time ™

@jasjeet

I’ve been looking to improve Listen Service for a while now.
got that on table this week
and have pumped out two prs related to that
total of 5 bugs solved were solved.
And its getting pretty close to other scrobbling alternatives.
not to mention you can now block other apps from scrobbling

@lucifer

Last week, I worked further on adding top listeners of artist/release group stats. I also worked on misc fixes around improving cover art coverage on LB website.
Then, I worked on storing MB Oauth refresh tokens in LB so that LB web can submit tags/ratings to MB in future.
Finally, worked on the datasets page improvements mayhem mentioned earlier.

@bitmap

last week I was mostly monitoring dbmirror2 replication logs on aretha and fixing any issues I found
there were a few crashes which I submitted some PRs for, some which took a while to debug, but nothing critical. the new packets are otherwise applying smoothly
the main issue was that the pending_keys file inside a small number of the packets was missing some table names, but I figured out why (and this file doesn’t contain any critical data – it can be derived from the pending_data file as long as the database has primary keys installed, which all mirrors should)
other than that, I did a small amount of code review and gsoc proposal review

@atj

last week I went down a bizarrely deep rabbit hole trying to work out why a supporter was unable to download from the FTP server
I also got sentry fully added to ansible, which was far more complex than it should have been
Plus general ansible role maintenance etc.

@riksucks

for the tagging, I played around with a new model that I recently read
and they claim to use less GPU for training things related to chunks of data
like, small chunks of data rather than large chunks like in ChatGPT

@jivteshs20

Was sick due to heatwave here in india
and preparing for my semester exams

Community Logos/Icons

@monkey

Since it’s 5:45 in the morning all the way on the other side of the planet, aerozol has entrusted me to stand in for him. [aerozol note: ‘trust’ is a strong word!]
He has been working on harmonizing our ‘secondary’ logos (i.e. not our main projects).
See [MBH-542: Replace wiki favicon with updated MB logo] and this github pull request for context. (also, 100 PRs for the design system already ‽)
These three new logos we wanted your input on are for Jira, Wiki and Discourse.
The main question is whether we should use the short or long form of these new logos; keep in mind we want to harmonize across projects, so we would rather not mix-and-match.
Long form

Short form

The main arguments for the short form is that they take a lot less space and fit a lot better (especially true for the community logo) and that they distinguish the websites better (the long form ones look identical for a bigger portion of the logo).
Both aerozol and myself prefer using the short form.
The main argument against using the short form, probably only relevant for the community logo, is that we shorten MetaBrainz to MB and thus it requires some minimal knowledge of where users are. We assume users on the wiki and Jira website know where they are and why.
So the main question put to the vote today is: short form or long form?
Thank you for coming to my TED talk.

Some people agreed that the short-form was better, but that it should be ‘MeBCommunity’ (and so on), instead of ‘MBCommunity’.

@yvanzo raised that the cons of using the long form (that it requires familiarity) is a strong enough con not too use the short form.

Further discussion to take place on the ticket.

Next Meeting

It was agreed to skip the next meeting, for International Workers Day, and return on 2023-05-08.

2023 Summit Date

@rob

So, I am proposing Oct 2-6 for our summit this time.
noting that we decided to move it to the week, rather than the weekend.
the GSoC summit is the weekend after, so it does not conflict.
does any one have conflicts on that date?

No conflicts reported, it’s agreed to have the summit from Oct 2-6, in Barcelona.

[UltimateRiff]

@reosarevok

Today I fiddled with the font size in MB at the suggestion of aerozol (and santiagofn, and probably a lot of other people because the current default sucks) and tested it at 14px that seemingly does not break anything

ooh~ that looks so much better~ I no longer have to get right up in my screen to read everything, lol

@lucifer

Last week, I worked further on adding top listeners of artist/release group stats. I also worked on misc fixes around improving cover art coverage on LB website.
Then, I worked on storing MB Oauth refresh tokens in LB so that LB web can submit tags/ratings to MB in future.

very much looking forward to these features~

---

also really digging the new logos~ I do almost prefer other W logo for the wiki, but maybe that’s just me…

[aerozol]

@UltimateRiff

also really digging the new logos~ I do almost prefer other W logo for the wiki, but maybe that’s just me…

Thanks!

Sorry, it’s a bit confusing - The high detail square logo is staying for the wiki. The favicon will change for the wiki, jira and forums. Jira and the forums will get new logos as well, to stay consistent.

[sound.and.vision]

icons/logos look nice

thanks for the font size adjustment, i can pull back on my zoom levels a bit now

[mfmeulenbelt]

I also use MusicBrainz zoomed in because of the small letters, but I still prefer the zoomed in look to having just bigger letters. Because all UI elements and all cover art are tiny on MusicBrainz.

[yvanzo]

@aerozol

People agreed that the short-form was better

Sorry but at best one or two persons quickly nod at what you two presented as the preferred option, most people didn’t even react, very likely because there was not much time left for the two next topics on the agenda. The time needed to read the text, which is slightly biased, was longer than the time for reacting to it. I will add further comments to the ticket MBH-542.

[aerozol]

@yvanzo

Sorry but at best one or two persons quickly nod at what you two presented as the preferred option

You are overestimating my preference for the short form, quite frankly.

I don’t write these notes with any bias, and I apologize for missing your comment right at the end. I’ve corrected the meeting notes now.

[jesus2099]

@aerozol

MeBCommunity

I didn’t understand where those would be shown but I find MeB quite cryptic and looks like Meh.
We don’t have enough room for MetaBrainz Community (with a space, also)?

Also I think I saw MetaBrainz Wiki mentionned, but for me it’s really a MusicBrainz Wiki, isn’t it?

wiki.musicbrainz.org

I have been using this Wiki without expecting stuff from outside MB, but maybe I just never realised…

[yvanzo]

I’m sure it wasn’t intentional, you even presented the pros and cons for each form. I rather assumed it was more likely an oversight, that’s why I provided some context especially the sequence of time which is easy to miss when reading from the back logs only. Sorry if my comment created any doubt about it.

My main worry was just that you might bury yourself into this…’ hole while there is likely no need to.

Thanks for correcting notes and more generally for posting weekly notes.

[aerozol]

@jesus2099

I have been using this Wiki without expecting stuff from outside MB, but maybe I just never realised…

I didn’t really realise either… the change to MeB colours will hopefully help the other projects feel more welcome on the wiki.

If anybody’s wondering, I’ve been advised that there are some server dependency issues that stop us from changing the wiki url. So it will remain ‘wiki.musicbrainz.org’ for the foreseeable future.