Notes from #MetaBrainz Meeting 2017-10-09

[Freso]

MetaBrainz Meeting 2017-10-09

Meeting start: https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/4013257/

Agenda

• Reviews
• MBS-9353: Do not show collections or user profiles to people not logged in
• MBS-9505: time period to edit your own entries
• Google Code‐in

Reviews

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

I came back from the awesome bcn summit, set up gcloud VMs for loujine’s visualizations, with the help of ruaok (a MB replicating database is now available on gcloud to be used by others VMs).
I set up few more nagios alerts concerning SSL certificates expiration.
I restored qnap IP blacklist, to reduce useless network traffic and load on gateways.
Googlebot indexation started over few days ago, that’s something like 8M hits per day. It explains the higher than usual loads we have on servers.
I did security upgrades and usual supervision. Discourse was upgraded too.
I’m flying to SFO today, going to Google headquarters on Friday for gsoc mentor summit. Tourist/zombie mode enabled this start of week.

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

For this week I don’t have much to report, but during the summit week, I completed dockerizing acousticbrainz AB-297(thanks iliekcomputers for the help). Other than that, added some GCI tasks for CB. Also started some work on CB-270.

@LordSputnik

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LordSputnik

This week I thought about form validation, which we need to finish off the new entity editing forms. I’ve started putting together a validator for the publisher form, which should be done soon.
This validator can be run client side and server side, and should improve server reliability and allow us to give better feedback to users on the editing form.
After this, I’ll write validators for the remaining entities. Once that’s done, we’ll test and do a new site release. And then I’ll be moving in to writing the new relationship editor.

@paramsingh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@paramsingh

I’m traveling to college today so will probably not make it to the meeting. This week, I made a couple minor fixes in the metabrainz.org site, did some code review for AB and LB, addressed some code review in LB for my PRs.

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

got back home today
starting to gear up back in action, just finished setting up the solr repo on my local machine and solcing a solr bug SOLR-49
also fixed up the GCI page for picard and added myself as a mentor

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

So in the last two weeks since the last meeting, I think the most prominent thing that happened for me was attending the summit - and organising the live streaming of it.
For anyone who missed it, the streams can be seen at https://www.youtube.com/playlist?list=PLDFCBbxgWJO-pvM-9Y3fKdFwc3hL_i5nC
Other than that, I helped a bit with the classical cleanup post, made a blog post about the stream, did some Twitter stuff, looked a bit into OTHER-302, and did some Discourse version updating.
I was also in a bit of conversation with Wikimedia Commons about updating the logos we had at their MusicBrainz page (which I also got made into a #REDIRECT to MetaBrainz (it used to be the other way around)).
Still a bit more to do there, but nothing insurmountable.
I added some spam tickets related to some pre-summit discussions about the spam situation.
Related to which, I’ve been declared Spam Sensei - but I think we’ll talk more about that at a later point (probably a blog post?) once some more of the needed development behind it has been done.
It’s a bit too much to talk about during reviews anyway.
I also dealt a bit with some reported editors and spent time on IRC and the forums.
(Most of this was two weeks ago - like pretty much everyone, I ended up catching the cold/flu that was circulating during the summit, so most of this last week, I was in bed and feeling miserable and unable to focus too long.)
I also started poking at Google Code-in - poking potential mentors, asking people to ask suggestions, etc.
But more about this by the end of the meeting.

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

currently on borrowed mobile internet at my mother’s cousin’s house!
I’ve been finishing up the debussy and i’ll be looking at instruments, but I probably won’t be online much since they have limited internet (mobile broadband) and I don’t want to use it up for the month for them
when I come home I’m looking at flutes and more.

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

So, I had a nice summit, then I had a less nice cold (although not as bad as Freso, it seems)
I started a conversation with Commons on artist images: Commons:Village pump - Wikimedia Commons
(it seems we have a difference of opinion in that they don’t consider small hobbyists worth storing an image for, while we do, but it’d seem like their notability requirements are lower than Wikipedia’s, at least)
Other than that, I wrote back to Lisa from DRAM (New World Records etc)
Did some support, edited some Mahler and some not-Mahler

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

I too had the cold, as nearly all of you heard. My was cut short because I started eating slices of raw ginger throughout the day.
nasty all around, but very effective.
well, that was my contribution to ColdBrainz.
I did a lot of lead-up to the summit, the summit and then trying to chill out afterwards.
I’ve been doing some LB stuff, but I keep getting sidetracked by accounting which we now do on a quaterly basis.
while it takes a little longer, overall there is less time spent on dealing with accounting, which is great.
sadly, Quesito and I are in a spat over renewing her contract and we’re not close to reaching an agreement.
so, you can expect Quesito to not be around until we sort this out.
not fun at all, as you might imagine.
also, I dealt with AirBnB aftermath stuff.
we were accused of breaking the washer, but the renter finally realized it was the tenants previous to us, so that is all set.

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

I attended the summit, worked with Rob and Ben on a plan to try to get BB ready for the masses, and investigated ways to improve the reliability of the BookBrainz site code.
More on the plan as we get settled.
Next up is working to dockerize the server.
In the meantime, I’m recovering from the same cold and traveling, so it’ll be a light week.

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

So I had a wonderful fulfilling (lots of gelato and chocolates) summit, thank you for that Just got back this afternoon.
Added a GCI task for design, might add a few more in upcoming days. Might also add myself as a mentor, still debating that one.
Other than that, this week I look forward to *eating Freso 's head * to set up JIRA for our design component. and working on the artist page!

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

got back tuesday night with cold but feel somewhat better today
spent most of the week converting the sidebar on our entity pages to react, which is actually a massive undertaking, but should be done in a few days now
flying to SFO tomorrow morning but should be on IRC throughout the week

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Managed to escape Catalonia on Tuesday, got back home on Friday.
I reviewed more PRs including JSON dump, lodash update to v4, JS flow types.
Added a report for admins to look at newest limited editors, in beta soon.
Worked on batch-removing known spam accounts using proper hooks.

MBS-9353: Do not show collections or user profiles to people not logged in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

we made it so you need to be logged in to see user and collection pages
can we ease this so just the collection description or user bio/website is hidden if you’re not logged in?
we could also implement something like MBS-9355 for the collection description
I’m not sure what effect the login requirement had independent of MBS-9355 actually, Freso or reosarevok might have a better feeling

A number of variants to undoing this hiding was discussed, and the meeting finalised on only hiding collection descriptions, user bios, and user websites of limited editor accounts for non-logged in users (behind a “log in to see this, because of spam” message).

MBS-9505: time period to edit your own entries

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

Just a reminder: “amending an entity” is for having non-destructive edits automatically accepted for entities you recently created and nobody else edited in the meantime.
This ticket is twofold:

1. Allow amending destructive edits (e.g. removing a medium mistakenly added to a release you just added). I prefer to keep away from this for safety.
2. Provide more time for editors to amend entities they just added.

This topic is bout 2nd point: The delay is currently set to 1 hour. Would it be fine to extend it to 1 day or 1 week?

Some discussion about whether to do 1 week, 1 day, 12 hours, or some other time frame. In the end, 24 hours was agreed on.

Google Code‐in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

So, Google Code-in org. application has started!
I will put in application for MetaBrainz immediately after tonight’s meeting.
(Or at least start on it.)
For mentors from previous years, if you want to mentor again, please add yourselves to Google Code-in/2017 - MusicBrainz Wiki and poke me.
For people who want to be mentors, please read over Google Code-in/2017 - MusicBrainz Wiki and Google Code/in’s own documentation and then poke me about it.
We really, really, really need a lot more suggestions on Google Code-in/2017/Task suggestions - MusicBrainz Wiki
So please think about whatever things you’re involved with related to *Brainz and see if there are any tasks that can be potential GCI tasks.
Remember that it’s not just coding tasks (“CODE”), but also documentation/training, outreach/research, quality assurance (testing), and user interface(!!) tasks.

Some additional discussion ensued with questions about possible tasks and nudges of specific community members to contribute to the task suggestions.