Also fixed a regression with replication cron job.
Otherwise worked on user admin stuff and spam ninja ui.
Plus usual PR reviews, doc updates, small fixes, Jira admin, etc.
That's all from me, go alastairp?
alastairp
🌊
ZaphodBeeblebrox
\o\
alastairp
a few things last week. I was also involved in this meeting for listenbrainz planning/integration of all of the SoC projects and other things
I did a few reviews for work that iliekcomputers and others were working on
I spent some time reading academic articles about recommendations, and am putting together on overview on the current state of the art, including the types of data that they need, so that we can see what we can build with our data
I also met with jmp_music to help him with his continuing work on AcousticBrainz
that's it. diru1100?
diru1100
Hello Everyone!
Freso
(Only _lucifer and Cyna[m] left on my list. Last call for anyone else who may want to give a review.)
diru1100
Last week I mostly explored on generating data for LodBrok.
Also got more clarity on how to proceed for GSoC after talking with yvanzo and LeoVerto.
Used the data given by Freso as reference to generate data for bio, email and url parameters.
This week I plan on completing generating the data and keeping the model in flask API.
Thank you, that's it
Freso
diru1100: Pick the next one to go.
diru1100
_lucifer: ?
_lucifer
hi all
I worked on refactoring the app for the last few days
It going good, I have reduced many modules to 1/4th of original
without loss of readability of code
thats it for me
Cyna[m]: nex?
Freso
No Cyna[m]?
I guess we move on from reviews then…
Thank you everyone for your reviews. :)
We have two more items on the agenda.
reo: 2 accounts 1 email
ZaphodBeeblebrox
eewww
Freso
I didn’t see any discussion on this on IRC, forums, or on the ticket.
ORG-40: Update wording of the MetaBrainz projects' Codes of Conduct
reosarevok
I like your rewording
Freso
Essentially, this is about adding a clause in the general MeB about explicitly disallowing sockpuppeteering and other misuse of accounts across all MeB projects.
reosarevok
In the forum
Mr_Monkey
Capital idea
reosarevok
I don't see any negatives
So, might as well?
Freso
I noticed talk earlier this week about a possible "listen bot" on LB too, which such a clause should also encompass.
Mr_Monkey
We've recently detected someon gaming LB data
ZaphodBeeblebrox
but "bots" in general woudl be exempt for mthis (liek we discussed last time)
wat
Freso
OTOH, this could also simple be included in the "be polite" first clause.
ZaphodBeeblebrox
lb data? what
Freso
The current CoC is already somewhat vague, but we also have very specific points (non-gendered language).
ZaphodBeeblebrox
I think having a spesific "don't have sockpuppets/ban-aversion" is good idea
Freso
ruaok: What’s your gut feeling?
ruaok
I'm for it.
ZaphodBeeblebrox nods
Mr_Monkey
I think specific language allows us to deal with abusive accounts swiftly
Without the need for ulterior justification/discussion
Freso
Alright. I see lots of people here for it, and no one against it. :)
ruaok
let me take a look at it and see if i can craft something.
I'll have something for the meeting next week, how does that sound?
ZaphodBeeblebrox
also, we are a failry fair(?) community. if someoen had legit reasons for more accounts the we would listen
eg bots. etc
yvanzo
+1
Freso
ruaok: I can write something up. I think I had a "draft" of sorts in the forum post.
ruaok
ok, turn that into a PR and then tag me as a reviewer, please.
rdswift thinks multiple accounts could be requested / approved in advance.
Freso
Will do. :)
yvanzo
It could even be generalized about “do not abuse system resources” and mention multiple accounts in particular (I think about rate limiting too).
Freso
yvanzo: Can you make a comment about that on ORG-40?
Okay. I just have no experience with documentation licenses.
Freso
I know ruaok has been advocating for basically getting rid of licenses for a while.
rdswift
Currently using GNU documentation license.
Freso
IIRC, the GDL is a bit clunky and has some weird clauses?
Wiki.MB is CC by-nc-sa
rdswift
Yes. Thus my question. Okay, I'll look at CC-by and CC0. Thanks.
That's it for me.
Freso
CC-by is basically MIT/BSD-like. CC0 is public domain-like.
But yeah. Might want to ask outsidecontext or zas at some point as well if they have any thoughts.
Anyway.
zas
I don't (about licenses)
Freso
That concludes today’s meeting.
Thank you everyone for your time. :) Stay safe out there!
</BANG>
Mr_Monkey
Thank you !
ZaphodBeeblebrox: Thanks for beta testing !
ZaphodBeeblebrox
I'm making another :D
ruaok
I think we should use cc0 for everything new.
rdswift
SGTM.
ZaphodBeeblebrox
ok, I know what "lgtm" means but wtf is "sgtm"??
Freso
ZaphodBeeblebrox: Sounds GTM
ZaphodBeeblebrox
..
ack
thanks freso
Freso
đź‘Ť
ZaphodBeeblebrox
also i have a pm for you (very short not a wall of words :D9
Mr_Monkey: can we have a component "merge" or similar?
Freso
I prefer SGTM to LGTM because I get the latter confused with LGBT and then I get very confused. :p
Mr_Monkey
ZaphodBeeblebrox: "Merging" subcomponentn create
ZaphodBeeblebrox
cheers!
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC students start here: https://bit.ly/2NUaxgb | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Meeting agenda: Reviews, Sockpuppet/system gaming MeB CoC clause [ORG-40] (Freso)
Right. I'm writing a tutorial at the moment, which explains that you can't edit the entities during a merge. You have to do edits before or after the merge.
