Notes from #MetaBrainz Meeting 2017-05-22

[Freso]

MetaBrainz Meeting 2017-05-22

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• Move meeting time
• Collection spam

Reviews

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

nothing much to report apart from reviews or the time spent researching for last picard meeting’s plugin manifest

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

I’ve been working on issues blocking the Beta release of LB this week.
Sent PRs for a bunch of them, specifically LB-62, LB-153, LB-155, LB-157 and LB-159.
The last 4 of those have been merged, so yay!
Also, spent some time trying to fix LB-159, but that is a weird issue with influx, I think.
I asked on #influxdb for some help, but doesn’t seem like that chan gets much activity.
Hoping to get the rest of the beta issues done before I get started with GSoC in a week!

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was filled with uncool BS. conference calls, tag teaming big corporations with Quesito, accounting, board meeting and other silly shit.
almost no technical work, which nearly drove me insane.
this week ought to better.
we have a kitchen sink in the office as of today.
it was installed in the customary spanish style.
(e.g. a little bit janky)

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

last week I closed some tickets and tried to keep a few more things in motion–
I finished all the emails the the EURO side of our accounting transition
we’ve gotten some nice emails back, thank us for making this transition to fiscal calendar billing!
and so I have one small group left to tackle in the accounting transition project
also doing biz stuff with ruaok that continues this week…
and then I spend two days trying to get to Merica.
and had a minor set back with immigration/customs that was ham related (of course)…

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Last week, I reviewed fixes for latest schema change server release bugs (swiftly hot-fixed by bitmap), worked on small issues regarding external URLs and progressed towards the release of languishing MBS-8393.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I worked on finalizing the full/incremental json dumping code, and am deploying it atm, fixing any last remaining bugs that crop up
I’ll trigger the first full dump today

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

In the past 14 days I’ve been on IRC and the forums a lot, spent a bit of time on KEXP stuff (drsaunders, are they actually doing better now? It’s been a while since I’ve heard from them/you. :)), “been to” a couple of Picard meetings, dealt with some reported editors, updated Discourse, attended a MetaBrainz board meeting, … and that seems to sum it up.
I spent last Monday’s lack of meeting to finally get around to going to a local Irish Monday session (and brought along Quesito to try and indoctrinate her), which was great craic.
And I was at a talk about using contexts to (maybe) improve music recommendations at UPF earlier (with alastairp).
alastairp posted a picture in here of a table of timestamps and MBIDs. Which is always a beautiful thing to behold.

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I mostly did support, but I also went through all the new attributes yvanzo is adding since that’s technically style
We mostly agreed though except for changing one name so all good!
(and this code should allow a loooot more tickets to be closed eventually)

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

These two weeks I’ve worked on Taonga pūoro again, individual instruments and their retroactive tickets, adding some that were not in the wikipedia list, but is explained in the book I borrowed from library, as well as releases with those instruments - musicbrainz is now one of the more comprehensive databases about this music!
Made an edit to change a (potentially contentious) Name https://beta.musicbrainz.org/edit/45486948 (thanks to Freso for voting no to keep it open) if anyone else wants to chime in, vote on it, etcetra. that will be appreciated

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

so this week I worked on moving things to complete CB-230. hoping to complete it this week before the coding period
I worked on a couple of PRs CB-230: Migrate dump_manager.py off the ORM by ferbncode · Pull Request #103 · metabrainz/critiquebrainz · GitHub and CB-230: Migrate ws, frontend and db completely off the ORM by ferbncode · Pull Request #102 · metabrainz/critiquebrainz · GitHub for migrating (hopefully) all of the stuff in CB off the ORM.

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

I’ve been working on some more UI stuff for entities this week
Mainly refactoring and extending the code I wrote a while ago for Editions to the other entity types
but nothing too tricky, so it should be done as soon as I get some time. Then I’ll partially roll back the entity editor changes and finally release a load of stuff that’s been waiting too long
Maybe even get the GCI stuff out before I meet the GCI students in two weeks

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

Usual maintenance (plenty of security upgrades this week), minor fixes
Picard meeting, PRs review/merge
i also checked in details the reason of the increase of ws traffic, and there is nothing abnormal, just an increase of global traffic
Current situation: 1/3 of requests are honored, 2/3 ends in 503s

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

I helped do some more improvements on the metabrainz website, related to the way we display tiers and stuff
finished fixing tests for SIR
just need to deploy that again now with schema change updates
need to check if mbdata and other dependencies are up to date
also helped gsoc students get started with the projects
and done another jira upgrade

@ListMyCDs

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ListMyCDs

I’ve been reading React documentation and preparing myself for the next week.
Have to admit I’m still little bit of confused but it’s getting better every day

@psolanki

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@psolanki

Didn’t do much
Started working on the ratings project for CB
Finalized schema with Gentlecat
Also, I want a general opinion, should CB have rating on scale of 5 or 10

A bit of discussion on this ensued. Most support for a 5-scale but using a 100-scale in the backend, similar to MusicBrainz, for ease of possible transitioning. However, it should also possibly be brought up as its own agenda item if @psolanki wants to discuss it further.

Move meeting time

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

the current meeting time sucks. basta.
I picked the meeting time when we had more in the US and fewer in the EU.
now most of our weight has shifted to the EU and then come our friends from india.

Proposed new meeting time would be two hours earlier, so anchored at 19:00 CE(S)T instead of 21:00 CE(S)T (or 18 UTC during European winter, 17 UTC during European summer), which would put it at 10 AM on the US west coast which is pretty much the earliest we can go. Two hours earlier will put the meeting at 22:30 in India, while the current/previous time is half past midnight for Indians.

There was almost unanimous agreement, with only @SothoTalker voicing dislike for the new time. @Freso was assigned to update the meeting wiki/doc page.

Collection spam

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

we’ve been getting a lot of DMCA takedown requests for people entering spam links to pirated content into collections.
I tend to take copyright issues very seriously, so I wish for them to go away. soon.

@Freso

We have a couple of possible ways to deal with this:

1. Hide collections for non-logged in users entirely.
2. Make robots.txt not index collections.
   I thought of a 1a) earlier today that might also work:
   Hiding collections for “new” users.

Some discussion followed. @Gentlecat suggested putting limits on creation of collections instead of on viewing of them, which @bitmap followed up on and suggested «1b) block editing the description field for new users + users without a confirmed email». @yvanzo (re‐)suggested «We could disable “ Allow other users to see this collection” for limited users.»

It was decided to go with @Freso’s and @yvanzo’s suggestion of disabling public collections for limited users.

[Freso]

Note! Next Monday, May 29th, and all Mondays going forward, the Monday MetaBrainz meeting will happen two hours earlier than it’s used to. See https://musicbrainz.org/doc/MetaBrainz_Meeting for the current meeting time/details.

Also, the decision taken about “Collection spam” was partially reverted/changed during an informal IRC meeting/session/discussion on Tuesday. Discussion/talk starts from https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3915376/