#metabrainz

LB-212: Show the MetaBrainz logo on the listenbrainz footer.

Oh, true, I helped chhavi_ and samj1912 a bit with stuff :)

kartikeya: please in one hour :)

(meeting right now)

Tackled small issues related to auto edits and UI languages.

(People still up: (zas?), chhavi_; people maybe up (please confirm): LordSputnik, Leo_Verto, alastairp, ListMyCDs, ferbncode; anyone else?)

i'm talking about thise logo https://github.com/metabrainz/metabrainz-logos/...

ok

kartikeya: meeting time til end of hour, sorry ;)

Mainly worked on MBS-9480 and related spam issues.

MBS-9480: New editor type: spam ninja https://tickets.metabrainz.org/browse/MBS-9480

yvanzo: thanks for fixing Estonian!

Fiddled a bit with React vs TT.

MB edits, votes.

reosarevok: You're welcome :)

Fin. chhavi_?

Helo :)

(chhavi_ is last one up, unless someone else speaks up. Ping: zas, LordSputnik, Leo_Verto, alastairp, ListMyCDs, ferbncode.)

So I and Freso discussed about setting up a workflow in JIRA for design tickets earlier this week.

Most of my time this week went into a lot of *invisible* design work. Did a brief competitive analysis of last.fm, discogs, iTunes, etc. Basically to figure out what we can learn from them and not reinvent the wheel :)

Oh, right, I need to get on that.

ugh itunes: what to learn: stop redesiging the site every x months that breaks all userscripts :P

reosarevok CatQuest helped me get started with editing and other doubts

!m reosarevok

You're doing good work, reosarevok!

!m reosarevok

You're doing good work, reosarevok!

Almost done with the artist page mockup, will run through it tomorrow with Ruoak hopefully and put it up for feedback And with reo’s help, trying to edit/add things

chhavi_: Whenever you have time, you may also want to try editing on e.g., Discogs and Wikidata to see how editing there works.

yea lso he helpe with debussy and isntruments, forgot ot mention :X

that's about it. fin. :)

samj1912, CatQuest: http://finnishnightmares.blogspot.com.ee/2015/1...

chhavi_: and Rate your music (rym)

I haven't gotten any responses from the pinged people, so let's move on.

XD

Freso: summit notes/minutes

aah okay. Added rym to my list. Let me know if any others that I should check out!

reosarevok: :D

Freso: and jwf|matrix ?

So as yvanzo reminded me just prior to the meeting, we have a set of summit minutes/meeting notes at https://docs.google.com/document/d/1ToifUYo_g-x... almost exclusively thanks to alastairp (seriously, thanks!).

jwf|matrix!

yvanzo: Didn't arrive at keyboard yet.

yvanzo: he can come up when he gets to the keyboard after this :)

We should probably improve the minutes to actually remember what we agreed. Not volunteering.

Make a GCI task for that? :p

I won't have the time or energy to finish the notes from the summit (I would also likely have to rewatch the thing on YouTube - which luckily I actually can this year though :)), so please, please, please people who attended, look them over and add what you remember from the discussions.

If we have each person take one discussion, it'll be quick!

E.g., maybe chhavi_ could flesh out the UX discussion and reosarevok the Translations? It doesn't have to be one person doing everything.

yep, I can add the UX part :)

So yeah, this is mostly a plea for people to chime in. 🙏🏼 🙇‍♂️

And that's it for this topic.

wtf is ?

🙇‍♂️

chhavi_: ❤️

jwf: Want to do a review?

Freso: If it's the summit meeting notes, I'd be happy to look them over. :)

CatQuest: man bowing.

Let me just do Google Code-in quick and we can do jwf's topic and potential week review (and other stragglers). :)

:+1:

So our official application is at 100% now! So we're definitely applying for Google Code-in! 🙌

Sorry still traveling, my flight from Zurich to Lyon was cancelled. Currently in a bus from Geneva to Lyon. Not much to say, but San Francisco and gsoc summit were fantastic, met many interesting people involved in the open source movement. More on that later.

Ah, too late

https://wiki.musicbrainz.org/Google_Code-in/201... still needs a lot more work though. :( We have a lot of CODE and D/T tasks and even a handful of O/R tasks, but only one listed UI task and one QA task.

We need at least 5 of each task type on that page to get accepted for GCI.

Is UI also "check the UI"?

(for things that are weird)

So try and think of some UI and QA tasks to add to that page.

Oh, I can add suggestions to the docs bit, I think

«User Interface: User interface can include many types of tasks including designing new visual aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are visually impaired.»

«Quality Assurance: Finding and verifying bugs is an important part of software development.»

Freso: can we add gci tasks for improving or adding importers ?

(UI and QA's definitions at https://developers.google.com/open-source/gci/r... respectively.)

zas: The Facebook event importer script (that is now broken) was a GCI task, so sure. :)

Freso: What comes next in GCI timeline?

(I miss opatel99 - gcilou, please tell him.)

yvanzo: GCI org. applications close Tuesday next week.

Freso: can you give some example of QA tasks?

(Maybe later)

And I think org.s are announced Thursday, maybe.

Freso: aw I will

samj1912: Check the links at the top of https://wiki.musicbrainz.org/Google_Code-in/201... :)

There are both official Google/GCI sample tasks and links to MetaBrainz's tasks last year.

ah ok

gotcha

The full GCI timeline is at https://developers.google.com/open-source/gci/t...

Ohm says he'll drop into the channel sometime today or tomorrow

Maybe we can add small design elements like " redesigned footers" from mockups for UI tasks.

gcilou: ❤️ :)

Any more questions for GCI? If not, I'll give the mic to jwf. :)

jwf: Take it away!

Leo_Verto: Do you want to do a review from mobile, or are you good?

I was looking at the "Insights" tab on GitHub repos and noticed a new tab underneath, "Community". All repos should have this page. https://github.com/metabrainz/listenbrainz-serv... On the page, it has a few recommendations for things to do for your project, and I also learned that GitHub has some way to access this in the API. Like for Hacktoberfest, DigitalOcean was highlighting projects that had a complete community profile.

Two easy things I noticed:

I can do a quick review if that's okay

1) We have a "HACKING.md" file in a lot of repos, but if we rename it to "CONTRIBUTING.md", it will match the GitHub requirement

2) We also have a code of conduct (https://beta.musicbrainz.org/doc/Code_of_Conduct). We could either copy+paste that to all repos or just add a file for Code of Conduct that links to that page for all MeB projects.

Leo_Verto: Sure, you can go after jwf. :)

jwf: I think the latter is better for 2).

I was going to do #1 for ListenBrainz, but I was curious if there was a preference for #2

Okay, cool.

jwf: we actually have a long-pending task to move to a MeB CoC IIRC

Esp. since that CoC is overdue for a revamp.

jwf: the HACKING.md file (at least, in LB) is not guidelines for how to contribute though. It's more of common commands needed by devs.

(more general)

So I was going to go through all MeB projects and add a Code of Conduct file pointing to the CoC on the MusicBrainz site

There was a web service for checking if a GH repo has everything setup for simple contribution, I'll see if I can find it once I got my PC set uo

we have http://github.com/metabrainz/guidelines too btw

And yeah, that would be awesome to get that hosted on the MetaBrainz site so it's clearly implied for all projects under the MeB umbrella

jwf: that CoC is very specifically MusicBrainz user oriented though, no?

That seems a bit of a mismatch for github

jwf: What reosarevok said.

What kind of CoC are they expecting?

Only "General" is really relevant for other projects.

Is it a CoC for developers?

(We also want to move the Privacy Policy to be a "global" MeB one for example.)

jwf: We are not using GH issues, will never match GH “requirement” of issue template.

iliekcomputers: Oh, awesome, will look at that.

Oh. Huh

reosarevok: I would imagine the CoC would be for anyone participating in the MeB community.

First time I see https://github.com/metabrainz/guidelines

Is this linked from somewhere?

yvanzo: Yeah, I figured, that's why I didn't bring that one up. :)

reosarevok: this is relatively new (few months).

yvanzo: We could make a template for PRs at least?

reosarevok: not sure, I saw it in a few PR reviews I think :P

PRs is true

reosarevok: yup, picard uses it

I think it started from there

Freso: Maybe the better question is if the CoC is something to visit first before adding it to repos?

It seems like it should be linked from https://musicbrainz.org/doc/How%20to%20Contribu... at least

and then gentlecat made a repo to move stuff there

I think it's fine to link to it now.

Might give me more incentive to get it modernised a bit. :)

Freso, jwf: I mean, these are “requirements” for a fully GH-driven project, which is not our case. It is a nice recommandation list, and we should just check that we have equivalent features.

Freso: I'd be happy to help with CoC discussions / updating too. I spend a lot of time on the Fedora Diversity Team and Fedora Council and we worked through some CoC issues last year to help us modernize a bit

yvanzo: Sure.

yvanzo: Right, but it seemed more interesting to me when I saw GitHub better highlighted projects to contribute to because of this profile. :)

jwf: I would like to "eat your head" (🤣) about that at some point, yes. :)

Freso: Yeah, feel free. :)

For now, I'll work on adding the linked CoC to the repos, can always change it later on if it moves somewhere else.

yvanzo: I think we may well do what we can to be better GitHub citizens, even if we will never be natives.

jwf: Oh, ok.

Freso: You chose a good head like me :p