Notes from #MetaBrainz Meeting 2017-05-29

[Freso]

MetaBrainz Meeting 2017-05-29

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Renaming some key instruments

Reviews

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

This week I released the “next” fix version, started writing up the upcoming instrument blogposts, and finished the Taonga pūoro instruments! Thanks to Freso and reosarevok for helping me!
Finally the “Turboneger” edit closed with a record 17 yes vs. 1 no*!
Thank you everyone that voted and helped make this a great consensus!
* extra thanks to freso who voted no to keep it open but "for the record: agreed with this edit. "

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Spent time on IRC and forums, went through a bunch of spam accounts and deleted them while collecting data, handled some reported editors, upgraded Discourse, removed some DMCA reported spam and spam on Jira, attended Picard meeting.

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was a lot of BS contracts, paper work and silly shit. not terribly interesting.
but, we have JSON data dumps starting to appear now.
which is really really cool and something that people have wanted for a long time.
on top of that we have incremental JSON dumps that will be happening soon.
so, soon people will have two choices for staying up to date with, which may get us more customers, since our data becomes easier to consume.
oh, we have a kitchen sink at the office now.
so we can do dishes and fill up the brita without doing contortions.
and there is another unicorn on the horizon, which makes me very happy.
but, we have a lot of BS stuff moved out of the way, so I should have more time for LB stuffs.
also, I’ll be AFK from June 8 - June 16.
I’ll be working minimal hours – mostly checking email and such. but really mostly eating.
also, our finances are looking really nice. thanks to Quesito!
I’ve promised the board to go easy on expenses for a while and hoard a little more cash, but if things continue we have more money for another engineer. also, we should start doing UX stuff soon.

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

last week, jet lag hit me pretty hard, and I slacked a bit…
mainly kept up with emails and accounting q’s
and did some help with ruaok on the BS stuff, which was exciting to see finalize
I’ll be setting up the social media banner contest this week!
and need to get back to some forum discussion too…

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I did support, made a few changes to style/artist since someone added a ticket notifying me of it being inaccurate
Finally submitted my graduation paper (only the defence left)
Today and tomorrow I’m checking an archivism conference in the National Archives here in town, which is pretty cool
(also lots of good cake)
I talked to bitmap about maybe doing a bit of TT to react work now that I have more time
Let’s see how that goes

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

well, usual supervision and minor fixes, security upgrades
worked on a tool to extract interesting numbers from our fat mb logs
started a deep analysis of it, looking for heavy low hanging fruits to reduce unneeded/unwanted traffic on our resources-hungry website
found out that Yahoo Slurp is 25% of hits
and i’m working with bitmap to modify robots.txt
slurp is the yahoo bot indexing pages
it indexes /track/ which are mostly redirects (303)
and don’t even get the target url
so we can skip 87k hits a day
just for this bot
also worked a bit on Picard, attended to tuesday’s meeting, answered few bug reports
fixed (partially) plugins api issue on new picard website

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

mostly worked on finishing the json dumps, those seem to be working fine now so I enabled cron in the container and the incremental ones have been generating for the past couple days
just needs the metabrainz.org endpoint
also worked on fixing MBS-9342

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I reviewed a bunch of DB changes for critiquebrainz again
done a bit more work on schema updates for solr
helped fix some issues with the metabrainz website
and started looking into that endpoint bitmap has mentioned

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week, I worked on measures against spammers, digged into MB caching, and tracked bugs in editing system.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

I did a bunch of work on LB this week, slowly but steadily getting through the issues stopping us from getting to beta.
The most notable of which were a kinda big refactor of LB and setting up docker for MessyBrainz.
There’s not many issues remaining for the beta release, but I’ll be starting on the GSoC project soon (coding period starts tomorrow), so big things on the horizon for LB!

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

this week I worked on improving code for migrating code off the ORM for dump_manager.py,
Also, to fix filtering of reviews according to entity type on browse pages, i worked on CB-257: Fix filtering reviews based on entity type by ferbncode · Pull Request #104 · metabrainz/critiquebrainz · GitHub
Also worked on CB-237, only managed to find a work around by installing libbz2-dev and rebuilding python during docker build.
Cleared some doubts related to setup of my MB database in dev env. very excited for the coding period. begins tomorrow

@ListMyCDs.com

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ListMyCDs.com

I’ve been preparing myself for gsoc but there’s really not that much to report at this stage.
Coding officially starts tomorrow!

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

Don’t have much to report. Will start coding phase 2 of my Gsoc project this week. There haven’t been any picard dev bug reports to fix which makes me think we don’t have enough beta testers. Also fixed the picard and plugin branches on github.
Also forgot that last week was a 2week review and I didn’t mention the inclusion of high dpi support for picard, new icons and picard dev on pip

Renaming some key instruments

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Based on the discussion in Drums vs. drumset @ApeKattQuest_MonkeyPython wanted to ask the meeting about renaming e.g. “drumset” to “drums (drumset)”. Several people voiced support for this and no one said anything against it.