| ted | Okay, let me start the official log === START MEETING === Agenda SFC Items (ted) Student programs (Outreachy, GSoC, etc) ( Mc ? ) Developer meeting update ( Mc ) | 17:04 |
|---|---|---|
| RdH | Thanks :) | 17:05 |
| ted | Vectors update -- https://gitlab.com/inkscape/vectors/general/-/issues/268#note_1411544358 Infrastructure update ( @doctormo ) Security Key Program ( Mc ) Contract Projects ( @joneuhauser ) Election Wrap up (pono) Current Votes Status Next Meeting: July 7th, 2023 Okay, SFC stuff. We got an update on financials from the SFC: https://gitlab.com/-/snippets/2551264 No new Paypal import, so the income numbers haven't changed. Though a little bird told me there's been good progress on switching from Paypal so that problem is hopefully on it's way out. On the expenses side we've mostly gotten billed from contractors. And one domain name renewal. | 17:05 |
| doctormo | No paypal script run yet? | 17:07 |
| ted | Nope :-( I imagine that'll be after FOSSY at this point. | 17:07 |
| joneuhauser | Is there consensus to leave PayPal? Don't know what to think of that. | 17:07 |
| pono | It's a very time intensive process, which is why we've been trying to add a new mode of donation. | 17:07 |
| joneuhauser | In addition or instead of? | 17:08 |
| ted | @joneuhauser, yeah there's a collection of issues, including the fact that people from most of Asia can't donate through Paypal. | 17:08 |
| Mc | ted: we can try to add a "bugfix program wrap-up" to the agenda | 17:08 |
| pono | After the conference and wrap up, I'm hoping later this summer to add a new donation mechanism that'll work with credit cards and international donations. | 17:08 |
| doctormo | That sounds good. It always sounds like the paypal script is a more manual process than expected. | 17:08 |
| ted | Mc, sure, I pushed all of the contract stuff into one as I had like four things for @joneuhauser all together. I figured that'd include bug fix along with the others. Last SFC thing: We've issued contracts for the Internal GTK4 migration developer. There's a contract for the external developer, but it needed some dates changed, so it should get finished next week. | 17:09 |
| joneuhauser | > add a new donation mechanism\nvs \n>switching from Paypal\n\nwhich one is it? | 17:10 |
| ted | Next up: Student programs (Outreachy, GSoC, etc) ( Mc ? ) @Tav couldn't make it, Mc can you take that one? | 17:10 |
| doctormo | Talking of money: This is a note that the Gimp project are forming the Wilber Foundation to fund development. | 17:10 |
| Mc | well, GSoC started, we have three contributors this year | 17:11 |
| pono | @joneuhauser We're looking at Stripe. But I'll keep you all informed as we dive more into it. | 17:11 |
| Mc | no problem yet, greeting meeting was organized a bit late | 17:11 |
| ted | Ah, interesting. Will be interesting to see how they structure their foundation. | 17:11 |
| Mc | and status blogposts will be posted on the inkscape website | 17:11 |
| ted | Ah, nice. That'll be more uniform. | 17:11 |
| RdH | @doctormo They want to leave GNOME foundation? | 17:11 |
| joneuhauser | >and status blogposts will be posted on the inkscape website\ndidn't happen yet because AFAICS they don't have permissions on the website yet to do that | 17:12 |
| Mc | afaiu their fundation will be hosted by Fondation de France (a french foundation host) | 17:12 |
| doctormo | @RdH Apparently. | 17:12 |
| ted | @RdH, I'm guessing they may want to separate out project funds from sponsoring development as well? | 17:12 |
| doctormo | More and more Free software projects are leaving the gardening only model and moving to more hands on funding. Although still non-profits. | 17:13 |
| pono | Good to see a mix of governance methods :) | 17:14 |
| Mc | whether in netherlands (godot, blender, krita) or france (gimp, VLC), the main model is a non-profit owning a "normal" company | 17:14 |
| RdH | I guess we can't stay a charity forever to be sustainable | 17:15 |
| Mc | (not 100% sure what it will end up with for gimp and godot yet) | 17:15 |
| ted | Huh, that is different. Not sure if that is effectively a white-wash of a company or not. | 17:15 |
| joneuhauser | @pono did something come out of the legal questions re. a european Inkscape entity we discussed at the hackfest? | 17:15 |
| pono | We won't be able to make a European entity in the near future. But we did resolve some of the questions around receiving grant funding via European funders. | 17:16 |
| ted | It is what Howard Hughes did in the early 1900's -- he did it mostly as a tax dodge. | 17:16 |
| Mc | ted: here it's to force community governance of decisions and funds | 17:16 |
| pono | We'll just need to write a set of rules similar to the trademark policy, about representation of the project and how the project interacts with the grantees. It'd be a great topic for another meeting (which I've got a link to a poll for scheduling). | 17:17 |
| Mc | (as the non-profit/foundation is community-led) | 17:17 |
| joneuhauser | @pono we should discuss this further, in a higher-bandwidth setting | 17:17 |
| pono | +1 | 17:17 |
| Mc | +1 | 17:17 |
| ted | pono, are you thinking before or after FOSSY? :-) | 17:17 |
| pono | Next week or the week after is what I set the poll for: https://framadate.org/5adtuMKKHPyJ2ERs I'll also send it to the list with some agenda topics (that @joneuhauser helped draft) | 17:18 |
| Mc | in other project-related news, we published a beta ! | 17:18 |
| ted | Next up: Developer meeting update ( Mc ) :-) Awesome, how is the feedback on the beta? | 17:19 |
| Mc | people are excited at the upcoming shape builder afaict (with lots of fixes by the dev team (martin in particular), of preparatory work from Maren to ease upcoming string freeze, and of vectors communication around the beta) our testing team (Klr17) deemed the beta quite stable in general | 17:20 |
| ted | Sounds great, is there a timeline for the final release? | 17:21 |
| Mc | early july iirc (7th ? not sure) string freeze is very soon, so that translators can have 4 weeks to update | 17:22 |
| doctormo | July 4th! Completely not related to US indipendence day. ;-) | 17:22 |
| ted | Amexit | 17:22 |
| doctormo | lol | 17:22 |
| ted | Cool, sounds great. Next up: Security Key Program ( Mc ) | 17:23 |
| Mc | no tiiiime sorry :( | 17:23 |
| ted | I haven't seen anything there, I understand if you feel like you don't have time. Should we just shut that down for now? | 17:23 |
| Mc | I'll send what I need at some point I'm a bit ashamed I havent already | 17:24 |
| ted | Okay. Sounds good. I think it's a good idea, but everyone is busy. (I'm behind on my Inkscape TODO list too) Next up: Contract Projects ( @joneuhauser ) (which should include bug fix project) | 17:24 |
| joneuhauser | Sure! AI Project: progress has been quite slow this month, but in general some refactoring going on. The parser itself is quite nice, but SVG conversion is lagging behind. Not yet sure whether we are going to extend this - there is a checklist of features that need to be completed on which I'll base my opinion. Contract hours are spent to ~90%. | 17:27 |
| joneuhauser | GTK project: Pono already said the current state. | 17:27 |
| doctormo | Final invoice has been submitted, I've used up all the hours. Hope people are happy with the results. | 17:27 |
| doctormo | (for the bug accel program) | 17:27 |
| joneuhauser | Bugfix project: I'm incredibly happy with the outcome. I'm still waiting on feedback from @Pono whether we can extend it. | 17:27 |
| Mc | It was a great success | 17:28 |
| pono | Great to hear it worked out! | 17:28 |
| Mc | @joneuhauser ah, because there is remaining budget from the fact we had only one contractor in the end ? | 17:28 |
| joneuhauser | Yes, as we've talked about in the Dev meeting. | 17:28 |
| pono | I'll need to review the contracts (and dev notes meeting). But if there are still funds that were allocated, we can look at extending the contract. | 17:29 |
| joneuhauser | I've emailed pono about this ~3 weeks ago, no response yet (or I didn't see it?) | 17:29 |
| Mc | pono: well, doctormo can talk about it, but he posted https://fosstodon.org/@doctormo/110470858948065357 which summarizes things well | 17:29 |
| doctormo | pono: My contract mentions written permission to go over the allotted time. But I'll leave it to you guys. | 17:29 |
| pono | Ah great, I had only seen the blog post. | 17:29 |
| joneuhauser | It certainly would require another vote because that's outside of the original proposal. The dev meeting was in favor of doing so. | 17:30 |
| joneuhauser | If it's alright with you, Pono, I'll just send out a vote for it. | 17:31 |
| pono | @joneuhauser Let me review the contract first, but I'll try and get you an answer later today. | 17:31 |
| joneuhauser | Also I'd like to do a debriefing together with the contractors and the SFC. What went well, what can we improve for next year. | 17:31 |
| joneuhauser | Awesome, thanks. | 17:32 |
| pono | Sure that's a great idea. | 17:32 |
| ted | Next up: Election (pono) I left that there for any wrap up, but I'm not sure if there's anything. | 17:32 |
| pono | We got some feedback that more information about the process and how the software works could be improved. | 17:33 |
| Mc | did we use the software ? | 17:33 |
| pono | So something to work on for the next one, but overall I think it went well. Mc: Yeah, @doctormo helped me get it set up. | 17:33 |
| RdH | I thought the software was to organize the voting. We didn't vote. | 17:34 |
| doctormo | I think there's some policy which is unclear about how equal number of candidates and slots should be handled. | 17:34 |
| RdH | (Of course, applications were handled.) | 17:34 |
| pono | Right, since there were just 2 candidates that accepted the slots, the vote automatically promoted them. | 17:35 |
| doctormo | But we could do a debrief for that too if there's enough of an agenda to process. | 17:35 |
| ted | @doctormo, can you write a short ammendment to our election procedure there? I mean, I don't think it should be too controversial? We just need to be clear. | 17:35 |
| doctormo | ted: A proposal? Not sure, I'm not unhappy with the direct promotion myself, but I can see how people might need some extra time, or maybe some warning. | 17:35 |
| doctormo | pono: As proctor, what would you expect to happen? | 17:36 |
| pono | Editing this document https://alpha.inkscape.org/board/referendums/resolutions/election_procedure.html to clarify the process is probably the best idea (or similar page) | 17:36 |
| ted | I don't think direct promotion is bad, but we should at least say that's what we do. And perhaps the proctor should get a "are you sure?" popup. | 17:37 |
| doctormo | pono: I think that's the old one, I've been working from https://inkscape.org/gallery/item/39937/inkscape-election-procedure-v4.pdf | 17:37 |
| joneuhauser | Why is the 2023 vote on the updated election procedure not on alpha? | 17:38 |
| ted | @joneuhauser, on my backlog :-( | 17:38 |
| doctormo | (trying to keep all policy documents linked from https://inkscape.org/*leadership-committee/ pono ) | 17:38 |
| pono | ah great. is that a file any of the PLC can edit? | 17:39 |
| ted | It's a Git repo So yeah, but I've been maintaining it. | 17:39 |
| joneuhauser | Alright @ted, that brings me to a suggestion: we should move creating and maintaining board documents into a git repo. Merge requests are voted on there, and a pipeline publishes important documents on the website. We can collaborate on drafting new documents in personal forks. | 17:40 |
| joneuhauser | Maybe we can come up with something. | 17:40 |
| ted | That would be interesting, we already have the repo of most of the votes. And a template. | 17:41 |
| joneuhauser | I'd be interested in working on that. Making the PLC business a bit more transparent. | 17:41 |
| ted | Well, we do have the problem that we need the ability to do secret votes if required. But otherwise, yes. | 17:42 |
| doctormo | I'd like that too. The website's good at public facing our final documents. but isn't as good as editable and multi-user edits. | 17:42 |
| joneuhauser | It is possible to do confidential merge requests on Gitlab. | 17:42 |
| ted | K, I think we'll need to have a discussion on all the permissions, but yeah. I think we're conservative right now, but I think that was primarily for simplicity more than a goal. | 17:43 |
| doctormo | @joneuhauser Are you thinking of hosting votes on git too, or would the vote still happen on the mailing list? | 17:44 |
| joneuhauser | Either way would work. Voting on gitlab would have the advantage that we could require 2FA for board members. | 17:44 |
| doctormo | We've have to update the FSA for that, I think it's very specific about the mailing list. | 17:45 |
| joneuhauser | Yes, we should do that anyway. It's an important long-term goal for me. | 17:45 |
| doctormo | No wait I'm wrong. | 17:45 |
| doctormo | It just says "might conduct business anywhere" | 17:45 |
| Mc | I don't think it specifies anything about the vote | 17:45 |
| joneuhauser | > I think we're conservative right now, but I think that was primarily for simplicity more than a goal.\nRelated: do Rene and I already have permissions on all board-related mailing lists? | 17:45 |
| ted | @RdH, what is your gitlab ID? I can't seem to find it. | 17:46 |
| Mc | (we could hold them on IRC) | 17:46 |
| doctormo | pono: can you add rene and jonathan to the SFC inkscape mailing list? | 17:46 |
| ted | pono, are they on the SFC ones? I don't think we control those. | 17:46 |
| Mc | ted: dehesselle | 17:46 |
| RdH | My GitLab ID 2907496 | 17:46 |
| doctormo | lol | 17:46 |
| RdH | ah, which one? | 17:47 |
| ted | K, I think I put both of you in the Gitlab group. | 17:47 |
| joneuhauser | Thanks. | 17:47 |
| pono | @doctormo They should already be added, I did that as soon as they were elected. And I think they've received mail to inkscape@sfconservancy.org can you confirm @joneuhauser @RdH ? (i just sent the scheduling email) | 17:47 |
| doctormo | Awesome! and thank you! | 17:48 |
| ted | Thanks Mc and @RdH ! Just because I have it up, the only folks without 2FA are scislac and @Tav :-) | 17:48 |
| joneuhauser | @pono if you used my regular email, then no | 17:48 |
| scislac[m] | Ted: How do I go about setting it up? | 17:48 |
| joneuhauser | https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html | 17:49 |
| doctormo | I use the FreeOTP app on my phone. | 17:49 |
| joneuhauser | Me too. | 17:49 |
| doctormo | Got all the accounts with their correct icons like a total nerd. | 17:49 |
| ted | I use Bitwarden and you can attach it to your password. | 17:49 |
| Mc | https://gitlab.com/-/profile/two_factor_auth | 17:49 |
| RdH | I cannot find any mail pono | 17:50 |
| ted | I love that, and it puts it on the clipboard so you just have to Ctrl+V it in. | 17:50 |
| Mc | I use a yubikey ^^ | 17:50 |
| RdH | Do you have a timestamp so I can double-check? | 17:50 |
| ted | Okay, fine Mc wins. I don't think we have anything left in the meeting. | 17:50 |
| pono | @joneuhauser @RdH subject "PLC Meeting for future planning", I'm checking with our sysadmin that the change was made | 17:51 |
| ted | So I'll just remind folks: Next Meeting: July 7th, 2023 | 17:51 |
| doctormo | @RdH \tFri, 2 Jun 2023 10:47:49 -0700 | 17:51 |
| ted | And I'll go ahead and: === END MEETING === | 17:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!