#metabrainz

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.)

Oh!

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. :)

Fin!

CatQuest: Go!

hi!

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 :O

when I come home I'm looking at flutes and more.

Hadet på badet!

next is reosarevok !

Hi!

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: https://commons.wikimedia.org/wiki/Commons:Vill...

(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

That's about it for me. ruaok?

right.

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.

(Other people up: bitmap, Quesito, yvanzo; people maybe up (please confirm): Leo_Verto, alastairp, chhavi_; who did I miss?)

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.

fin. Leftmost!

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_!

Helo. :)

So I had a wonderful fulfilling (lots of gelato and chocolates) summit, thank you for that :D 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.

chhavi_: You'd be most welcome on the team. :)

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!

XD

fin! bitmap ?

hi

(I already created a UX label: https://tickets.metabrainz.org/issues/?jql=labe... )

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

Nice. :)

fin, yvanzo ?

hi

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.

(Other people maybe up (please confirm): Leo_Verto, alastairp; who did I miss? If not, yvanzo is the last one before moving on.)

fin.

If I missed anyone for reviews, now's the time to speak up.

I guess not.

Alright then!

bitmap: MBS-9353

MBS-9353: Do not show collections or user profiles to people not logged in https://tickets.metabrainz.org/browse/MBS-9353

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

MBS-9355: Do not allow an editor to set bio/link if the user is limited https://tickets.metabrainz.org/browse/MBS-9355

+1

I'm not sure what effect the login requirement had independent of MBS-9355 actually, Freso or reosarevok might have a better feeling

I'm not sure either. It seems to me (based on non-hard data) that spammers have moved to making entities.

Same in both counts

right, I'm guessing it helped but it'd be nice if we stopped blocking the entire page

(But I don't want to crack down too hard on that until we have SpamBrainz in place, so we can collect data while cracking down.)

(Because ❤️ data.)

bitmap: I agree.

+1

reosarevok, ruaok, Leo_Verto: Any thoughts?

If not, I guess it's motion carried.

I'd like to have world-viewable user descriptions so maybe some day we can have keybase verification for MB accounts

I think it's fine to open it up

If it makes anything worse, we revert

I don't think we should prevent setting collection description for limited users.

Leo_Verto: ++++++

but yeah, I'm all for opening up stuff, at least for unlimited users

Just not displaying it should be enough.

would it be an idea to explai somewhere accessible to people signing up, that these limitatis are *becasue* spaammers?

CatQuest: Yes, a very good idea.

+10

Okay, so.

bitmap, want to summarise?

I guess we just "hide the collection description or user bio/website if you're not logged in"

that seems to be what everyone's ok with here

Sounds good to me. Only of limited users, or in general?

only of not-logged-in users

(like, should we just hide all descriptions and say "log in to see this?")

oh, right

+1

Doesn't sound like a bad idea.

I'd be fine with just doing limited users to start

if we can implement the least amount of restrictions that actually helps deter spam, that's good

+1

+1

I don't mind either way, just thought that maybe hiding it from everyone will send a message to the spammers or something that it's pointless

Eh, dunno :) Either way works

fine by me too

So just a "log in to see this" on limited user profiles.

and collections

Yes.

bitmap: ^ ?

yes, collections descriptions, user bios, and user websites

sounds good

Ok, if it's only in limited user stuff it really needs to specify it's for spam reasons in the log in message :)

Alright!

MBS-9505: time period to edit your own entries https://tickets.metabrainz.org/browse/MBS-9505

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?

can't we add "remove relationships to entities, what you've added yourself to that?

1 week seems a lot but 1 day seems fine to me

+1 to 1 day!

I'd say maybe 6 or 12 hours. 1 day also seems overly long to me.

But that's bikeshedding I guess.

1 hours is too short

Esp. since it also has the restrictiong of "no one else has edited in the meantime".

I don't see any technical (or other) reason that prevent us from extending this delay to 1 week.

Agreed that 1 hour is too short.

week is a bit loong

i thin k24 hours is good

If we make it 1 week, we might as well make it 1 month. And we might as well make it 1 year. And we might as well make it 1 decade.

A week just feels like people wouldn't really think of it as a new addition anymore

people rest, rethink, ask, read docs, realsie what hey did wrong, etc

after one week other users may already haved tagged the release using the data and this may be used in destructive ways

But 1 day, half a day, whatever, seems good

More than one hour at least is definitely a good idea