Notes from #MetaBrainz Meeting 2017-04-03

[Freso]

MetaBrainz Meeting 2017-04-03

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• picard-plugins & Travis
• picard-plugins issue tracking
• DR: MBS-9248 (postponed)
• Picard v2.0 (postponed)
• Picard comprehensive tags (postponed)

Reviews

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

so this week we released picard 1.4.1
which means… we finally pushed to 2.0 on the master
and we merged this behemoth of a PR → gh:P#503
i am expecting bugs so feel free to report em at Jira
did mostly 1.4.1 and migration to 2.0 work
and finalized and submitted my gsoc proposal

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Spent a bunch of time on IRC and forums, as usual.
Sent some big words to KEXP, which seems to have gone well, based on reports on how their editors have started behaving since that mail.
Bumped Discourse version.
Intervened in some Twitter conversation with a begruntled user, that might return now.
I bumped some user statuses for some GSoC applicants on the forums too.
And reverted the option for OTHER-290 based on last meeting.
I don’t think we’re evaluating that today though.

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

I had a pretty busy week, but I’ve been further ideating on the BookBrainz data layer to prep for WS work.
I also plan on looking at our BB proposal this evening.

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

dealt with support and sent some emails for an autoeditor election (thanks for the reminder, Freso)
We’re getting less MBID questions, it seems, but still a few
Dunno if something changed on the BBC or it was just a slow week though
Other than that, slow week
(well editing, of course)

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

not much from me today, just working on instruments and releases

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

This week, I worked on lots of bugfixes for LB. Specifically, artist_msids and user-generated data being dropped (LB-145 and LB-139), incrementing user listen counts in redis (LB-144) and user export of data (LB-146).
Also, made the final submission of my GSoC proposal and took part in a hackathon in the college over the weekend, where we made our VERY hacky implementation of a blockchain. It didn’t really go as well as planned.

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

Nothing much this week. I worked on migrating oauth client and moderation log code off the ORM and opened PRs in CB. Started working on some sql for initial creation of database.

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

I worked on verbiage a bit last week–we are making progress–but after a few days off, need to get back to it and see if we can’t finalize some pieces.
I also dove into invoicing and accounting with ruaok which will continue this week.
Thank you otringal, gcilou and CatQuest for banner designs and feedback on ORG-10. I uploaded two more mock up that we had discussed looking at—so soon we need to make a decision and make some nice clean new banners!
and we welcomed a Unicorn supporter and a Bronze supporter last week!!!
today I got to meet Loujjine and discuss data visualization for several hours–it was amazing–and Icelandic chocolate! Thank you Loujine!

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

well, quesito covered a few things already.
working with AEG Presents to get things nailed down and them squared away. it took a long time, but it worked out well in the end. props to them understanding that they were working with a tiny org.
then there is another possible supporter that we’re talking to, who wants special things. double unicorn trending towards triple unicorn.
then I spent a bunch of time friday sending out concert vouchers to people. I’ve got for Lotheric if s/he wants it.
everyone: If you got a picture of a Ticketmaster concert gift card/voucher, I mean for you to use it.
all of it. however you see fit. ensure that none goes to waste.
if you don’t want yours, please let me know I’ll shovel them around a bit.
I also did reviewing, merging and releasing of LB work that iliekcomputers__ has been doing.
next I need to review which bugs we need to fix before going full beta, but it should only be a handful.
oh and Paul Jessop, friend of MB, made a special 1 day trip to BCN to chat with me.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I mostly worked on schema change tickets
I finished mine except for the work languages one, which I started (finished the SQL, halfway done with the UI)
and I worked on a TemplateToolkit plugin that makes it possible to embed React components inside TT
so we can move our templates to React piecemeal
I think that’s all from me
other than code review

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

i dig Angelfish analytics tool a bit, just enough to find main drawbacks
then most of the time was spent preparing the 1.4.1 Picard release
I also fixed MBH-481, solution is a bit hacky, but it was urgent
I upgraded grafana and influxdb, and started to play with grafana alerts feature since now it supports Telegram (among others)
To finish, we had a bad event yesterday with a lot of load on MB website
not really identified the source, but the effects are showing weakness we need to work on
so i started to think about possible solutions, notably doing a proper rate limiting on websites too
the other axis, identified since months, is to improve MB website template system performance
because it doesn’t scale well with traffic

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week, I have polished and pushed SQL part for entity attributes (UI still in progress), without any change to the existing work attributes, as announced. The outcome of discussions with bitmap, Freso and reosarevok is that languages won’t be handled by entity attributes. Further potential improvements to attributes (such as short name for types and allowed values, free text for fallback “Other” values…) better have to be postponed rather than rash.
I’ve also investigated many recently reported issues by users and Sentry. Among those, a small bug in edit search led me to revisit and address the remaining subtasks of the long-awaited issue MBS-390. More edit search issues in progress.

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I’m still working on the indexer
the receiving part of triggers
updates should be working, still need to implement deletion support
and test it all
I also reviewed GSoC proposals, helped people with that

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

So this week I worked on getting my ES6 update to bookbrainz-data finished - so we have our first published npm package bookbrainz-data - npm (build is failing due to minor linting errors)
I also updated -site not to break because it used to point to the master branch of bookbrainz-data, which changes It now uses the stable npm version
And the last couple of days I’ve nearly got all the ES6 updates to -site done too
Apart from that, I did a little bit of proposal reviewing today, and helping out justharshal

picard-plugins & Travis

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Sophist suggests that we add tests for the Picard plugins in the picard-plugins repository, which no one disagreed with. He also suggested that we set up Travis for running the tests, which also no one disagreed with.

picard-plugins issue tracking

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Resuming discussion from last week, since @Sophist was around.

@Sophist

My thinking here is that the quality of Picard Plugins reflects on the quality of Picard. And sometimes plugins need minor changes in Picard and changes to the Picard website - and so it seems to me to make sense to use Jira for Plugin tickets too.

@Freso

I think picard-plugins should still live GH issues, since picard-plugins are not supported by “MetaBrainz”, but are meant to be much more like a “hotpot”(?) for Picard users to submit their things to.

@zas and @bitmap said they preferred to keep picard-plugins issues on GitHub for now, and maybe we can reevaluate again at a later point once Picard 2.0 is more developed.

DR: MBS-9248; Picard v2.0; Picard comprehensive tags

Postponed to future meetings, due to lack of time in this meeting.