#metabrainz

and also submitted a patch to help the incremental sitemaps service recover from recent RG type updates. that's already been deployed in prod

otherwise I was writing some docs about React state handling in MB, which reosarevok mentioned was needed, and doing a bit of code review

that mostly's it. fin, go yvanzo

Hi!

Among other things during last week’s doc sprint, I wrote and documented some scripts to repair SIR on queues alert.

bitmap: oh! I marked it as being done by you in the docsprint doc then :)

The video call with a member of the Weblate team has been useful: lot of answers to technical questions; I forwarded hosting negociations to mayhem.

(we have agreed, but communication is going slowly with them)

Plus usual maintenance, support, triage... That’s all from me. Go reosarevok!

Hi!

I wrote a fair amount of docs for MB, also helped KassOtsimine with the instrument one (still working on that) and got an area one from drsaunde which I haven't had time to check yet

Other than that, just updating PRs to get ready for beta release tonight

KassOtsimine: if around, you go!

hi! meow! etc.

I've been working on writing a documentation about how t oadd instruments

the first itteration was finished and is currently going through the reosarevok treatement

else i've been looking at instruments, closing invalid ,etc

[design-system] 14akshaaatt opened pull request #50 (03master…deploy-to-gh-pages): Deploy to gh pages https://github.com/metabrainz/design-system/pul...

how about you, bitmap ?

bitmap went

I went first :)

bitmap started out. :)

oh he went

ok Freso then!

I’ll pass it on to lucifer! Go!

hi all!

go lucifer!

(Still up: alastairp, mayhem, akshaaatt, monkey, zas, Freso – anyone else who want to give review, let me know ASAP!)

I mostly worked on reorganizing and adding documentation to ListenBrainz last week. also updated/added tests to follow up on already open PRs. that's it for me.

alastairp: next?

hi there

I did some docweek stuff, helped lucifer decide what to write in a few places, and reviewed his work. I also updated some syswiki things and cleaned up some MBH tickets

most of my time I continued looking at the BPM analysis that I was performing the previous week, resulting in https://github.com/metabrainz/mir-analysis/blob... and https://github.com/metabrainz/mir-analysis/blob...

and I did a bit of reading about mood prediction of audio, which bought up an interesting paper which resulted in some discussions today with mayhem and others about how we can collect annotations from MusicBrainz users

on that note, mayhem?

[design-system] 14akshaaatt merged pull request #50 (03master…deploy-to-gh-pages): Deploy to gh pages https://github.com/metabrainz/design-system/pul...

hey.

last week was all about documentation.

I spent the bulk of the time devising a plan on how to pass the reigns of MeB to the team, should I... end up on the bottom of the indian ocean. with the banking token and my mobile phone.

what steps does the team need to take?

how does one recover passwords for all of the services we have?

What services do we have that are not already visible to the team?

What is our business dev philosophy?

I've devised a way in which Reo and Zas are both needed in order to take control over my accounts, the bank accounts and establish contact with our accountants.

it was equal parts depressing, a fun challenge and very tedious.

but I am very glad its done. I think our tram factor now hovers around 3.

Which is a drastic improvement from 1. :)

!m mayhem

You're doing good work, mayhem!

I also doled out updated contracts for most of the team and participated in another roundtable discussion for the ODI peer learning network.

boring, tedious, nearly all done.

and a big thanks to zas and reosarevok for taking on such critical roles in this. especially reosarevok, since he now has to deal with our bank in cali.

fin.

Freso, you ready now?

I prefer to go at the end so I can transition to next topic, so I’d prefer to pass to akshaaatt :)

Hi everyone!

My week started by brainstorming more mb revamp work and spending some time on the community forum. While at it, I got some important feedback that we first need to define a proper guideline about the design we are looking to use with detailing around the color scheme, font sizes etc. so that others can follow the same to help with the work.

This moved my attention towards the design system in place and I had a painful time updating and fixing it.

I also visited all our projects (including the likes of Picard!) and set them up locally to get started and see if there are any problems around the work and reported some.

CB took a hell of a time to get started!

Learned a lot of new stuff, which works great with what's upcoming this week!

fin. Go monkey!

Hi !

(Only zas and myself still up. Last call for anyone else who may want to give review!)

Last week started with a long overdue transfer of the main BookBrainz repositories to the MetaBrainz Github organization 🎉

Then the rest of the week was working on documentation. There is so little in BookBrainz that there was ample choice.

I revived the developer docs (https://bookbrainz-dev-docs.readthedocs.io/en/l...) and started documenting the schema and other aspects

Thanks to Shubh and ShivamAwasthi for giving me a hand on that

I also worked on the user guide (https://bookbrainz-user-guide.readthedocs.io/en...) , but haven't polished that to commit it yet.

And finally helped a bit with the general communal syswiki/document-all-the-things effort

That's it for me, zas go !

Hey

last week I didn't do much, I was dealing with pretty bad family stuff

I kept an eye on stuff though

I fixed cert issue with wiki.mb

I fixed a nagios issue related to the removal of wiki previous VM (now totally gone)

plus various minor things and few edits, Picard PRs reviews. fin, Freso?

🙋

A little bit of the usual, but also a fair bit of time working on documenting things related to Community Managing.

Also a chunk of time spent talking with Rob and working on things related to that.

fin.

No more people on my list for reviews, so this wraps up that item. Thank you everyone for your reviews. :)

We have one additional item on the agenda today, so…

reo: Repo review

Hi!

I brought this up during the week, but I took a look through our repo list and I listed on https://docs.google.com/document/d/1bl7xpNq3tDA... the ones that seem either to need a description to more easily understand what they are (a few) or just useless and in need of archiving away to clarify we're not working on them at all (a fair amount)

alastairp also contributed a list of repos (apparently mostly by zas) that are not accessible by coreteam, and maybe should be

So if the team people have some time to take a look (no huge hurry, unless some of the hidden repos are very important to reduce zas' bus factor I guess) we could improve the state of the metabrainz repo a bit and make things more clear :)

I expect a lot of the repos need zas, mayhem and/or possibly bitmap to check them and see if they're indeed outdated and to be archived

Anyway, that's it from me on this :)

I'll have a look this week

Thanks!

Thank you reosarevok :)

Also, re docsprint, yvanzo mentioned adding tickets for stuff we didn't get to during this week, maybe other projects should too if they're not doing it yet :)

Oh, yvanzo, did you mean for Doc sprint to also be on the agenda this week?

No, that was from last week I guess, to plan for the meeting on Wed.

I thought as much. :)

Alright then!

That wraps up today’s meeting then. Thank you for your time everyone!

Stay safe out there!

</BANG>

Thanks everyone!

Thank you!

Thanks !

akshaaatt: I think the branch to deploy to should be `gh-pages`

Ah ohkay monkey!

And then probably select that gh-pages branch as source in this page: https://github.com/metabrainz/design-system/set...

Yeah, just about to do that

Finally monkey https://metabrainz.github.io/design-system/ :)

Ni e

Nice!

monkey do we want the plan to be: Define all the front-end, react components and CSS in this repository and directly include them as a package to the respective projects? This way, we can be sure that MB, LB, BB, etc all follow the same shared dependencies. Does this sound good?

With this, we can also document the components properly here and other projects could be like.. hey! That button which BB uses looks cool, we should use it as well

Like I want to restrict us from bumping bootstrap version 3 to 5 for all projects separately

reosarevok: I updated a couple of repo in the doc: mb-solr & mb-solr-cloud, does it look good so far?

[bookbrainz-site] 14dependabot[bot] opened pull request #768 (03master…dependabot/npm_and_yarn/babel/preset-react-7.16.7): chore(deps-dev): bump @babel/preset-react from 7.16.0 to 7.16.7 https://github.com/metabrainz/bookbrainz-site/p...

yvanzo: much better, thanks

yvanzo, bitmap: there's 11 tickets in master now, should I put a beta out with those for now?

reosarevok: sure, should I merge the warnings PR too?

it has a selenium failure though I can't see how it's related

bitmap: lemme check approved stuff

I'm ok with merging https://github.com/metabrainz/musicbrainz-serve...

[musicbrainz-server] 14mwiencek merged pull request #2392 (03master…bump-minor-js-deps): Bump some isolated JS dependencies https://github.com/metabrainz/musicbrainz-serve...

Also https://github.com/metabrainz/musicbrainz-serve... since it's already deployed anyway AFAIU?

yes, it's already been tested in production

I think I'll also merge https://github.com/metabrainz/musicbrainz-serve... if that seems ok?

https://github.com/metabrainz/musicbrainz-serve... is also approved by you, can you see a worry why it'd need a second review? If not I'll merge

I understand yvanzo was ok with the content of https://github.com/metabrainz/musicbrainz-serve... and just wanted more docs

But maybe he can confirm before we merge

We can also merge on Wed

If he's not around atm :)

2375 seems fine but a TODO to add a test might be nice?

I approved it anyway

And I'm also ok with putting https://github.com/metabrainz/musicbrainz-serve... already in beta and seeing how it feels

It shouldn't be able to cause issues, right?

Other than "very large logs"

2364 seems small enough to not need a second review

I'll add a ticket for that test

And add it to my todo

yvanzo: ok :)

[musicbrainz-server] 14reosarevok merged pull request #2364 (03master…MBS-12127): MBS-12127: Allow batch-changing all blank artist credits https://github.com/metabrainz/musicbrainz-serve...

re: 2394 we should probably set some log-opts on the website/web service containers first

yvanzo might have a good idea of what to set for those

to limit the size of the logs

Ok, then let's wait for his review / ideas, merge on Wed if sensible