#MetaBrainz Meeting 2022-04-25
World Malaria Monday
Last meeting: 2022-04-11
Next meeting: 2022-05-02
Kia ora! It’s been a slow few weeks/months for me, buried in other work
but also partly because I’ve been trying to tease things apart in a design sense
so it’s been slow going, but hopefully important stuff
mainly standardising all the logos, so that we now have a library of logos in the logo repo
that all match and are ready to go
if I catch anyone using an old one…
Also putting together some guidelines for MetaBrainz design and MusicBrainz design
Initially I was hoping to have one doc that covers all projects but I should have realised they were too different already
It would be great to get feedback on the design docs after, because the timings good with GSOC applicants lately
They all ask very similar questions and some docs might help!
so, this week I was a lot more productive than I was expecting.
did work and
swept outside and planted flower-leeks and other spring things
sadly those things aren’t really brainz related,
But I did infact manage to add a few tickets and test beta Bookbrainz and
!m monkey for the new beta-release routine!
as well as adding some books and releases and retagging and suches.
had some discussion on the community… thanks @kellnerd, indy, @mr_monkey and @aerozol for lots of interesting input.
This week I will also be doing much of the same, but I hope to also be able to squeeze an instrument or two in as well
last week I worked on an Ansible role to manage /etc/hosts, based on a request from
@alastairp. It’s not deployed yet but should be real soon ™.
I also hacked up a script that queried all the servers, pulled information on running Docker containers and then rendered a web page.
aside from that, just a few other minor Ansible related bits and bobs, and then watched @zas deploy several new servers in a matter of minutes
I think @zas and Ansible are becoming a single entity
@Freso noted that he does “not feel comfortable travelling with how the world acts like COVID is over when it very much is not”, but most others who spoke up were fine with going.
No objections to the proposed dates, so MetaBrainz Summit 2022 will be on October 8th–9th “unless something changes and we hear objections about this date in the next week or two”.
Thanks to aerozol, we have some design guidelines available now
design-system/component-usage.md at components · metabrainz/design-system · GitHub
design-system/MetaBrainz design guidelines.pdf at master · Aerozol/design-system · GitHub
design-system/MusicBrainz design guidelines.pdf at master · Aerozol/design-system · GitHub
We want feedback from everyone/anyone on this
It would be really good if everyone could take a look. Some of this will bite you in the ass later if you don’t, I promise
I believe we should be including more sections in the design guidelines. Please let us know the topics that should be included
I also put some sneaky changes in there - for instance, there isn’t really a text style consensus in MB, so I made something up from the direction akshaaatt is heading in. We can edit as we go, but eyes would be good, these are big changes
Also, accessibility guidelines, minimum font size, etc…
These docs are more like guidelines, it lives alongside akshaaatts fancy component library for css etc
Also, I am realistic about making all of you follow guidelines loool
Anyway, I believe we need to head in the direction of following these guidelines in the future because I faced an issue understanding how to design something new
It’s really apparent with the GSoC students too I think. I think new devs need it, and it will have the side effect of maybe helping all you old hands align
There was some discussion about the use of PDFs for these and how to suggest, implement, and track changes (since PDF does not lend itself well to traditional code-based version control systems like git). No definite resolution, aerozol and akshaaatt will discuss more how to go about this.
It was also decided to merge the logo repository into the design repository.
Securing MeB infrastructure - part 2
It was decided to do a separate security meeting the next day, Tuesday April 26th at
regular meeting time.