#metabrainz

/

      • zas
        discussing with ruok tonight about it, we'll go for snapshots (processing only each 3 days)
      • LordSputnik
        ruaok: yo momma's fat
      • Freso
        A fat log is a sturdy log.
      • gcilou
        LordSputnik +1
      • zas
        so we can get a general view of web service
      • ruaok
        LordSputnik: at least she ain't ugly, like Leftmost's momma
      • alastairp
        here
      • zas
        apart that, i did usual maintainance, PR reviews, and a bunch of MB edits
      • also i made it to BCN ;)
      • Freso
        πŸ™Œ
      • reosarevok
        Freso: yo momma's got a sturdy log?
      • zas
        Hope to meet you all soon ;)
      • Freso
        Not that I know of.
      • Quesito
        benvinguda zas!
      • ruaok
        lol
      • zas
        Next ? alastairp ?
      • alastairp
        hi
      • last week I was in meetings *all* week, so didn't do much
      • zas
        ahah
      • alastairp
        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
      • Freso
        I did?
      • reosarevok coughs. Not (only?) Freso :p
      • !m Freso
      • BrainzBot
        You're doing good work, Freso!
      • alastairp
        oh, maybe it was reosarevok
      • other than that, I did a bit of code review for ruaok and some AB review
      • Freso doesn't even remember πŸ™ˆ
      • a bit of planning for SoC
      • reosarevok
        To which we're accepted! yay
      • alastairp
        fin. ruaok ?
      • Freso
        \o/
      • reosarevok
        etc
      • ruaok
        last week I was battling a cold so things moved slower than usual.
      • Freso
        (Other people up: Gentlecat bitmap LordSputnik - anyone feeling left out, raise your hand. :))
      • reosarevok
        You fought the cold and the cold won?
      • ruaok
        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?
      • CallerNo6
        !m mayhem
      • BrainzBot
        You're doing good work, mayhem!
      • Quesito is very loyal, don't cross her ;)
      • ruaok doesn't plan to.
      • ruaok
        ok, LordSputnik, go.
      • reosarevok would like to see how a mean dossier about us would look like tbh
      • LordSputnik
        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
      • Freso
        (Leftmost?)
      • LordSputnik
        fin. ;)
      • reosarevok
        Modernizing? Isn't it like 1 year old? :D
      • LordSputnik
        reosarevok: JavaScript
      • Who still needs to go?
      • bitmap?
      • Freso
        reosarevok: It hasn't changed language for more than a year, it needs to change in some other way.
      • ruaok
        in JS years it is effectively dead. :)
      • bitmap
        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
      • Freso
        (Only Gentlecat left on my list. Anyone else up for review(ing), now's the chance to step forward!)
      • bitmap
        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
      • Freso
        !m yvanz / Zastai
      • BrainzBot
        You're doing good work, yvanz / Zastai!
      • bitmap
        fin, Gentlecat
      • 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
      • Freso
        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.
      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC Geting Started: https://goo.gl/JTNkn0 | MeB meeting agenda: Picard 2.0 (samj1912), schema change (Freso)
      • samj1912
        Hi everyone
      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC Getting Started: https://goo.gl/JTNkn0 | MeB meeting agenda: Picard 2.0 (samj1912), schema change (Freso)
      • so the dev. cycle for picard 1.4 is almost at its end with 1.4.1 PRs almost merged
      • sampsyo
        Freso: I totally dropped that one on the floor, sorryβ€”but I still really want to do it!
      • samj1912
        for Picard 2.0 I had proposed a few tickets which can be found https://wiki.musicbrainz.org/Development/Summer... here
      • 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
      • Freso
        I think Qt5 or Py3 should happen first. And then the other one.
      • zas
        any update on antlar patch for cover art + album ?
      • if not, we can release 1.4.1 this week, without it
      • samj1912
        zas antlarr was busy last I heard from him
      • He was gonna join the meeting
      • Freso
        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.
      • bitmap
        I'm skeptical there needs to be an "api v2"
      • Freso
        antlarr is online at last.
      • zas
        bitmap: for plugins ?
      • yes, but clearly using in-app deployement wasn't really on the radar when api v1 was designed
      • bitmap
        for the plugins endpoint
      • zas
        not sure though if we need 1.1 or 2.0 though ;)
      • no definitive thoughts about it yet
      • bitmap
        I mean I'm not sure why picard/the website can't just filter things based on the plugin api version
      • Freso
        (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.)
      • BrainzBot
        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
      • samj1912
        bitmap: the reason for 2.0 was also a more stricter guideline for plugins
      • ruaok
        are we done? what is going on?
      • Freso
        (I'd say Qt5 (since it's basically already done?) β†’ Py3 (also already in progress) β†’ [ 975/976 , UI/UX ] β†’ ? 2.0 release.)
      • zas
        yup
      • samj1912
        and also newer plugin points
      • Freso
        Maybe we can discuss plugin API versions at next meeting? Seems like it's big enough a topic for a separate agenda item. :)
      • samj1912
        Freso: and I also discussed the possibility of including picard user stats while querying
      • zas
        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
      • Freso
        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?
      • bitmap
        samj1912: maybe the ticket is not explained very well then, I'll comment there
      • Freso
        ruaok: We're discussing Picard 2.0.
      • samj1912
        bitmap: okay :)
      • zas
        The most important will be to define tasks for GSoC related to Picard 2.0
      • ruaok
        I get that, but conversation just stalled. it would be nice to move things along and respect everyone's time.
      • zas
        ruaok: +1
      • Freso
        samj1912 zas bitmap: "So release 1.4.1 and then try and make 2.0 roadmap?"
      • zas
        k
      • samj1912
        cool with me :)
      • we can discuss more after the meeting :)
      • Freso: you can bump the meeting agenda, done from my side :)
      • Freso
        Alright.
      • Freso: schema change
      • So. No one has talked anything about schema change tickets or anything so far this year.
      • ruaok
        because we normally start on march 1.
      • bitmap: do you feel like we need one?
      • Freso
        Experience shows that last minute schema change hacking often gives pretty chaotic results.
      • bitmap
        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
      • ruaok
        any thoughts on what should be tackled?
      • chirlu would like to move the schema change date to November in general.
      • reosarevok would be happy with using the time to finish last year's stuff, releasing a schema change only if there's stuff on the pipeline from chirlu or someone
      • 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.
      • reosarevok
        (and making sure we have the *second* schema change in case there's GSoC stuff that needs one)
      • bitmap
        not at the moment, I have to look through the schema change component
      • ruaok
        I'm happy to delay to november.
      • bitmap: wanna do that and then we'll have a look next week?
      • bitmap
        sure
      • Freso
        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.
      • ruaok
        kewl, thanks.