Notes from #MetaBrainz meeting 2018-02-12

[Freso]

MetaBrainz Meeting 2018-02-12

Meeting start: Making sure you're not a bot!

Agenda

• Reviews
• GSoC idea design tickets
• Syswiki for community-run services

Reviews

@samj1912

Making sure you're not a bot!

@samj1912

so this week, I learnt a lot of new stuff, the general JS ecosystem, React, Redux, flux and started helping with the react port for mbs
the PR is here →
MBS-9626: Convert entity headers to React by sambhav · Pull Request #608 · metabrainz/musicbrainz-server · GitHub
I started out thinking I will port just 1 header file, but ended up doing a bunch of them
this also helps me digest MBS code in managable bits
and look into WS/3 parts
apart from that, picard reviews as usual
and I helped @chhavi with a POC for our design system
Addendum: forgot to add that he also started writing a blog documenting the freezing system for picard/pyqt apps in general

@zas

Making sure you're not a bot!

@zas

Mainly Picard stuff, targetting 2.0
Plus usual supervision, upgrades, server restarts, alerts managing
create a new VM for irc bots, Leo Verto will move stuff from nomo to it
Implemented CAA-88 support in Picard, and pushed a bit for it to be done, which succeeded

@bitmap

Making sure you're not a bot!

@bitmap

I worked on CAA-88, fixed the caa-indexer to put the new thumbnails in index.json and added them to the caa redirect api
worked with the IA to figure out a way to generate the thumbnails for old releases, I’m doing that now through their meta manager
we’ll need to link them from mbs when that’s done
fixed our eslint setup to help people submitting react prs with trivial coding issues
spent too much time trying to codesign picard app bundles and wasn’t able to figure it out yet
and I did a bunch of code review, cleaned up some existing PRs and fixed some test failures in mine

@yvanzo

Making sure you're not a bot!

@yvanzo

Latest contributions to MusicBrainz server made during GCI 2017, by naiveai and spellew, have been released last week.
I fixed small issues, reviewed PRs by spellew and samj1912, and worked on the anti-spam thing which I have to split into smaller chunks for review and to avoid conflicts with ongoing migration to React.
I took a break by looking into small schema changes and other prerequisites to redesign ideas.

@Rob

Making sure you're not a bot!

@Rob

• Prepared for and held the MetaBrainz Board meeting.
• Continued to work with attorneys to fix our spanish org.
• Some LB reviews and trying to get the LB beta up and running.
• A couple of conference calls and working down a backlog of emails.
• Move the 2016 annual report forward.

@dragonzeron

Making sure you're not a bot!

@dragonzeron

I have now gotten access to Japanese irscs and now I am going back on my recordings I have added to add irscs and adding labels that released songs and adding ISWCS and Jasrac ids as well as add the new lyric sites onto works and what not

@iliekcomputers

Making sure you're not a bot!

@iliekcomputers

Worked on LB PRs and spent a bunch of time trying to batch submit listens instead of just submitting 50 at a time. Almost ready but still some problems in it.
I also spent some time trying to understand how dumps get to the ftp server in MB, so that I can get LB dumps to the ftp server too. Ideally I’ll get it working this week.
In other news, currently in cold Manali for a few days, be back tomorrow.

@reosarevok

Making sure you're not a bot!

@reosarevok

We were working on the cleanup, meaning that we found out even more style stuff to change
https://tickets.metabrainz.org/browse/STYLE-913
https://tickets.metabrainz.org/browse/STYLE-916
And https://tickets.metabrainz.org/browse/STYLE-912 and https://tickets.metabrainz.org/browse/STYLE-911 which are unrelated to the cleanup but still
Other than that, general support issues

@ApeKattQuest_MonkeyPython

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

Well! it seems finally a solution to my macomputer is in sight! I’ve rung them and sent email, the guy has sent me an answer that he’s working on it tonight and tomorrow!
Hopefully this means I’ll be getting the machine back asap!
Still doing some works on releases and instruments. I’ve now almost finished the 3 /Dvořák/ releases I rented before yul (lol) -__-

@alastairp

Making sure you're not a bot!

@alastairp

not sure what I reported last time I was around
did I say that AB uses Docker now? at least for development
I merged a whole bunch of patches from RashiSah (thanks! are you here??)
I want to try and upgrade react in the coming weeks (uh oh)
otherwise just keeping on keeping on

@chhavi

Making sure you're not a bot!

@chhavi

So this week, I and bitmap finally set up our design system repo, for the “grand redesign”
It’s still empty, but yes, we are on it.
Also fiddled with bootstrap and react to set up a POC for it, with help of samj1912
Final-ish rounds of mockup ready for Artist entity. Will put them for feedback this week. Once done, we can start slicing them into components for our design system
Having a basic template and components, will make it faster for designing/developing other entity pages. We should be rolling with this redesign more rapidly in a month or so, in my estimation! (hopefully)
Apart from that, helped zas a bit with picard log viewer and a banner for our latest cleanup.

@Freso

Making sure you're not a bot!

@Freso

I was a bit around IRC and had a board meeting on Tuesday, but have mostly been sick and unfocused all week, so haven’t done anywhere close to as much as I’ve wanted to. I really hope spring comes around soon. Ah well.

@Deleted_Editor_1968048

Making sure you're not a bot!

@Deleted_Editor_1968048

Being not so active recently, had an exam this month for my graduation and trying to learn something useful in spare time. rn I’m trying learn react

@vishichoudhary

Making sure you're not a bot!

@vishichoudhary

was looking for some bugs in picard.
Added some keyboard shortcut keys in picard
apart from that read about picard coverart part

@ferbncode

Making sure you're not a bot!

@ferbncode

This week, I created a PR in CB for creating db tables in test container before the tests run. This would prevent tests failing due to code running while running and setting up the test app (as in Pull requests · metabrainz/critiquebrainz · GitHub). Will try to improve this by adding test.sh (like in LB, AB), so that there is no need to remove containers explicitly.

@dpmittal

Making sure you're not a bot!

@dpmittal

I was not so active these days but I was setting up CB locally and will start contributing again soon…

@rsh7

Making sure you're not a bot!

@rsh7

I have worked on some open issues, and working on a new one

@kartikeyaSh_ircc

Making sure you're not a bot!

@kartikeyaSh_ircc

This week I created 3 tickets(LB 308,309,310) and created 3 PR’s on LB (LB-148,308,309). these deal with Last.fm compatible API. I need to discuss some problems that i’m facing then continue further work.

@akhilesh

Making sure you're not a bot!

@akhilesh

I worked for bookbrainz, and I Sent this PR for improving search Results

GSoC idea design tickets

Making sure you're not a bot!

@chhavi

So some of our ideas on GSoC page require a UX component. Yvanzo has linked them, I have left some initial comments/mockups. It will be nice if we can have feedback on them. Will help someone be more productive with their proposal/coding time.
Here’s one.
https://tickets.metabrainz.org/browse/MBS-9613
And the other is the setlist editor.
https://tickets.metabrainz.org/browse/MBS-9533

Syswiki for community-run services

@Leo_Verto

I’m doing a fresh install of BrainzBot and samj asked me to document it, where should I do that? The syswiki seems like the obvious place but I don’t (and definitely shouldn’t) have access to it. This seems like it’d affect all projects run by non-MeB employees (e.g. also BookBrainz). Should this kind of info go into the project repositories? The wiki? I’d love to just have a central place for storing and finding that kind of info.
also is there any monitoring stuff that we should plan to integrate?

Some discussion and clarification happening, but ultimately there was consensus that installation and deployment documentation should be in the related project’s repository, to the extent possible (ie., nothing secret, like credentials).