Inkscape Board Meeting Transcript for Friday, 2023-05-05

ted=== START MEETING ===
I've been a bit out of it, but there seems to be tons going on, super excited about all of it.
Agenda
    SFC Items (ted)
Student programs (Outreachy, GSoC, etc) ( @Tav )
Developer meeting update ( Mc )
Vectors update ( )
Infrastructure update ( @doctormo )
16:57
McHi!17:01
TavHi!17:01
tedSecurity Key Program ( Mc )
AI Import Project ( @joneuhauser )
17:01
scislac[m]Hi!17:01
tedBugfix Program ( @joneuhauser )17:01
ponoMorning :)17:01
tedGTK4 Bootstrap ( @joneuhauser )17:01
doctormoHello17:01
tedElection ( pono )
Current Votes Status
Next Meeting: June 2, 2023
Okay, I'll kick it off.
Got the financial snippet from SFC: https://gitlab.com/-/snippets/2537929
Not
much change there, just some expenses from the AI project got paid out.
Here is the allocations, they were just updated with that change. Nothing exciting: https://office.inkscape.org/nextcloud/index.php/s/P6YArrZGzFXJ4FR
I
think looking at the backlog there'll be some more expenses hitting from the various contracting things next month.
But, pretty much "as expected"
17:01
doctormoNo new paypal donations?17:03
tedOther than that I've had a crazy month so I haven't had much time to follow up on things. But I think the time window on the travel stipends for the hackfest has closed, so I can start closing those tickets out and catching up on that.
No, no paypal import :-(
Last date there is still 1/31
17:03
doctormoOK.17:03
Mcted: you can update the projected for gsoc to 150017:03
tedYup, can do. But that's not until the next item on the agenda!
😉
Student programs (Outreachy, GSoC, etc) ( @Tav )
17:04
TavThree places for GSoC.17:04
ponoSide note, I'm looking back at other payment processors, and I think we might be able to try something out later this summer or early fall!17:04
Mc:)17:05
tedGreat, to see those projects moving forward.
Do we have someone for the in-person summit? Or multiple people?
17:05
TavGtk4 migration, Improving CSS, Customizable Canvas Controls.17:06
TavOne person per project this year, I think.17:06
Mcyes17:06
TavNo discussion of who wants to go.17:06
Mcnot yet, we'll see17:07
tedDo we have someone that wants to go? Or do we need a committee to decide between folks? Or whatever.
Okay.
Seems like that's relatively cut-and-dry.
Next up: Developer meeting update ( Mc )
17:07
McI missed the last one :D17:08
TavOnly $1200 for travel expenses, probably won't cover travel from Europe.17:08
doctormoDeveloper meeting notes are available :-)17:08
Mc@Tav oh it should be well enough ?17:09
ted@Tav, personally I think that we should subsidize that if needed, but we should probably see who has time first.
I'd be more worried about someone's time.
17:09
McOct 22-25, I'll know later if I can make it17:10
ponoI don't see when the summit is this year, is there any info on the GSoC page about that?17:10
tedAre we still on track for a release here in the next little while?17:10
ponothanks Mc17:10
Mc(Mountain view)
ted: We should be
we should start discussing the beta schedule (as we did not see any catastrophic event for alpha)
17:10
doctormoYes, we can do that in today's dev meeting17:13
tedGreat, that would probably be good to do and hand off to Vectors.
I think their meeting is tomorrow?
17:13
Mcpono: I completely messed up the dates, sorry
Friday, October 13 (starting at 5pm) - Sunday, October 15 (ending by 5pm)
17:13
ponogotcha, thanks17:14
Mcpono: ( https://paste.fulltxt.net/RVe:u1 )
"Not every organization will send a delegate so we will likely have ~40-45 open spaces for orgs that wish to send a second delegate."
17:14
tedI pinged @Moini late, and I don't think she's around. Is there someone else who's been tracking Vectors stuff?
Vectors update ( )
17:15
doctormoI've not heard anything from the vectors team, though they have been busy posting things.17:16
tedOkay, I'll try to figure out an update for next month there with a bit more notice.
20 minutes isn't exactly fair.
Next up: Infrastructure update ( @doctormo )
Any infrastructure stuff?
17:17
doctormoA small update to the website for elections, no much else going on.17:19
doctormoSome small fixes.17:19
tedCool, next up: Security Key Program ( Mc )17:20
Mcno news, sorry17:20
tedOkay, next up (I'm just gonna group these): AI Import Project ( @joneuhauser ), Bugfix Program ( @joneuhauser ), GTK4 Bootstrap ( @joneuhauser )17:20
Mc^^17:21
tedWell, hoping @joneuhauser won't group them, but let him go between them.17:21
joneuhauserAI Import Project: Progress is adequate, recently some refactoring was done. \nBugfix project: see https://inkscape.org/*membership/blog/april-bug-accelerator-2023/, Rafael has decided to step out of the program (this is exactly the reason why I insisted on more than one contractor). \nGTK4 bootstrap: 2 applications for the external contractor so far, very interesting candidates. Internal contractor: only one application, hiring team has concluded and selected Tav as internal contractor. This is now with the SFC. The additional GSOC student should also help there.17:23
tedDo we need to look for someone else for the bugfix program? Or just no time?17:24
joneuhauserWe'd need a new vote for this. Let's discuss it at the dev meeting later tonight.17:25
tedOkay, sounds good. We're getting kinda close to a release to be able to do anything though. Not sure, might depend on the beta schedule.17:25
ponoSounds good. Is there any time pressure with an upcoming release?
(re: finding a new person for the bugfix program)
17:25
tedGlad to hear we got a couple applicants for the gtkmm place of the migration. I was a bit worried we wouldn't. Excited about that.17:26
joneuhauserYes, someone from upstream (GTK and GTKMM) is interested.17:27
tedFor folks on those hiring committees please request your stipends (or ask how to if you don't know).
(I like closing things out) :-)
17:27
Mcpono: the time pressure is the one we put ourselves, but we have semi-regular releases (~4month) so it's not critical to miss one17:28
tedYeah, but we also wanted to release before gtk4 and like to before gsoc... so we kinda need to at least fork for the release soon.17:29
doctormoIt's important not to miss the 1.3 release. We have queued up way too much to skip it.17:29
RdH(pono: have you been getting my emails?)17:30
doctormoOr you mean... not miss the release but miss the schedule.17:30
ponoGotcha, thanks for the info.17:30
tedAnyway, though. That's a decision for the dev meeting, not a PLC thing. So make sure to go to the dev meeting if you want to discuss release schedules :-)17:30
Mc@doctormo the schedule (or the fact to have a bugfix contractor for a specific release)17:30
pono@RdH I see I missed some, I'll respond to those today. Sorry about the delay.17:31
tedOkay, next up a meaty one: Election ( pono )17:31
Mcyay, election \\o/17:31
tedI got an email about nominations!17:31
TavVOTE!17:31
Mcdo we have a list of nominated people ?17:32
ponoThanks to @doctormo for helping me get the election setup.17:32
ted@Tav, not yet 😉, NOMINATE!17:32
pono@joneuhauser and Michele have been nominated so far.17:32
doctormoEach person can nominate one person, or themselves. This is just a limitation of the software though, so we can revise that for next time.17:32
ponoIt's moving along!17:33
tedCool, as long as we have at least two nominations I'm not too worried :-)
But we of course would love more. And no special skills required.
Not sure who's reading the backlog, but if you care enough to read the backlog, you should at least consider it.
I think any member of the PLC would be happy to talk to you about it if you have questions.
Okay, going fast today (and I was worried about it), Current Votes Status:
17:33
doctormoAlso consider accepting the invitation, and ask questions if you're unsure.17:36
tedWe have one outstanding vote on Wilber Days, please look at that.
Though, I think we should ask for it to be move to Wilber & Inkscape Days 😉
Next Meeting: June 2nd, 2023
Thanks everyone!
=== END MEETING ===
17:36

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!