I've been working on instrument documentation, the page is basically done and now only will need flisespikkeri, thanks so much to resarevok for helping to rewrite my ramblings!
I hope to finish that up and have it uploaded to... wherever? :D
This week I will be working on instruments and tagging moar music
fin, next can be: zas
Last week, I worked mainly on Picard, PR reviews, patches, code cleanup
I was away for a personal reason on Tuesday
(Only yvanzo, mayhem and myself left for reviews. Last call for anyone else who wish to give review!)
We received a notice about hardware issue on clash, so we organized to move services from/to it to let me reboot and patch the issue (firmware)
that went smoothly thanks to everyone that participate
apart that, usual supervision, upgrades, user support, that's it for me. yvanzo ?
Some maintenance operations too last week: RabbitMQ move, SolrCloud 503s.
I improved the script I earlier submited to help with updating MB search indexes.
Submitted another script to collect logs for maintainers, now making it work for macOS too.
Looked into Solr 8 update, reviewed PRs, triaged tickets.
Also started deploying an MBS mirror instance for VolumIO.
Fin. Go mayhem!
last week was loads of AB discussions and LB roadmaps, contracts with atj and doing some hacking around recording similarity.
then I also hacked on LB's MB metadata cache and did a proof of concept of a standalone app that displays now playing info -- that looked quite promising.
today I prepped for our board meeting tomorrow and did more SQL hacking and stuff.
dseomn_ joined the channel
dseomn has quit
dseomn_ is now known as dseomn
I didn’t do all that much last week. Got my booster shot Tuesday and took Wed and Thurs off. I spent a bunch of time whacking spam accounts with the new flag on Friday. Thank you reosarevok and bitmap and yvanzo for getting that in. ❤️
Thank you all for your reviews!
We have a number of items on the agenda, so let’s get to it!
lucifer: GSoC Ideas List
it is that time of the year again, GSoC org applications have opened today. The deadline is Feb 21. We need to get an ideas list before that.
lucifer: I failed to respond to you earlier...
yes, remove AB for sure.
and keeping CB out is also good. let us convince ourselves that we want to keep CB before investing more in it.
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: Google Fonts: ORG-51 (lucifer), git branches auto-deletion (yvanzo), Valentine’s Day meeting? (Freso)
Yes, we also download and run JS scripts from third party vendors in Listenbrainz (spotify and youtube players) which I guess would fall under the same ruling
and with browser compartmentalization, the promise of the CDN weakens.
monkey: yes, we need to plan for that in the future.
IIRC MB already tries to avoid this stuff, bitmap specifically told akshaaatt to avoid it for Bootstrap
e.g. for stripe we cannot avoid it. thus we need to put a notice in place saying that in order to make a payment via strip we'll be downloading stripe code.
Can we move on to next topic and handle specifics outside of meeting? :)
I think one of the key items from that ruling was that "it's possible to self-host the font, therefore it's not 'strictly necessary'", which means that it's possible that hotlinking a js file _is_ necessary (as monkey has found before with versions changing)
Freso: yep, just got done. lets move on.
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: git branches auto-deletion (yvanzo), Valentine’s Day meeting? (Freso)
yvanzo: git branches auto-deletion
ah, mayhem said the same thing too
This is for repository maintainers.
There are a lot of obsolete branches wandering around.
they're just this branch, you know?
I know I have a ton locally, I try to delete them from github when merging though
It might make sense to enable the option “Automatically delete head branches” for most repositories, especially, the ones that have only one important branch.
Although I guess a lot of old ones are still there
For MBS, I’m not sure this is possible, given there is 'beta' and 'production'.
+1, also we already have that enabled for LB and CB iirc.
we have the delete turned on in LB, and some others
Would it be alright to enable it otherwise? (I think about syswiki, guidelines, metabrainz.org, etc.)
fine by me
I'll see for Picard, we have a lot of dead branches, but in general I think that's ok
For Picard it is probably not a good idea either indeed.
In general, if you have more than one important branch, don't enable it.
Can’t you mark more than one branch as protected?
Yes but I don't know the details of the auto-delete option.
i'mma head out, there 's nothing esle after this topic, right freso?
CatQuest is 🍲
Freso: Valentine’s Day meeting?
It's an invitation? :)
v-day party at freso's house!
Today’s the 7th and in 7 days it’ll be the 14th. Idk if anyone has plans for any kind of celebration or anything on this day but we also don’t really have any precedent for what we do at this date, so…
Anyone who know they won’t be around?
Or should we just go ahead with meeting?
mayhem will be around
I'll be around
something something nerds are loners etc
maybe reeeooo won't be? :P
Plans can always come later.
I guess let’s go ahead with it, but if anyone’s going to not be around, that’s okay: just send me a review by mail. :)
I will be around too, but anyone can be off for a meeting.
Thanks for your time everyone! (Sorry for going over!) Stay safe!