- Inkscape Board of Directors

Inkscape Developer Meeting, May 10th 2025
by Martin Owens 10 May '25

10 May '25

Dear Developers, Event: https://inkscape.org/cals/event/64/ Attending: RdH, Martin, Anu, Aarav Oswal, Tav, Adam Belis, Marc Next meeting https://inkscape.org/cals/event/1/ is the late meeting on a Sunday. Bare this in mind! Release scheduling; René and Martin talk about the building of the 1.4.2 macOSX release. The tag is ready so he'll be uilding those after the meeting. Marc says everything looks good when he looked two days ago, so he went ahead and made the installers and tags. There's over 50 commits of translations because of how weblate works there tends to be multiple commits for each user. We formalise that each protected branch has a translation branch with the pot file updated to that protected branch so translations can happen as soon as posible. Tav has been working on context fill and context stroke which fixes a bunch of issues for inheritance. Including some crashes. Martin and Tav had a disagreement about how tests should be done and did not come to an agreement. Some discussion around the PDF output with various issues that has been spotted. Tav has worked on a crash when text flowed into space and you export selected item. Marc has been trying to draft some stuff on the future of LPEs. Martin suggests meeting to talk about the design. Tav suggests using a switch statement. Generated Items is the more generic name. A discussion develops that goes into some of the possibilities and details. René has been working on the move to the new mac statium infrastructure. Master is already working on the new system. 1.4.x is currently stalled as there are some issues remaining. His next tasks is working on that after the release. Up next will be looking into providing remote access to developers who don't have a macOS machine themselves. René needs to work out how to do it network wise and will provide a proposal for everyone when ready. It can be slow for openGL and we should explain this to people who use the system. Martin asked RdH about the process for doing capypdf in macOSX. We expect a 1.5 release in a year so we have time to work it out at the very least we will have a version for the very latest version. We check upstream macOSX version limitations. Marc reports on the GSoC. We have 5 students who have been accepted. On-Canvas spell checking, UI-Free Inkscape, AI file format support, Recolor Art Work, lib2geom improvements. Martin has worked on some PDF fixes as well as the next steps in design for color management. Running a design meeting this week. We talked about the hotel being paid and the trouble with getting the SFC to make sure this important aspect is finalised safely. Thanks everyone for coming.

1 0

Developer Meeting; May 2nd 2025
by Martin Owens 02 May '25

02 May '25

Event: https://inkscape.org/cals/event/1/ Attending: Mikekov, Martin, Tav, Jonathan, Willy, Velfel, Elendil Next Meeting: https://inkscape.org/cals/event/64/ (May 10th) We start by welcoming Velfet; from Serbia. We talk about topics. They've started by looking into the code and getting familar with how things work. We share advice. Mikekov; Is back to working on the object properties dialog. Will be presenting at the Summit and will hopefully get something deliverable. Jonthan; Announces that he will be stepping away from Inkscape after the Nuerumberg Summit. He's also been working Illustrator work and waiting for GSoC. Tav; Has been working on context-fill and context-stroke issues in rendering and PDF export. Martin has also been working on context work for the new PDF output. Willy; Has got his first feature merged this week. Congratulations! A new settings component which allows a folder to be changed and opened. Has added a new async method for checking if files are valid. Elendil; Has been traveling. Martin; capypdf work and getting frustrated with the CI build system. We talked briefly about the OPSOSL situation and that the PLC is working with the SFC about solving it. We worked on merge requests for 20 minutes, reviewing tricky code requests. Big thanks to everyone! We talked about the introduction of an AI policy in the developer team. We want to know if the quality of contributions will impact review time. Martin brought the question of the roadmap team. He's collecting feedback in order to put together a proposal which can encapsulate the guardrails of what a team would do, and what it's limitations would be. It would involve meeting at least quarterly, and not being a closed team that made up all of the ideas itself, but would instead be responsible for sourcing and combining the ideas in our community into a roadmap. He's asked everyone to think about it and get back to him if they have ideas or want to talk further. Thanks everyone for coming to this week's meeting. Best Regards, Martin Owens

1 0

Today's Status Meeting is Cancelled
by Ted Gould 02 May '25

02 May '25

Hello, Today we're not going to have an chat status meeting. As folks paying attention to the chat will know there's been a funding issue with our hosting provider so we're having an emergency meeting with SFC to discuss options in places of the regular status meeting. Sorry for the late notice. Next status meeting will be June 6th, 2025. Ted

1 0

Funding for OSUOSL, Was: [Hosting] Future of OSL in jeopardy
by Martin Owens 30 Apr '25

30 Apr '25

Dear Board, Please read the attached request for help from our hosting provider OSUOSL. I'm proposing that since Inkscape is in the position to help, we should commit to giving them $20k in a one off amount, and commit to something reasonable for a yearly grant. Since they run our website, this mailing list and email provision for our various services. And have been working on our new matrix chat server. Their support has always been courteous, smart and fast and we've depending on them for a long time. I'm presenting an ambitious proposal, but I believe that getting them over this emergency situation would be in our long term best interest. We have given to them in the past. But I believe this is our time to put our resources behind an important bit of infrastructure. This isn't a vote, we'll do that later. Possibly after next Friday's meeting. Related Social Media post: https://floss.social/@downey/114428216313195235 Best Regards, Martin Owens

1 0

Inkscape Developer Meeting 16th April 2025
by Martin Owens 16 Apr '25

16 Apr '25

Dear Developers, Event: https://inkscape.org/cals/event/1/ Attending: Marc, ltlnx, pbs, Jonathan Apologies: Tav Next Meeting: https://inkscape.org/cals/event/64/ (earlier) Inkscape Release 1.4.1 is removed because of crashes and we need release 1.4.2. We want to be more courteous to other teams such as documentation and translations so they have some time to prepare themselves. Marc will send out a message to everyone explaining our situation with the plan. Martin explained what happened in 1.4.1 and why it couldn't be released. The splash screen was loading too early causing macOS to crash and causing an error with command line uses as the CLI wasn't read in by the time the splash screen was being loaded. The developer team is basically ready but will give two weeks for other teams to get themselves into position for the point release. this puts the release at the end of April, start of May. The bug Accelerator program met today and there isn't a lot of bugs fixed yet in April as Martin took a break to work on PDF and Tav working on LPE issues. Blog posts for March are available on the website. Willy has been busy doing the documentation project, Inkscape manual. He's modeling it on the Blender manual and the end goal is to have it in the UI interface, not just in the help menu. Jonathan has been organising the GSoC review meeting. The details for the discussion were disclosed but were not added to these minutes as they are confidential. PBS wanted to ask about how exporting symbols. Inkscape for windows is hitting the limit on the number of symbols and so PBS created a branch to experiment. This shows that almost everything can work, except for Plugins which are the under-used C++ based code since the API would need to be available. We could ask the projects using plugins to design what the inkscape symbols API should. Martin has been working on PDF output dealing with Markers and context paints, wrote some more tests and is happy with the test output so far. PBS has some ideas about how it might be possible to make a static version of capypdf, but this would be highly experimental. We talked briefly about cppgir, but the problem is that it takes so long to load; but it's a good API and with gtkmm being not as maintained this might be a good future option. See you all next week! Best Regards, Martin Owens

1 0

VOTE: Update our trademark terms
by Ted Gould 03 Apr '25

03 Apr '25

Background There have been a few instances brought to the PLC of possible trademark infringements where it was borderline on whether those were violations of the trademark agreement we've posted. One of the biggest issues there was that it wan't clear that the icon was part of the agreement and restrictions on such. These changes attempt to make clear that the icon is also restricted. For reference the full document is available: https://inkscape.org/about/branding/ Action The proposal is to change the points under Section 2.2 from: > In addition, you may use the Marks to refer to products, services, or communities outside of the Inkscape software and Inkscape Project without written permission in the following contexts: > When referring to Inkscape software that is not substantially unmodified, to say that the such software is a "derivative of" or "based on" Inkscape. > When referring to communities of users in the context of their use of the Inkscape software, e.g., virtual communities, community-moderated online forums, consortia of organizational users, etc., provided that the Marks are not used to suggest endorsement of any user community by the Inkscape Project. To the following: > In addition, you may use certain of the Marks to refer to products, services, or communities outside of the Inkscape software and Inkscape Project without written permission in the following contexts: > When referring to Inkscape software that is not substantially unmodified, you may use the term "Inkscape" only (and not any other Mark, such as the Inkscape Logo) to accurately describe the relationship of such software to official Inkscape software, such as to say it is a "derivative of" or "based on" official Inkscape software. > When referring to communities of users in the context of their use of the Inkscape software, e.g., virtual communities, community-moderated online forums, consortia of organizational users, etc., you may use the term "Inkscape," the term "Inkscapers," and the Inkscape Logo, provided that such Marks are not used to suggest endorsement of any user community by the Inkscape Project. Timeline Please post a vote to this list by March 24th, 2025 Votes A. Accept the changes as proposed B. Changes, but also: _________ C. Do not change Thank you for your consideration, Ted

6 5

Inkscape Developer Meeting, March 31st 2025
by Martin Owens 31 Mar '25

31 Mar '25

Dear Developers, Attending: Martin, Marc, Jonathan, Mikekov, Ishann, Itlnx Event: https://inkscape.org/cals/event/1/ Marc: created and uploaded 1.4.1 binaries and has been investigating issues with the various builds and adding in translations. Jonathan: updated extensions for the release and released on pypi. Working on AI import. Some of the designs internally to AI have some really weird design choices. Martin: Bugfix Accelerator work + investigation of Windows slowness. Some discussion with Mike about Pattern editing architecture. Helped with the AI importer work with a PDFBones library for opening pdf files based on pdf Mikekov has been working on the Gtk Window preview editor. A separate project to see glade files and edit them a little bit. Hopes to get back to Inkscape work soon. SVG W3C held a meeting and we didn't know until after they had met about trying to revive interest in supporting SVG. Itlnx has been working on translations, fixing various small issues with the translation strings in the software. Needs to access read the docs account and will be following up with Maren to find out how to do that. Also helped with the release making a graphic for the website. Next meeting is April 8th and is at the earlier time. Thanks everyone for coming and helping with the 1.4.1 release! Best Regards, Martin Owens

1 0

Fwd: [Contact] Potential support from Steam games
by Ted Gould 10 Mar '25

10 Mar '25

Hey folks, This came in to the contact list and seems like it might be a good idea. Anyone have experience with this? Ted ---------- Forwarded Message --------- From: Sweetlads <admin(a)sweetlads.com> Subject: [Contact] Potential support from Steam games Date: Mar 9 2025, at 12:55 pm To: contact <contact(a)inkscape.org> Hi there, I intend to utilise Inkscape as a tool to help the community create assets for my game via Steam Community Workshop. The amazing thing about the Steam Community Workshop is it allows developers to share revenue earnt from items submitted into the game with both the creator of the item and the software they use. The revenue shared with the software comes out of Steams cut and does not subtract from the creators efforts. In order for Steam to share this revenue, I require a 64 bit Steam ID to link Inkscape's account with my game. I understand this may come with a bit of upfront effort, so allow me to add some context into the potential value from games supporting you this way. The largest game utilising the steam community workshop is Counterstrike with a market cap of $4.6 billion. Creators earn on average $430,000 per contribution (as small as a weapon skin). Earning just a small percentage of this per designer could add up! Thanks again for your tool, and hope I can support you in the near future! _______________________________________________ Contact mailing list -- contact(a)lists.inkscape.org To unsubscribe send an email to contact-leave(a)lists.inkscape.org

3 2

Developer Meeting for March 7th 2025
by Martin Owens 07 Mar '25

07 Mar '25

Developer Meeting Mar 7, 2025 Event: https://inkscape.org/cals/event/64/ Attendees: Martin, Ishaan, Mike, Willy, Jonathan, Elendil, Marc, Tav Next meeting: https://inkscape.org/cals/event/1/ Martin: Started working on the Bugfix accelerator program. Contracts are signed. Many open, high-priority issues are on Windows and MacOS. Mike has been working on dissecting his mega MR, got stuck on in-gamut functionality which he now thinks should be undone. Some color discussion between Martin and Mike. Mike is also experimenting with writing a Viewer for ui files. Jonathan has been organsing the Nuemburg event. There was some organisation needed for the hotel, getting a place with single rooms but people had already booked a room in a hotel. Also worked on the extension event sync system. Asked about 1.4.1 extensions and Marc said that updates should be in place before the Gtl new version is available for windows. Marc worked on the 1.4.1 release candidate installers. Worked on the capypdf building for windows Martin and Jonathan report capypdf build files appering in the source folder. Willy worked on the documentation on the dev said and has been looking at a Korean translation. Asked about getting extensions written in python which work like the python extensions in Blender. Martin gave a description ofhow the current extensions work and why it can't be changed into a blender like system. A new system would have to be wirtten. Tav started working on fixing bugs, two down and 2 being worked on. Jabier has a fix for one of them but the fix has to be understood more. There is some complexity in the node tracking system. We all want to talk about the LPE code in Nuerumburg. How we can refactor it into a healthy place would be on the table. Elendil has been working on the 1.4.1 release notes. There some things missing so far. Also working on the bug accelerator program, currently looking at a crash on clones when closing Inkscape. Tav, Martin and Elendl will meet on wednesday at 10am EST. Jonathan and Isshann talked about visa situations. Thanks everyone for coming! See you next time. Martin,

1 0

Developer Meeting; Feb 27th
by Martin Owens 27 Feb '25

27 Feb '25

Dear Developers, Event: https://inkscape.org/cals/event/1/ Attending: Martin, Adam Belis, Ishann, Jonathan, Marc, Mikekov Next Meeting: Release for 1.4.1, Marc compiling for RC and bug fixing is being prioritised. Inkscape was accepted into Google Summer of Code for 2025. Vectors has been informed so that an announcement can be constructed. First meeting of the Bug Accelerator Project has had it's first meeting. Jonathan asked about making sure Krlr17 is signed up to the milestone, but that appears not to be possible on GitLab. We'll have to just make sure we're watching the page. Mikekov asked about going to the Inkscape Summit and if we can start booking tickets. Jonathan said the timeline is tomorrow for submitting. Martin asked about information around who is going and when they will arrive to better aid the coordination. Mikekov was working on slicing his megga merge request into pieces. Especially his color okhsv work. Asked for a merge request on 6945. Martin has been working on the PDF work so it's finished in time to be able to work on the Bug Accelerator Program. The output is looking great and most of the issues are fixed and most of the features and done. Imbeded SVG images are next to support and will be rendered as vectors. The builds for Windows need help and the builds for macOS will be really questionable consider the XCode requirements for the llvm for C++23. Jonthan has been working on the async extensions work for inkstitch. W talked for a little while about how to make object-set selection saving and where that data should be saved. Adam has been working on some merge requests and back porting. Jonathan wants to talk about dong bug fixing on the master branch and doing work both local and upstream on Gtk issues and cleaning up the remaining problems for all platforms. He needs help with creating a list of work items. Adam was asked to help with the prioritisation and tagging. René negotiated a new agreement with MacStatium for better CI and a remote machine to be able to connect to and test development. Last minute chat about how to talk about UX issues, sometimes they are labeled as feature requests when they aren't really feature requests but valid UX problems. Figuring out if they should go into inbox or if they can go in the main tracker is sometimes a gray area. But UX is important enough for us to take them as real issues and not just features so labeling is important. That's it for this week. Thanks everyone! Best Regards, Martin Owens

1 0