#metabrainz

discussing with ruok tonight about it, we'll go for snapshots (processing only each 3 days)

ruaok: yo momma's fat

A fat log is a sturdy log.

LordSputnik +1

so we can get a general view of web service

LordSputnik: at least she ain't ugly, like Leftmost's momma

here

apart that, i did usual maintainance, PR reviews, and a bunch of MB edits

also i made it to BCN ;)

🙌

Freso: yo momma's got a sturdy log?

Hope to meet you all soon ;)

Not that I know of.

benvinguda zas!

lol

Next ? alastairp ?

hi

last week I was in meetings *all* week, so didn't do much

ahah

although I did a bit of hacking to try and get an API using GraphQL, and getting data from a database

as a quick hack

seems to work really well. Freso pointed me at another implementation which just hits our ws. it could be interesting to get a proof of concept going to see

nice thing is it lets you specify exactly what fields/relationships you want returned in a request

I did?

!m Freso

You're doing good work, Freso!

oh, maybe it was reosarevok

other than that, I did a bit of code review for ruaok and some AB review

a bit of planning for SoC

To which we're accepted! yay

fin. ruaok ?

\o/

etc

last week I was battling a cold so things moved slower than usual.

(Other people up: Gentlecat bitmap LordSputnik - anyone feeling left out, raise your hand. :))

You fought the cold and the cold won?

I spent quite a bit of time working LB and getting the PR count down. some talking about LB and general philosophy on computer science with iliekcomputers.

some shit talking to SothoTalKer and the like.

also dealing with some contracts and sending out invoices.

and plotting the evil overthrow of our russian friends. Quesito writes a mean dossier!

fin.

iliekcomputers: you here?

!m mayhem

You're doing good work, mayhem!

ok, LordSputnik, go.

This week I've mainly been tidying up and modernizing code in BookBrainz

Not particularly productive, but better to set good standards now than later on

(Leftmost?)

fin. ;)

Modernizing? Isn't it like 1 year old? :D

reosarevok: JavaScript

Who still needs to go?

bitmap?

reosarevok: It hasn't changed language for more than a year, it needs to change in some other way.

in JS years it is effectively dead. :)

been working on the sentry pr more

tried to remove some of the code we had to reimplement and integrate it better with Catalyst, which is still a pain

(Only Gentlecat left on my list. Anyone else up for review(ing), now's the chance to step forward!)

got it to include to contents of @_ for each stack frame in the reports

fully tested it in the release editor and got it to properly report errors there for stuff we care about, with correct stack trace context (i.e. from where the error occured, not the eval/catch block)

spent a bunch of time reviewing/testing prs too, since we've gotten quite a few from yvanz / Zastai lately

!m yvanz / Zastai

You're doing good work, yvanz / Zastai!

fin, Gentlecat

I spent some more time figuring out how trigger generation code works in sir

wrote some documentation, done a bit of refactoring

also started planning how to implement better trigger functions/messages

fin

Thanks everyone!

With no one else having spoken up, let's move on with the program.

Freso: resuming meeting notes

🙋

I'm going to resume the weekly meeting notes soon. I've asked for feedback on how to approach it on the forum, to give y'all a chance to decide the path forward: https://community.metabrainz.org/t/resuming-the...

Please go vote/comment there. :)

fin.

samj1912: Picard 2.0.

Hi everyone

so the dev. cycle for picard 1.4 is almost at its end with 1.4.1 PRs almost merged

Freso: I totally dropped that one on the floor, sorry—but I still really want to do it!

for Picard 2.0 I had proposed a few tickets which can be found https://wiki.musicbrainz.org/Development/Summer... here

and https://tickets.metabrainz.org/issues/?jql=proj...

I basically wanted to decide a rough roadmap for how we should be progressing with 2.0

and set an order/priority on the above tasks

along with the direction we want picard 2.0 to go in

zas bitmap Freso input?

s/input/inputs

I think Qt5 or Py3 should happen first. And then the other one.

any update on antlar patch for cover art + album ?

if not, we can release 1.4.1 this week, without it

zas antlarr was busy last I heard from him

He was gonna join the meeting

UI/UX overhaul is likely going to be pretty invasive, so that might be nice to have as the next target. But it's also pretty invasive, so might not be possible to actually do before a lot of other improvements.

I'm skeptical there needs to be an "api v2"

antlarr is online at last.

bitmap: for plugins ?

yes, but clearly using in-app deployement wasn't really on the radar when api v1 was designed

for the plugins endpoint

not sure though if we need 1.1 or 2.0 though ;)

no definitive thoughts about it yet

I mean I'm not sure why picard/the website can't just filter things based on the plugin api version

(About priorities/roadmap: PICARD-975 and PICARD-976 can be done independently of UI/UX overhaul at least, but PICARD-9 might have some parts of it depending on the overhaul. But maybe that's less important whether it happens before or after overhaul.)

PICARD-975: Reimplement the threading code in picard https://tickets.metabrainz.org/browse/PICARD-975

PICARD-976: Reimplement the picard WS code to accommodate future versions of MBWS https://tickets.metabrainz.org/browse/PICARD-976

PICARD-9: Options profiles / quick presets https://tickets.metabrainz.org/browse/PICARD-9

bitmap: the reason for 2.0 was also a more stricter guideline for plugins

are we done? what is going on?

(I'd say Qt5 (since it's basically already done?) → Py3 (also already in progress) → [ 975/976 , UI/UX ] → ? 2.0 release.)

yup

and also newer plugin points

Maybe we can discuss plugin API versions at next meeting? Seems like it's big enough a topic for a separate agenda item. :)

Freso: and I also discussed the possibility of including picard user stats while querying

this is why i don't want to delay 1.4.1 even more, we release it and focus on 2.0. If some important issues is found in 1.4.1 will just do a maintainance release

I read samj1912's notes more like trying to make some kind of roadmap for 2.0.

Okay. So release 1.4.1 and then try and make 2.0 roadmap?

samj1912: maybe the ticket is not explained very well then, I'll comment there

ruaok: We're discussing Picard 2.0.

bitmap: okay :)

The most important will be to define tasks for GSoC related to Picard 2.0

I get that, but conversation just stalled. it would be nice to move things along and respect everyone's time.

ruaok: +1

samj1912 zas bitmap: "So release 1.4.1 and then try and make 2.0 roadmap?"

k

cool with me :)

we can discuss more after the meeting :)

Freso: you can bump the meeting agenda, done from my side :)

Alright.

So. No one has talked anything about schema change tickets or anything so far this year.

because we normally start on march 1.

bitmap: do you feel like we need one?

Experience shows that last minute schema change hacking often gives pretty chaotic results.

I'd like there to be one at least, but I won't personally be working on anything big because I still have to finish the UI from last year

any thoughts on what should be tackled?

but if you're not available to work on it, not sure if we can have a new hire in place to start on that soon.

(and making sure we have the *second* schema change in case there's GSoC stuff that needs one)

not at the moment, I have to look through the schema change component

I'm happy to delay to november.

bitmap: wanna do that and then we'll have a look next week?

sure

Yeah. What I'm trying to say is that March 1 is likely too late to start *thinking* about what to put in a Spring schema change. If people aren't already at least thinking about what to put in a schema change, it's likely going to be a rushed affair yet again.

kewl, thanks.