#metabrainz

hi!

(Only dragonzeron and bukwurm_ are left on my list. Last chance to jump in!)

Last week I worked on the reviews done by ruaok for LB-352, LB-367. And started to work on creating artist clusters where I got stuck after finding LB-368. I believe LB-368 extends to LB too

LB-352: MessyBrainz: Add script to fetch artist MBIDs provided recording MBIDs from MusicBrainz https://tickets.metabrainz.org/browse/LB-352

LB-367: MessyBrainz: Add script to create recording clusters https://tickets.metabrainz.org/browse/LB-367

LB-368: MessyBrainz: Sort artist_mbids before inserting into the recording_json table https://tickets.metabrainz.org/browse/LB-368

fin

dragonzeron: go

Alright

so I have been working on mass ISRCS adding and doing some Japanese cover albums

however whenever I link the Amazon link to the album the image from amazon does not come up I dont know what the issue is cause I did not have problems before a few month ago

and Now I have to manually add the album picture to the album on mb

so I was wondering if you guys could possibly look into that

sounds like a ticket to me

dragonzeron: Amazon cover images are a bit hit-and-miss. Generally, if you're sure what Amazon has is correct (it isn't always), uploading it to CAA is preferred.

indeed

Yeah most of the time they are those

and I make sure to by getting the correct image

Anyway. Anything else?

Nope Arigatou

bukwurm_: Around?

Let's move on for now. If bukwurm_ comes around, they can give review after…

zas: GitHub!

grrrr

voilà.

🎉 🎉

Cheers for the bride!

but m$ ruins services and we need to expect that github will become unusable soon

exactly

Sigh

I'd say we're in a pretty good position regarding github right now

Are we really going to not even wait and see at all?

Well, I am not sure we should start packing before even thing are clear

About the comparison with FB/React, FB doesn’t have history of ruining software, whereas MS is the inventor of the strategy “Embrace, extend, and extinguish”.

We have a bitbucket mirror we can turn back into main first

Microsoft's track record isn't really good tbh.

If needed

we'll wait, but better make the B plan soon

we only use it for code, tickets and wiki are already hosted elsewhere so a migration to say Gitlab shouldn't be too complicated

I'm all for moving to GitLab, since GitLab is More OpenSource™ than GitHub anyway, but I'm also with reosarevok: let's wait and see what happens.

I guess the best way to go about this is to set up a gitlab mirror

Isn't gitlab having issues dealing with all the new load anyway?

lets hope for the best "Deal not finalized still. will take up a few months"

I mean, if we were to self-host gitlab then sure, but I don't think we want that

About the example of Xamarin, there has been patent issues with its former independent version Mono.

And in case things do change, we can switch over

+1 reo and freso

reosarevok, can't tell, their public dashboard is overloaded right now :P

+1 samj1912

I don't think we could go wrong reserving the relevant namespaces on gitlab so +1 samj1912

that's what is said before the meeting "watch thme with argus eyes. if things change for thre woorse. move our shit asap

wait and see, but be ready is my take

maybe we could do somekind of a slow move to gitlab

I donBt think anyone disagrees that a plan B has to be prepared just in case.

start with a gitlab mirror

+1000 ruaok

and then eventually (tm) move away from github anyways

(considering that gitlab is closer to oss)

for now, keep your eyes peeled and watch for trouble.

ok argus eyes means "look very closely"

so yea, what I said :D

I don't want to leave github just yet, it offers a lot of visibility and is much better community wise than gitlab.

gitlab's got a pretty neat importer so someone with admin rights on the meb org could import all the projects as a preliminary mirror

is that importer overloaded rn? :P

samj1912: prepare for desillusion ;)

not a bad idea. and will send a message

If it does end up being unusable we can switch to gitlab (since we will have the mirror and all)

I think it's fine waiting a few days.

+1 to that

GitHub is not going to "die" in a week and GitLab is getting stress tested enough right now as-is. :)

iliekcomputers, probably not but their grafana is https://monitor.gitlab.net/dashboard/db/github-... :P

mirror to gitlab and keep watching them intentily

If github continues to work "independently" maybe we can stick to github

^^ Freso +1

Sourceforge is still around ... ;)

has anyone used gitlab's code review? is it usable?

shush, zas :P

it is?

oh yea. right. so is last fm .. but

bitmap: IIRC, yes. I've been hosting my personal projects on GitLab for a while, and I think I've had a single PR there. :p

now I'm curious if gitlab will let me actulaly use thier website with the older broser :D

Anyway.

bitmap, haven't used it but according to this blog it's pretty similar to github's https://yalantis.com/blog/code-review-via-gitla...

Seems like conversation is stalling.

no other alternative ?

Leo__Verto: More like the other way around, IIRC. :p

bitbucket but we moved the private repos away from that for reasons, right?

I think the best way to go about this is mirror all our repos with a sync. And switch over when the GH cons outweigh the pros

ಠ_ಠ

Gitlab model isn't that great, they don't offer anything special to open source orgs

really, we should not start a move just yet.

please let just look at alternatives for the time being and not make any decisions for now.

+1

sure

watch and make plans

+1

makes sense

Anything else anyone wants to add to the discussion? Or can we let ruaok's words be the final ones for this discussion?

zas, do we need any GitLab EE features? Private repos are free for everyone

Leo__Verto: Maybe you can discuss GitLab things post-meeting. :)

Leo__Verto: for how long ? now it may changes

Freso, sure

bukwurm_ is still not around, so…

(Or I haven't seen anything from them.)

Thanks for your time everyone!

Have a great evening!

</BANG>

Thanks !

Thanks!

kartikeyaSh: hi

iliekcomputers: hey, how was your holiday?

pretty good, thanks.

bathing in a lake sounds awesome!

I'd like to talk about your brainzutils PR

iliekcomputers: let's talk

the sqlalchemy version thing is weird.

I agree with your point that each of our projects should ideally use the same version of sqlalchemy.

but they don't right now.

Leo__Verto: this is what pico is to me : https://en.wikipedia.org/wiki/Pico-

what to do about it? any suggested solutions?

Given that the new code you add is gonna be used in MessyBrainz and AcousticBrainz, i'd like to use the latest version that works with both of them.

thank you

rsh7 has been using the musicbrainz module in AB, so she probably has info about which versions work with AB.

rsh7: ?

iliekcomputers: do you have any logs for CB ?

kartikeyaSh: not right now, I'll try to come up with some tomorrow. I tested it a week ago, and promptly forgot to save logs.

anyways, eventually all our projects will use brainzutils for MB access anyways, so we'll converge to a single version.

AB uses SQLAlchemy == 1.2.5

iliekcomputers, kartikeyaSh: AB is using 1.2.5 right now.

kartikeyaSh: I don't think messybrainz would have any problems with 1.2.5 either?

let me change that and see if it works

zas, okay, skimming over gitlab's feature page (https://about.gitlab.com/features/) it seems like we'd lose the following features when migrating from GH: a bunch of ticket stuff that is irrelevant as we don't use GH issues, requiring PR approvals, restrict pushing to master on a per-user basis (groups might be in CE, not sure)

heh

it does come with some sort of JIRA integration which seems better than GH's https://about.gitlab.com/features/jira/

iliekcomputers: CB uses SQLAlchemy==1.1.13

so AB has the latest one

tbh, I'd like to move all of them to 1.2.5 if possible.

maybe something else was wrong not sqlalchemy

possible.

I'll try 1.2.5

Freso: Sorry, I missed the meeting without prior notice. Got stuck in some nasty traffic, and had no way to communicate. 😅

on MeB

i'll take a look again tomorrow.

on msb, you mean, yes?