#metabrainz

My only question so far is "why is this a pdf, that's not very user-friendly"

That is user-friendly, not dev-friendly.

Easily shareable and downloadable

I took a quick look at the MB one in the morning, but I'm not even sure how many of these we do not follow at the moment

Akshaaatt was going to convert it into readme's for me but I think it's probably a bigger job than expected?

aerozol: Any chance you can use a text-based format that can be diffed using git?

Agreed reosarevok. At first I thought we'll have a markdown file but given how beautifully aerozol has made the document, I would prefer the pdf

Would need to look at them more calmly side by side with the site :)

I'll talk to akshaaatt about how we can go about it

But yes we need to make it editable hence the idea of putting it in a google doc/slides

I think it's fine to have a pdf too, just yeah, not super easy to comment, update etc, especially while we're still working on it

I think both is a good idea, but design guidelines should be reasonably static, I will do a PDF to go alongside once we've finalised

Agreed

Google doc or readme?

aerozol: If it cannot be a source format, you can try using a pdftotext and have a text-format copy along with the pdf.

While we're on this topic - merging the logo repo into the design repo? Thoughts? It makes sense to me

disclaimer: I don't know how complicated that is to do

https://github.com/metabrainz/design-system/pulls There are 2 Pas currently available here. Both can/should be reviewed by team members who want to provide some insight into design stuff :)

IMO these guidelines won't change often (if at all) and PDF is the most reasonable format, allowing to present things nicely (which is important for graphical guidelines)

sounds good.

PRs*

(its not hard)

Yes monkey

+1 for mergin, no point in having them separate

(I don’t think we’ll have time for "Securing MeB infrastructure - part 2" this meeting.)

Is that us akshaaatt?

Yes aerozol, the logos should be merged to the design repo I feel

Yes aerozol, that's about it from my side.

I'll make a ticket

Thank you!

Freso: a minute.

could i get a direct lin kto the actual pdf (cant get github)

Maybe we should have a separate security meeting again?

CatQuest: https://github.com/Aerozol/design-system/raw/ma...

probably better

thnaks monkey

yvanzo: Normally there would have been ~30 minutes for the topic. Just so happened this week that there were two "longish" topics as well.

And also https://github.com/Aerozol/design-system/raw/ma...

At least to skim through the rest of the document written by lucifer.

(Which I did warn about during the last meeting. :p)

+1 for another security meeting, I think that makes sense and gives us more time to discuss

I'm happy to do it as a separate meeting again

lucifer: all the way through the top artists page 1. not a single bad track!

Tomorrow normal meeting time?

can do

ok for me

OK for me

Works for me

sgtm

ok

Ok

👍

Seems like that’s most people on board with that, and we just hit 20:00 in CEST land.

yass

so it's 6AM for aerozol now

So let’s go with that. Sec meeting tomorrow at regular meeting time, 19:00 CEST :)

Pinging atj just in case ^

Thank you everyone for your time! Stay safe and remember to wear your mask! 😷

</BANG>

to go to bed or to stay up... that is the question (nobody feel too bad though, I'm an ok morning person!)

Thanks Freso! Stay safe!!

Franks Theso !

<3 aerozol

thanks all

Thanks!

mayhem: btw next playlist also in, with all ranks 10-21. it chose 10 this time.

long meeting for a change. thanks all!

if you feel better I too woke up t 5 ish today (but i went ot bed agai nand slept until 10)

lucifer: odd. so very odd.

tomorrow should be fine, best set a reminder

👍

monkey: btw, this is the doc that I started about SSR: https://docs.google.com/document/d/1ioXNMfj6Fwb...

mayhem: maybe because of the training data split.

monkey: currnetly planning on coming to the office tomorrow

I've been digging into SSR + Flask too alastairp

the rmse's aren't very far away so randomness can do that i think.

Same, office tomorrow afternoon

not sure how movingtime is going for you

oh, great!

monkey: can I assign you https://tickets.metabrainz.org/browse/MEB-136 :P

MEB-136: Merge Logo repo into Design repo

we can probably do K-folds training for better result.

lucifer: good insight.

This week I'm wary of taking on more aerozol, but mabe a kind soul here would like to crack their git knuckles?

updated link to @meb

All good, it's not really a priority

Or if it can wait a bit that's OK too

monkey: ^

Assign it to me aerozol

alastairp: monkey: mayhem: i might not be around for next month's LB meeting (friend from abroad is visiting). do you want to hold it later this week instead? also, lmk if there's something that i need to do to avoid blocking you on any tasks.

akshaaatt: Before I forget, if you have to recode the 'recent additions' image sliders anyway, can we change it to 'upcoming releases'? Mayhem was in favour of this a while back too

Legend, Akshat, done!

lucifer: no problem for me to push it back or bring it forward

We can do next week perhaps, LB team? Tuesday?

alastairp: I've raised PR for places page also. The only pending work is BU version upgrade.

next week is next month :)

delay one week would be good.

Ahaa

Actually I am reusing the previous code as of now for the cover arts aerozol

+1 to delay

delay 1 week works for me.

But I would be keen on updating it to upcoming releases

Ah okay all good, worth a try! See how you go?

thanks1

Yuss aerozol!

lets delay then!

Noted. Mon. 9th at 4PM UTC

it's in my calendar now

Maybe we should have a shared MEB calendar?

That would be a good idea monkey

aerozol: I kinda like he split colour text of the projectname that you have a line over in the "colour usage" section tho :o

i see google calendar has that option. https://support.google.com/a/answer/1626902?hl=en

also the second colour for bookbrainz in 2.2g Colours: BookBrainz is wrong

CatQuest: hah! did Akshat see that? Because it's a screenshot of his design > <

so mean

oh no :O

sorry!

Honestly, if there's a really good reason, then sure, use colourful text. But I want to discourage it. Brand colours can be used elsewhere

the one the gradient is based on i mean

monkey: have you never used the term 'chrome' to mean the user interface of something not counting the actual content?

eh, I don't care too much on it, just kidna liek the look of a little bit of colour

Oh, BB gradient I changed because it looked like poo

Nope

tch

I tweaked some of the other gradients as well

chrome is a metal finish and a really crappy browser

i think the gradient shoudl be used sparingly. (if at all)

yes

:D

On a more serious note, orange for text on a white background will be very hard for people with visual disabilities to read

so where did I learn it from?

yes indeed

and the contrast ratio doesn't meet our *new* accessibility guidelines

remember i also have an acessability thing though: ADHD

https://stackoverflow.com/questions/5071905/wha... maybe something something mozilla

...but I'm not coming in making everyone change everything ASAP, hopefully they just help things

aerozol: in general the documents seem sane (but their format was a bit hard to read, wich is ironic :D)

Your ADHD will be very good with the guidelines!! Is the BB gradient change too obvious/distracting?

to be frank, all the gradients are super distracting

Honestly: these guideline docs is where people assess whether a designer is crappy or not. And you always try flex some design on them

used a little they are fine

already on test.mb it is too much now

Agreed - there's a note in there somewhere about using them very rarely

yes!

also I must say: I want something about using text *and* icons. icons are not always the best way to convey something

links that are only icons for example.. not the best

No comment on test.mb from myself until Akshat has it looking how he wants

Then we can adjust if needed!