Notes from #MetaBrainz meeting 2018-02-26

[Freso]

MetaBrainz Meeting 2018-02-26

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• OTHER-77: MarkBrainz
• Design ticket

Reviews

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

well, a piece of business to close out a long standing piece of drama that started last year.
as you may know, Elizabeth and I got into it wrt her contract renewal and she took the conflict to the board of directors.
the board of directors has been investigating the situation and working out how to address it.
today the board issued the following statement that (hopefully) closes this chapter:
Board Statement: Personnel conflict resolution, Elizabeth Bigger - Google Docs
I did not write this statement, nor did Freso.
If you have any questions about this, then please mail your questions to freso. freso@ , as per usual.
this drama has been weighing very heavily on me and zapping my motivation to get things done.
I’m very much hoping to move past this and to finally find my motivation again.
last week was the usual BS for me. conference calls, dealing with this drama and the positive bits, doing some LB work.
(and spending some time in a forest freezing my ass off with hippies, but that is another story)
onward and upward.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

apart usual supervision, upgrades, restarting stuf, etc… i mainly worked on Picard, investigate the plugin system and possibilities
concluded it is something that could fit GSoC, and we shouldn’t delay Picard 2 even more
PR reviews, feeding forums with dumb ideas, edit reviews, and usual bunch of MB edits

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

this week was mostly spent on MB apart from picard reviews
we are upgraded our JS stack (node → yarn and bitmap is working on a webpack PR)
apart from that typical react stuff and PR reviews

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I spent most of the week testing/reviewing/rebasing/merging react prs mostly from samj1912
I submitted some more prs to move the migration along
along with a pr to fix our site in IE11
and a giant pr to move our build system to webpack which will bring a host of improvements to make development much easier

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’m finally caught all up on meeting notes again! (At least for the next ~45 minutes.)
Still working through other backlog. Poked at some editor reports. Poked at forums. (Poked a bunch of spammers very, very hard, and put more spammers on a list for feeding to SpamBrainz later.)

@dragonzeron

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@dragonzeron

I have been working hard on trying to add irscs as well as complete the lyrics site I added to the whitelist then other then that I been going on artist page and romanising there names

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

So, I did the usual support, and tried to contribute a bit to the cleanup
Other than that, I took some time to look at a bunch of style tickets, and:
either resolved them outright (fixing/wontfixing, quite a few wontfixes)
requested implementation from devs- thanks yvanzo!
or marked them as blocked until some code is written that makes them possible
(for example, quite a few are blocked until we get https://tickets.metabrainz.org/browse/MBS-3993 )
Since implementation requests still are officially unresolved, I still look like a slacker on the graphs, but what’s there to do
Anyway, that’s mostly it - I like these new options for style, so I’ll try to go through more old stuff and set it to whatever is appropriate
Oh, and I opened two new style discussions, please give input?
"(bonus track)" and "Artist X cover" in ETI [STYLE-777]
"Cover" release group type [STYLE-555]

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

finally up to speed with my old edit mails! Wrote feedback on chhavis great artist-page design ticket
been editng hyperion releases and working on OTHER-326!

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

So this week I reviewed a PR by akhilesh
This will introduce a stats page for BookBrainz
It’s looking pretty good at the moment, and hopefully will get merged this week
I’ve also worked a little bit more on the relationship editor, but not a huge amount of progress
There’s also been some PR work done by bukwurm_ (I think that’s his IRC name anyway)
This piece of work will eventually show a warning when the editor is about to add something that’s already in the database

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Not much to report, I have been mostly off half of last week, failed to keep up with PR changes (damn git spammers), fiddled with docker/vm for dev env, wrote a draft for *Brainz markup (OTHER-77).
Aside, latest MBS release has been skipped since main changes were about internals only.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

Released a new version of brainzutils with a bug fix and a feature addition
Fixed a bug in LB beta which was a bit hard to track
Made flask-debugtoolbar work with all PythonBrainzes
Reviewed various PRs on the python projects
Did PR review addressal on the PR which releases listenbrainz dumps
Did some work on deleting old dumps from the server
Deployed latest CB to production with help from ferbncode (thanks )
Now working on adding a feature to LB that allows users to request that their stats get calculated

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

this week I worked on acousticbrainz and sent a PR for fixing CLI interface in dump_manage.py: https://github.com/metabrainz/acousticbrainz-se… (Need to update that). sent a fix for this CB-280:
CB-280: Fix Spotify mapping page suggestions by ferbncode · Pull Request #182 · metabrainz/critiquebrainz · GitHub
Some deleted mbids are causing trouble in CB for which I will try to send a fix this week.

@vishalchoudhary

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@vishalchoudhary

this week changed some of picard code from vary python2 to python3
and did some researched about proposal and writing proposal

@akhilesh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@akhilesh

This week I worked on adding statistics page.
I created a PR with top editors statistics which @LordSputnik kindly reviewed. Then I also worked on his suggestions in the PR.
I created a PR for resolving the issue

@yagyanshbhatia

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yagyanshbhatia

Last week was mostly spent on look at and write test for Picard utils and studied a bit for plug-in systems too.
That test I wrote needs refactoring first… so working on it
Add tests for encoding and decoding filenames by yagyanshbhatia · Pull Request #844 · metabrainz/picard · GitHub
Couldn’t do much because of ongoing semester exams

@bukwurm_

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bukwurm_

This is my first meeting.
I have been hacking into BB for a while.
I made few pull request some time back.
Once merged, they will allow for stricter check on dates being entered via editing pages.
This week I have started to work on feature to enable warning messages if users enter something which already exists in the database.
I am learning a lot and loving it.

OTHER-77: MarkBrainz

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

I wrote a draft proposition you can read at
Brainzed Markdown Draft #84884 · GitHub
and comment into issue tracker.
This is probably not complete, but it is a good start, IMHO.
If you have specific issue in mind, not covered by this draft, please say it!

Design ticket

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

Helo, we plan to wrap up the mockups for Artist page in the coming weeks. So if you wish to give any last moment comments and feedback, now is the time
Link to the comment you would want to see for the latest mockups (quite a long thread now, so this might help)
https://tickets.metabrainz.org/browse/MBS-9536?focusedCommentId=45357&amp=&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-45357