Notes from #MetaBrainz Meeting 2017-10-16

[Freso]

MetaBrainz Meeting 2017-10-16

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Summit notes/minutes
• Google Code‐in
• GitHub community recommendations

Reviews

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

Not a lot to report for last week. I had a fun time spending a few days with my brother in SF and then meeting people and eating chocolate at the GSoC summit. I’ll be back full time this week to help with search PRs and submit the React stuff I was working on.

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

Further work on improving server reliability. A lot of the changes will end up being configuration, and I am thinking about ways to improve our default behavior in this area. Major touchstones are handling the redis server being unavailable and behaving better when elasticsearch goes down. Still to come, dockerization of the service.

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

working on instruments, researching sorna vs zurna
if they are the same or not (anyone with any input is welcome to give it here)
trying to find out if the https://tickets.metabrainz.org/browse/INST-301 should be closed a “we already have fujara and this seems to be a simple variant” or not, again anyone with input here or on the forum post that will follow is welcome to do so :​)

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

This week I started on SOLR search
Fixed about 30 or so pending Solr tickets
We should have search parity with the current search by the end of the week hopefully

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was a lot of accounting and PRs. not a lot else, really.
I’m glad that samj1912 is kicking ass on the SOLR stuff – it is really nice to finally see real progress on that.
its taking a lot of time to keep up with that.
and I’m still trying to re-establish communication with Quesito, but we seem to not be speaking the same language at the moment. no idea what will happen going forward.

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’m at my mom’s place in Copenhagen now, since it’s her birthday, and will stay the night here and go to my cousin’s wedding tomorrow, so my connectivity is so-so right now.
In the last week I spent some time upgrading Discourse and doing some Google Code-in stuff as well as spending time on forums and IRC.

@paramsingh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@paramsingh

this week was a lot of LB work
I worked on a big PR getting our scheduler out of the webserver
then I started writing code to get LB data dumps working
And I fixed a couple of bugs in the alpha importer
I also fixed a small doc bug in AB

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I did support, mostly
I also looked a bit more into the whole Commons-for-images thing, legoktm gave a few ideas
Need to look into it more

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Tackled small issues related to auto edits and UI languages.
Mainly worked on MBS-9480 and related spam issues.
Fiddled a bit with React vs TT.
MB edits, votes.

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

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
reosarevok CatQuest helped me get started with editing and other doubts
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

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

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.

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

This week I started working on SpamBrainz, coming up with some kind of rough architecture for the project, writing a database schema and then mostly scrapping it in favour of something NoSQL. I also had some kind of enlightenment last night and drew something that may involve viking robots, I’ll scan that later.

Summit notes/minutes

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

So as @yvanzo reminded me just prior to the meeting, we have a set of summit minutes/meeting notes at MusicBrainz Summit 2017 Minutes - Google Docs almost exclusively thanks to @alastairp (seriously, thanks!).
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.
E.g., maybe @chhavi could flesh out the UX discussion and @reosarevok the Translations? It doesn’t have to be one person doing everything.
So yeah, this is mostly a plea for people to chime in.

Google Code‐in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

So our official application is at 100% now! So we’re definitely applying for Google Code-in!
Google Code-in/2017/Task suggestions - MusicBrainz Wiki 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.
So try and think of some UI and QA tasks to add to that page.
«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.»
(UI and QA’s definitions at शुरुआती निर्देश  |  Google Code-in  |  Google for Developers respectively.)
(@zas: «can we add gci tasks for improving or adding importers ?»)
The Facebook event importer script (that is now broken) was a GCI task, so sure.
(@yvanzo: «What comes next in GCI timeline?»)
GCI org. applications close Tuesday next week.
And I think org.s are announced Thursday, maybe.
The full GCI timeline is at Google Code-in 2019 のタイムライン  |  Google for Developers
(@samj1912: «can you give some example of QA tasks?»)
Check the links at the top of Google Code-in/2017/Task suggestions - MusicBrainz Wiki
There are both official Google/GCI sample tasks and links to MetaBrainz’s tasks last year.

GitHub community recommendations

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@jflory

I was looking at the “Insights” tab on GitHub repos and noticed a new tab underneath, “Community”. All repos should have this page. Community Standards · GitHub 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:

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. 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.

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

Some discussion happened about our Code of Conduct needing a revamp and whether we should link to it now or wait for it to get fleshed out. There was also some discussion related to how we’re not fully using GitHub (e.g., GitHub is not used for issue tracking), so we may not be able to get 100% “completion” on the community page.

It was decided to 1) link to the CoC rather than copy+paste it into all repositories, 2) link to the current CoC rather than wait for the revamp, 3) do as much of the “GitHub community recommendations” as we can/makes sense as it might help discoverability on or via GitHub.