Notes from #MetaBrainz Meeting 2023-08-14

[aerozol]

MetaBrainz Meeting 2023-08-14

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

Agenda

• Reviews
• GSoC blog posts

Last meeting: 2023-08-07
Next meeting: 2023-08-21

@reosarevok: Welcome to another Monday meeting!
In the wise words of ApeKattQuest: “wait fuck is it monday uuhhh”

Reviews

@CatQuest

[ApeKattQuest] making a slow start at updating instruments and images, we had a very big storm here (a named weather) and a lot of people got evacuated, I’m safe♌

@snaekboi

[Pratha-Fish] Last week was kind of low key
Not a lot of work, but a ton of self reflection on my part. Re-thought about my project timeline for a while
Also worked on some of the comments on PR #4 on the musicbrainz-bot
And looks like Imma be eating your heads for 2 more months, as we’re planning a project extension : D

@vardansaini

[vscode_] So this week 1. I worked on testing the Apple Music Player integration.
2. I worked on adding the Apple Metadata Cache using the Apple Music API.
Currently, running behind schedule on this task but will try to pick up pace this week and complete it on time this week.

@jasjeet

[jasje] last week has been very productive
ive been spending 8+ hrs on perfecting things
and the new update for ListenBrainz Android is just around the corner
so stay tuned for that

@akshaaatt

Continuing on what jasje said, the upcoming update is going to be our biggest update so far. The feed will be out. And it’s massive.
Also a big UI revamp has also been there
monkey is looking forward to see it
Listens submission has been improved with more features
I made sure aerozol is happy with the designs. Feed is as expected and we have cleaned up other sections as well
Commendable work jasje! Awesome. I’m really happy
That’s pretty much it. We have both been in a hacking mode recently. Other than that I also got my visa sorted!

@mr_monkey

[monkey] Last week I waged an arduous and madness-inducing battle with our discontinued front-end testing harness Enzyme, hopefully for the last time.
I emerged victorious (able to merge LB#2534 [Refactor user feedback logic])…but at what cost? My sanity.
As a consequence today I worked on setting up a replacement (React testing library) and get to know how it works. So far it’s looking like a better way to write tests and it definitely works with React 18 and functional components, so that’s encouraging.
I also worked a bit on polishing up the beta LB Radio interface with mayhem (LB Radio - ListenBrainz), and reviewed/finished up a bunch of smaller PRs (thanks lucifer for doing a spontaneous PR cleanup day with me : D )

@kellnerd

Slow week from me this time on the GSoC front…
Last week I was still working on the BB type definitions a bit before my research project seized my attention.
In the previous weeks I had tried to work on both projects in parallel, but now that I’m working on the written draft for my research thesis, this does no longer work out effectively.
So I’ve asked monkey to pause my GSoC project for two weeks and get the research project done before fully focusing on GSoC again.
This most likely means I’ve nothing to report next week, but I’ll still be around for the meeting.

@yvanzo

Last week I mostly investigated some frequent warnings in server logs.
From that I found and partly fixed a display issue in cover art editing history.
Also investigated distributing MB archives’ disk usage over several directories/volumes/hosts.
Last, got the reply of MTCaptcha who are sponsoring us with a free Enterprise plan, thanks to them!
Plus usual support and tickets triage.

@zas

Last week I mainly did Picard PRs reviews, related to upcoming 2.9.1
I also upgraded Discourse, we need to decide about new navigation, poll reveals users prefer sidebar
I fixed an issue with some upgraded grafana dashboards
plus usual stuff, system upgrades, user support. fin. bitmap ?

@bitmap

last week I mostly did code review for MBS or musicbrainz-bot
worked a bit more on [pull 2982] and submitted an issue upstream for the eslint crash which luckily is being fixed soon
revived [pull 2747] and added a test, which is now on beta, so let us know if you encounter any login issues there
also investigated a few hosting-related issues (oom errors on pink and yandexbot queries bringing down the site, which I had to resolve by blocking requests to /instrument//recording listings)

@lucifer

last week, i worked on reviewing multiple PRs and giving final touches to existing PRs (popularity datasets, soundcloud player etc.). also some GSoC discussions and reviews. that’s it for me.

@vishalftw

[pixelpenguin] I completed the work on having Queries to be used in dropdown for similar results, Issue [LB-1249: Allow users to invoke new dataset hoster queries from results] and PR [pull 14]
With this task complete, only porting and testing from listenbrainzserver is left. I added source parameter for fetching results from listenbrainz server in this commit as well - [pull 2522]
Lastly, I began documenting all the basic changes for the project’s blog. Thanks to lucifer for all the help in getting the issues completed

@atj

Nothing to report this week.

@reosarevok

Last week I mostly dealt with URL handling code based on me looking at a lot of style requests for whitelists and whatnot
yvanzo reviewed those and most of them are now in beta
By the way: next week I’ll be away in Spain

[some discussion about who will run the meeting, mayhem will do it if they are around, but can’t guarantee it]

@rob

[mayhem] last week as pretty much all about the LB radio UI. we’ve made quite a few bug fixes and well as introducing new ones that poor lucifer has to deal with. sorry, lucifer .
but its been super fun to work on and I am doing more fixes, but starting to look more serious at content resolution and making playlists available on local collections.
but that will mostly need to wait, since week I’m half working (off tue/wed afternoon) and the 2 weeks following I will be on vacation in the pyrenees.
not much else going on.
well, except that poor jasje got rejected by payoneer and isn’t going to get paid for his gsoc due to a minor technicality. fucking payoneer.
so, this time I will pay the stipend, but going forward, students who fuck up the rules will be shit out of luck. we’ll have to warn the next batch of students. if there is a summer of code next year.

@ShivamAwasthi

Last week was very unproductive for me. I worked only on the last two days of the week.
I worked on writing some tests for relationship-types, started some work on identifier type editor, and made some improvements to the relationship type editor PR.
Apologies for not being able to attend the last meeting, I was on a flight and I forgot to send a mailed-in review also because of all the preparation for the shifting.
have shifted to a new city, and started my first job which has greatly affected my productivity, but hopefully it will be fixed soon when I will shift into a new apartment.

@arsh331

[arsh] So I was able to finish up the artist info panel for my project and now working on integrating it with the existing codebase
Overall I am happy as I was able to get quite a few things done
I will try to wrap up integrating with codebase and adding brainzplayer this week

GSoC blog posts

@rob

[mayhem] gsoc’ers, listen up!
we require all of you to write a blog post on our blog about your experience and progress during your time this summer.
so, you should be planning to write that very soon. when you’re nearly ready to post it, contact your mentor to organize a blog account and have your mentor review your blog post.
lucifer: remind me of the dates they are due again?
[lucifer: * 28th, for those who don’t have an extension]
so, if anyone has questions about this, now is the time to ask, otherwise ask your mentor.
[it is mentioned that mayhem and bitmap are the MeB org mentors]
I would suggest taking a look at our blog to look at past blog entries from other students for a guide on how they should look.

Absent: aerozol (1)