July 2022 - Inkscape Board of Directors

Fwd: Legal: Agreement to use Inkscape as a prop on a TV show (NZ)
by Martin Owens 23 May '23

23 May '23

(sent to wrong address in original CC)

3 2

FSA Final Call for comments
by Ted Gould 26 Jul '22

26 Jul '22

Hello PLC, Karen sent out an updated FSA, which includes the changes we voted on, but also updates that come from the newer version of their template. I've read through them and don't see any significant changes other than just making it easier to read. We don't need to vote on the change because, well, everyone has to sign it anyway. But, it would be nice to not end up in a state where someone won't sign it because they don't like change. So this email is to ask if anyone has any blocking changes on the FSA as sent by Karen, and attached below. My schedule is that, if no one has blocking issues, I'll ask the SFC to send out the FSA for signatures on Monday August 1st, 2022. Thanks, Ted

3 3

Inkscape 1.2.1
by Marc Jeanmougin 14 Jul '22

14 Jul '22

Inkscape 1.2.1 ============== Inkscape 1.2.1 is now released. You can download it at: https://inkscape.org/release/inkscape-1.2.1/ then, if you want to support Inkscape, donate to the project at: https://inkscape.org/support-us/ ---------------- Inkscape 1.2.1 is mainly a stability and bugfix release, fixing a nasty data loss crash with the export dialog, various other crashes, and improving page export and some translations. Thanks to everyone involved in that release! -- The Inkscape team

1 0

VOTE: hardware 2FA for project sensitive access
by Marc Jeanmougin 01 Jul '22

01 Jul '22

Dear leadership committee, Your attention is required to vote on the following matters: Background: Some contributors have, or need to have, access to social media accounts to post on the behalf of the project, or to infrastructure accounts, most importantly gitlab. For computer security, we would like to protect those accesses with a safe 2FA method, and the safest method to avoid impersonation and phishing attacks is a 2FA hardware token with FIDO2 or U2F. Then we would be able to set a policy to enforce 2fa when contributors need access to passwords that would be shared on nextcloud, or to contributors with "owner" access to gitlab projects. The most common such token is the Yubikey (45€/$ a piece+10 tax+5shipping) but there are equivalents with open hardware component and open source software (e.g. solokeys at 35€/$ incl. tax +5€ shipping, or nitrokey ). As for the amount of people, the vectors team has around 10-15 people with some level of access to passwords of the project, 4 people do not have 2FA and have "owner" access to the whole gitlab project, + 2 "maintainer" access to inkscape/inkscape (and more in other sub-projects). We also have the possibility to offer it to all regular contributors for whom it would be useful. It is yet to be seen whether we could have a discount by asking, or if there is a way to pay for the whole order and get a single reimbursement instead of reimbursing individual contributors Ballot: a. Reimburse up to 2000 USD for password and project protection, and also offering it to contributors who have been in the project for more than a year and ask for it (implies support for option b) b. Reimburse up to 1000 USD to protect the project's passwords on nextcloud and gitlab project access (only contributors who have access to nextcloud, and gitlab maintainer or owner access) c. Do not do it d. Other (please specify) Thanks! -- Marc

6 9