#metabrainz

did oy ubuy the big one or the little one, the mber or the sliver?

Freso: how about this? I just buy some whiteboard paint. will you help me paint a couple of walls?

mayhem: That sounds like a good idea, actually. Sure!

you may or may not remember IA's solution. At least that's where I first saw it done.

cheap as chips in the US, expensive here. better keep googling.

CatQuest: I don't...

They put sheets of glass on the walls.

Oh.

what?

neat

harder for us. painting wall is doable, methinks.

glass + white wall = whiteboard that you can accidentally use a sharpie on.

CatQuest: Sorry. Missed an l before that tab!

I like CallerNo6 idea

CallerNo6: understood. and ideal.

Mineo are you free now to discuss picard review for https://github.com/metabrainz/picard/pull/586 I couldn't get your comments entirely :), I didn't get 1 and 3 and I think 2 and 4 are out of scope for that PR?

huh, it seems like the code I have in the listenbrainztest_db for messybrainz is an old version which is causing a syntax error

mayhem: So whiteboard paint or wallglass?

Or "still looking"? :)

(and that building them involves tools and crap)

plush pigs are probably ok

I think I have it fixed, I'm building from docker-compose.test.yml again, hopefully that brings the new messybrainz repo and fixes it

Freso: went with v2 for the plugins api for now, I think all v2 plugins should be backwards compatible for an api level of v2, in case we decide to make some extremely breaking changes in say picard 2.7 we can bump the api level (which makes sense since v2.7 should not have any breaking changes for previous apis, and by breaking changes I mean something like

updating all plugins to qt6 or something of the like) Picard anyway checks the api levels of plugins before showing them in the plugin list so if we introduce new plugin points in say v2.7 and there are plugins made for that, they wont be shown in picard 2.6

hmm I've tweaked quite a lot of he translations.. gonna wait until tomorrows build to see all these changes and make the finals tweaks i think.

hmm I can show /per/ file things are in. that hleps with context and grouping stuff to focus at one time \o/

CatQuest: someone will have to repull the translations again for that to happen :P

CatQuest: Did you ever figure out where release type names were taken from?

Freso: no i was not :/

did not*

CatQuest: There should be an "attributes" or something translate repository thing.

it's in there?

great. i'll look inot it tomorrow/saturdady

saturdaddy

saturday :)

^

yea

ok *fine* i'll do it now :P

help*

CatQuest: Oh, that wasn't what I meant to do. Sorry. I just was already there, so I thought I'd make it easier for you when you had time. :/

Freso: that's ok :)

it makes it easier

too easy :P

:p

ja! i found it!

hah, it was n't me

[picard-plugins] antlarr opened pull request #80: PICARD-983, PICARD-984: Fix wikidata plugin genre merges and ui problems (master...master) https://git.io/vDzHo

CallerNo6: In reference to - https://chatlogs.metabrainz.org/brainzbot/metab... Sure! Also, the dates are out, so maybe we can talk about meeting sometime soon :) (Although it might be a bit too early to plan for June)

SothoTalKer: It isn't my birthday today. It was like 20 days ago :)

anshuman73: i meant happy new year then :))

anshuman73: The GCI meeting dates have not been established yet, have they?

Freso: They have, I got a mail confirming the dates.

Ah, alright then. 👍

anshuman73: maybe i just confused the dates xD congratulations for being a winner :3

Freso: They have divided the trip in two this year, half the orgs go in first week of June and the other half go in the last week

alastairp: re that test.sh problem, I did a docker-compose build from docker-compose.test.yml and it worked. :)

SothoTalKer: :)

anshuman73: Yes, I knew that much. Hence why I thought they hadn't divided up the org.s yet. ;)

anshuman73: Do you know which other org.s are in the same slot as MeB?

Freso: also, saw the blog post ! Nice job with it !

Freso: No, not yet.

although, it should be clear in a few days time, they said they'll be making chat groups

anshuman73: "Tasks done" paragraph?

I meant the paragraph in the blog post listing out the specific things/tasks done by students

s/paragraph/paragraph(s)

zas ping

Freso: kött (and köttbullar).

elkmeat :D

bitmap: Good that you identified the issue with the BEFORE DELETE triggers. I had started wondering whether pgbouncer had gone into statement mode somehow, myself.

bitmap: Did you remove the triggers? In that case, I would close the tickets that were likely caused by this.

ah the blog! can someone link that, i think i missed that link

danke!

for a moment i wondered who "mers" was

chirlu: triggers were removed, yes

Is the stuff that shouldn't be there (like https://musicbrainz.org/release/68c69d72-8769-4...) supposed to be removed automatically somehow, or should we deal with it manually?

nice blog post Freso!

Thanks.

How does beets fit into MeB?

beets me

LOL....

Heh, someone else asking about genre in bizdev

"Do you have any plans for this in future?" yes we plan to discuss it on our summits forever! :D

Seems like too small a task for GSoC.

now.. is genre a subjective or objective thing? :)

Measurements show it’s 99.9% objective.

Polls show it's 73⅓% subjective.

chirlu: dunno, it's on the list from last year

those polls are rigged O:-)

iliekcomputers: did you fix the problem?

gsoc

with the msb init

CatQuest: the initial implementation indicated in https://wiki.musicbrainz.org/Development/Summer... is definitely not too big for gsoc

\o/

It doesn't sound that much smaller than some of our past gsoc projects though

indeed

In any case, if nobody picks it (like last year) then it won't matter :(

there is no rason a gsoc shoud be Hella huge so much that it requires 3-4 years of followup

all this talk about MB has got me interested in perl :P

Well, that was more like "we need this but can't do it so maybe we can advance it with gsoc"

iliekcomputers: the issue is that your image contains an old version of messybrainz code - I've fixed this. You will have to re-build the image so that it gets new messybrainz code

I tried learning it a couple of weeks back but then gave up because of readability :P

samj1912: \o/

mb has "very clean perl code" tho

What readability issues did you have?

<3<3<3

"Replace [multiple] language with proper multiple languages" is the one that kinda sounds too small for gsoc to me

chirlu: perl in general, not MB

Quesito: beets is a 3rd party tagger that uses MusicBrainz (and AcousticBrainz) data.

reosarevok: from the description it sounds like a rather large project.

I mean, sure, it's a schema change, but other than that, is it that complex? We can't break the ws so it'd just involve keeping printing [Multiple] where we do now if there's more than one and adding another bit with all the languages I guess, and the UI itself could be basically the same as for selecting multiple instruments for one rel

Quesito: It's listed at https://metabrainz.org/supporters

(IIRC... *checks*)

!!!

sampsyo!

And well, there's the SQL, but SQL is easy