- Inkscape Board of Directors

Developer Meeting Dec 12th 2025
by Martin Owens 12 Dec '25

12 Dec '25

Hey devs, Big meeting today. Event: https://inkscape.org/cals/event/1/ Attending: Martin, Charlotte, Ltlnx, Marc, Mikekov, René, Pbs, Regie, Ishann, Tav, Vaibhav # The 1.4.3 Release ltlnx is managing the 1.4.3 release and talks about the task list which is almost entirely done. * One item to do is the versioning which Marc will take care of now. * Documentation is in sync. * all graphics are up to date * Martin says Extensions are out of sync and won't be up to date in time for the release. Ishann asked about it. * We will directly pull from the CI for RC build which is scheduled for today. * There is a signing step which is now integrated which improves the process. * Tav concluded his Bug Accelerator program with the fixing of startup crashes on macOS * 1.4.3 RC will e released tonight, and given to vectors to announce so we can get testing. Vectors have asked for an announcement time for the RC, dev team will make the builds and would like as much time as is possible for users to download and test the RC to pick out any major breakage from various updates to libraries and various fixes. Marc asks about website problems for the release. Martin reports that the website is unstable and sometimes works well and sometimes get slow. We looked at some of the remaining critical and blocking issues. Charlotte looked into the keyboard switching issue which may have been fixed upstream, we'll be keeping an eye on it for the release candidate. Other blockers have all been fixed and we look like we're in a good place. René didn't get much of a response for his tofu fix, but knows it's fixed because of other apps that have all been fixed in the same way. # Translations problems Maren brought an issue about possibly AI or automated updates for Swedish and how we handle that Marc says it's all settled. PBS raised a problem with po file being updated frequently which leads to massive submodule repository every time we pull in master branch and update the submodules. the frequency can be adjusted and the old commits can be squashed when needed to save space. 7d day frequency for weblate sync. # Funding discussions We talked about the meeting we had with the owners of Audacity and some of the interesting ideas for funding models. This discussion covered a lot of ground but has not been recorded in the minutes so people could speak their mind. # Any other business We talked about the lack of announcement messages in rocket chat, Ben has fixed the crontab but it's still not going through. Rene talked about sorting out some of the build folders to make it easier to manage changes and remove dead files. Thanks everyone for coming, Best Regards, Martin Owens

1 0

Developer Meeting: Nov 26th 2025
by Martin Owens 26 Nov '25

26 Nov '25

Hey everyone, New time for this week's developer meeting. Event: https://inkscape.org/cals/event/1/ Attending: Martin, Mikekov, Vaibhav, ltlnx, René The meeting time had changed but the website has issues sending out reminders to everyone. A reminder here that you can subscribe the the ical for the developer team's calender here: https://inkscape.org/*developer/calendar.ics add this as a remote calendar in your calendar software and you should get up to date reminders. Martin looked into why the website wasn't behaving and found the crontab on the new machine wasn't migrated. Sent an email to Ben who was contracted to do that work for the migration. Mikekov, Vaibhav and Martin talk about spin button we have a long talk about user experience. Screen sharing was done and we worked out the share of work between Mikekov and Martin who are trying to unify the widget experence. Mikekov has been working on the font selector which uses a preview and icon view which are going away. These are being replaced with ListView and GridView widgets. We also can hide certain styles to collapase families of fonts together. This also resolves some cut off preview problems. Viabhav, not doing too much, tried to replicate the extensions gallery crash. Not replcated on he's local linux machine. Had a discussion with Jabier about LPE archetchture, and wants to write an article about it to clarify the architecture. We talked about the problems in the lpe system and fixing issues with the defs. litnx has been pusing 1.4.x fixes, including the welcome dialog. Martin asked if he could take care of the backports. René has been busy with the prepartions for the 1.4.3 release with updates to the dependencies. Lots of deps because it's been a while. Currently investigating the macOS tofu problem, there are some problems with kerning which might be caused by a dep which might not be fixable. We talked about the release schedule and getting everything ready. The conservative updates to the deps might be a better way to update the macOS and Martin suggests René make an assessment about the work they might have to do vs. the benefit of updating the deps for the point release. René wants to revive the tests for the windows CI. Pbs asked if we could use clang, this was tested but doesn't look like it would work. Thanks everyone for coming everyone. Best Regards, Martin Owens

1 0

Developer Meeting, Nov 18th 2025
by Martin Owens 18 Nov '25

18 Nov '25

Hey Devs! Event: https://inkscape.org/cals/event/64/ Attending: Martin, Mike, Philip, Tav, Willy Next: https://inkscape.org/cals/event/1/ (TIME HAS CHANGED!) Mike has been working on making the newer spin button widget used in the rest of the project. Migrating over the UnitTracker and various widget fixes. Willy is trying to fix 1.4.x: text tool pop-over Spinbutton changes, pop-over closes. and Command bar collapsing issue. Pbs talked about animation and live preview, some time was spent discussing the preview functionality and what we can do to allow changes to be previewed without modifying the document or abusing the rendering engine with extra changes at unexpected times. This discussion was quite long. RPATH issues in our build systems are ongoing. Tav has been working on macOS bugs and crashes where jpeg files are not accessable from finder, this involved learning a lot of how macOS works for depevelopers. and color font support and getting the tests all smoothed out. Talking about the late meeting situation, looks like the best time is 2 hours after the early meeting. Which is about 3 hours earlier than currently set. 6pm France, Noon in Boston, 1am Asia etc. Pbs and Martin talked about the filters engine work and the need for clearing up the premultiplicating situation in bilinear interpolation for various different spaces. Martin has been working on harmonising spin button user experience. Thanks for coming everyone! Best Regards, Martin Owens

1 0

Developer Meeting, Nov 10th 2025
by Martin Owens 10 Nov '25

10 Nov '25

Dear Developer Team, Event: https://inkscape.org/cals/event/1/ Attending: Marc, Tav, Charlotte, Martin, Mikekov, Jonathan Next: https://inkscape.org/cals/event/64/ Tav has been adding color fonts to Inkscape so we support all the various different formats. SVG, OpenType COLRv1, COLRv0 and Google Font thing. He's made some color fonts with the same glyph to test the font support going forwards. There's a couple of failing tests for some clipping and some pepper and carrot text tests. This test is useful for visually inspecting possible problems before committing the changes with slight differences. There's a slight problem with strokes not being rendered in Firefox which makes it hard to compare the SVG Font format. Martin talked about Conical gradients, which are needed for some css and COLORv1 Object to Path. Marc, not much, some updates for weblate and the translations stuff. Tav asked about how easy it is to add a new file, and Marc explained that it's all automatic now so is even easier. There's a security fix in librsvg which is a security problem, we're hoping that the new version will be able to fix it, but we don't know for sure if it will fix it. Marc has time to work on the 1.4.3 release and Martin points to the milestone page on GitLab https://gitlab.com/groups/Inkscape/-/milestones/19 for everyone to work from. Charlotte has been looking into the the bug for windows flashing back and forth in windows. But it's tricky because windows development is so much slower than on Linux even with a powerful CPU. She's also added a merge request and was concerned she has the ability to push directly to master but this isn't the case. Jonathan is still around and interested in working on funding projects but time is tight right now with his PhD. Martin talked about the website and taking payments, is in talk with Ben about putting together the second round of funded work to add that Stripe integration to the website. Martin has been working on widgets in the fill and stroke dialog and has been working on the harmonising the generic widgets so our programs looks more cohesive. And also has been working on some UX testing workflows with RDP and desktop sharing, but the technologies aren't great for disposable desktop sharing. Will share if it's figured out. Mikekov has been working on some UI improvements here and there, the next target is the spin button, we have developed our own based on Tav's work and now we need to remove all the older generic Gtk spin buttons with our more functionality such as unit support. We talked a bit about the design of this widget and all the possible ways of integrating units into the actual box itself. Next meeting we will decide the new meeting time for these later developer meetings. Thanks everyone who was able to come.

1 0

Developer Meeting, Nov 2nd 2025
by Martin Owens 02 Nov '25

02 Nov '25

Hey Everyone, Sunday meeting this week, Monday next week, big thanks to everyone who came today. Event: https://inkscape.org/cals/event/64/ Attending: Martin, Willy(ltlnx), Marc, Philip(pbs), Tav Next Meeting: https://inkscape.org/cals/event/1/ There was a discussion about live path effects and merge requests. We reviewed a merge request which was stuck in review and got it un blocked by the consensus of the team. We talked about some of the difficulties with live path effects and getting things fixed while waiting to get lpe structures refactored. We talked about the release for 1.4.3 and some of the outstanding issues, the file opening in macOS and the language change crashes in windows. A review of a bunch of different issues depending on their priority on the milestone mostly between Itlnx and Pbs. We talked about a Gio security bug which can cause a security issue, but it's an upstream issue and it's only breaking on Windows. We tried to think up ways of testing the issue given out limited access to windows machines and experts who can help debug it. Marc will report a bug upstream to Gio / security gnome org. Marc has moved the translation work their own po files and communicated with the developer and translation mailing lists. Thanks Marc! Martin has paused working on the engine waiting for reviews, they're working to get a new paint order widget which is a restackable widget that allow values based on their order and is poking Gtk with the specific UX they want. Willy was working on the default canvas colors in the preferences and has been looking at some of the difficulties in Gtk4 widgets for color selection. Tav has been working on getting his merge requests merged and reviewing his color font work again. Martin will do the developer survey results next week. Thanks everyone for joining on this Sunday Evening/Morning. Best Regards, Martin Owens

1 0

Developer Meeting, Oct 25th 2025
by Martin Owens 25 Oct '25

25 Oct '25

Hey Devels, Event: https://inkscape.org/cals/event/1/ Attending: Marc, Martin, Elendil, pbs Next Meeting: https://inkscape.org/cals/event/64/ Martin asked everyone to fill out the developer survey. We first talked about adjusting the developer meeting times now that we have lots of new developer and people with new schedules. Tav was to create a survey for possible new times, Marc will follow up with Tav to get that poll. We talked about the data access API, Martin asked Ryan to do a DX (Developer Experience) test of the new API adding a dithering filter. Also added was a color transformation filter and Martin is looking forward to his working being code reviewed. Martin has added a multi page SVG update moving inkscape's custom inkscape:page element to the SVG2 view element. The attributes are pretty much the same. An update mechanism is added and lots of tests for various things. Testing with Firefox and Chrome this work should allow multi page support in other SVG viewers and editors. Marc is working on the translations repository. Finished migrating to weblate and moving the po directory with a submodule and clearing out all the merge requests outstanding. Creating CI jobs for updating and is weighing up an automated or manual process. Now to figure out if we need to remove the CI translator checker, Martin agrees. Elendil has been working on a regression with the version attribute which appears to be missing from the svg files that we are currently exporting from 1.5. Marc wants to talk about XSLT export hidden objects and the way the extensions don't current handle XSLT effect extensions, Marc will write this code to put it in. Martin talked about adding such a feature directly to the export dialog since it's already doing much of the same work for hiding objects off the page. The code already exists. Pbs has touched the recolor artwork google summer of code. Looked into a new packaging system called "Sharon", this might let us deliver AppImage type builds with Vulcan support. Martin and Pbs talked about the color access API and some of the direct and compile time problems between that and the color API itself. Martin answered questions and requested code review as the primary help needed. We talked about some of the llm influenced merge requests and how to handle people who don't even talk without using an LLM. Philip asked Marc about heap and symbol problems, and if plugins (compiled ones) have ever worked in windows because the issues if you need to access things outside of the inkscape binary. There was a discussion about how the extensions and various plugins should work and what is known out in the wild. We talked about the release of 1.4.3 and the focus on bug fixing. Martin would like more developers to consier working on things in the milestone to get it as good as possible. Marc wanted to know about capypdf packaging and what kind of packaging we should expect to see for the 1.5 release. Martin says we're likely to need an up to date version and Marc says he'll make a Debian package and make sure it's available mostly for the PPA. We talked about various packaging strategies. Thanks everyone for coming to this week's meeting. Next one is Sunday 2nd November. Best Regards, Martin Owens

1 0

Developer Meeting Notes: Oct 17th 2025
by Martin Owens 17 Oct '25

17 Oct '25

Hey Developers! Event: https://inkscape.org/cals/event/64/ Attending: Mikekov, Martin, Jabier, Willy, Tav Next Meeting: https://inkscape.org/cals/event/1/ We kick off with Willy who has two open open merge requests for the developer team to consider. One is the rotation snapping which is ready to be re-reviewed. It uses a regulr Spin Button instead of a Math Spin Button so it's got some regressions still. The second is a 1.4.x patch for the toolbars so the buttons dispear one by one instead of chunking entire groups at a time. We talked about the 1.4.3 issues and the open issues and when we can schedule the release. We suggest a December release with a project wide request to focus on fixing some of the remaining issues for 1.4.3 so make it a really stable release before 1.5 comes out. We talked about the 1.5 release and Martin's idea for releasing 1.5, 1.5.1 and then calling the 1.5.2 Inkscape's 2.0. This is in an attempt to promote stability an give users the time to field trial some of the new functionality before we make a big splash with the 2.0. We talked about freeze policy. Mikekov went through some of the remaining open issues in Gtk4. Martin asked if our Gtk upstream needs help or not or if things are progressing organically at the right speed for our release on macOS, windows etc. We talked about the dificulty of getting program admins who can organise projects that pay people to work on different aspects of our release issues. And our recruitment of volunteers that tends to depend heavily on programmers instead of people who might be more stilled in admin releated organising. Mikekov helped with the Dash2 issues, and doing merge requests. His currently thinking about the preferences dialog. He's been medidating on how to clarify the preferences to reduce the amount of duplicate code and depend on the glade file directly. There's a couple of routes to having preferences paths defined in glade files and widgets constructed with simple APIs, there's a refactoring pathway for how we would get there too. But the ultimate aim would be to remove most of the code until only loading of the glade file remains. We talked about how Gtk custom widgets work so we don't need to load each widget by Id. Tav has been working on color in CSS issues with export. He wants to have a meeting with Martin to talk about Color further. He's looking into the problem of integer artefacts and generating example files in 16bit to test how browsers are currently dealing with the older limitations and if they have been overcome. Some of these artefacts are actically used by filter designers as inputs to produce iteresting results. Report on Bug Accelerator Program, Tav has a few hours left. Martin talked about his engine improvements and walked through the entire plan for filters, color, memory surface management and the stepping stones that are being worked on to get everything in place for CMYK support. Tav and Martin talked about various details in support and what it means for SVG. Tav says that the attendance at the late meeting is very poor. Should we redefine a new time for that meeting so it's easier for other contributors. Martin asked Tav to make a survay for all the new contributors about their availability. Thanks to everyone who was able to come to this week's meeting. Best Regards, Martin Owens

1 0

Policy Discussion: Social Media and Inkscape's Presence in other spaces
by Martin Owens 03 Oct '25

03 Oct '25

Dear PLC, The vectors team are requesting guidance on the use of social media spaces such as Twitter which have become problematic. I believe that such guidance can be made into a generalisable project wide policy and present here a draft for what this might look like. Request for comment, since I've probably over thinking it: ======= # Inkscape Community Spaces Policy Inkscape is a project with a wide and inclusive community who participate in many places online. We do not wish to restrict what spaces people participate in as users, or even fan groups; but must be decisive about which spaces can be counted as official, use the inkscape trademark and brand identity and what rules must apply in those instances. ## Official Inkscape Community Space A space which is run by the Inkscape project must follow these rules to be considered an official Inkscape Community Space: 1. It must be run: 1a. On an Inkscape controlled infrastructure or Virtual Private server for example the inkscape website, chat room, forum, etc. 2b. On behalf of the project by a third party running Free Software server components. For example BigBlueButton, GitLab, Mastodon etc 3c. Be given a special exception by the Project Leadership Committee. 2. It must strictly follow the Code of Conduct: https://inkscape.org/community/coc/ 3. It must have a moderator, or moderator team that can respond in reasonable time to abuse. 4. If possible, it should use the Inkscape branding, mark, and domain name to associate itself with the project. 5. Should be linked directly from the Inkscape website as a core part of the community infrastructure. 6. May be private for contributors, special team members, project leads or users in general depending on the needs of the platform. ## Official Inkscape Outpost A space that is run on some other platform, which is used for outreach, advertising, news and to connect with the wider user community in the existing spaces where they have existing accounts. These rules apply to official outposts: 1. It must NOT be run by Inkscape, but must be in a third party website or service. 2. Must have an account or administrator which is ownable by the project where a copy of the required credentials to access the service can be maintained in the PLC accessible credentials repository. 3. Must not be used for contributions to the project: a. As a permanent store of code, merge requests, issues, graphics, or designs or canonical store of official documentation except where it is a published copy or clone for read-only accessibility. b. A singular place for user sentiment, such as polling and surveys, except where such a poll or survey is also available elsewhere AND the results are copied into the project's core spaces for record keeping once completed. 4. Must NOT act as a place where users believe they are talking with, reporting to, or filing complaints with the actual Inkscape Project. When users attempt to contact "The Inkscape Project" through an outpost service, the user should be redirected to official channels, issue trackers, website, mailing lists etc by a moderator. This redirection should be made available in the bio/profile text for clarity. 4. All participants must follow the Code of Conduct and where moderation and administration is possible, the code of conduct should supersede local rules. Where administration is not possible, blocking and block lists may be employed to moderate the spaces. 5. Must not be on a platform known for or owned by people intent on popularising, propagandising or otherwise supporting hate, fascism, terrorism, violence, sexual abuse, and other politically ideological wider communities. 6. Must NOT be linked from the Inkscape website. The outpost service is intended to support users who are already on those platforms, not encouraging new users to join them. But should include links FROM those sites or service profiles TO Inkscape and it's core community platforms such as the website and forums. 7. Should have activity at least once per three months to indicate its still in use and has interest in being maintained. 8. May use Inkscape's trademark and logo, but must try and communicate that it is for outreach, news, user community, etc and where it is a website that invites technical contributions should make it clear that the service is not being used for that an redirect people to the correct resource. ## Fan/User Run Communities Some communities are run by users who are not involved with the Inkscape project and are not bound by our code of conduct. So our rules are generally about the appearance of being official and the use of our trademark: 1. Are encouraged to use the Inkscape Code of Conduct as a way of managing their moderation. 2. Must not use the Inkscape brand or logo unmodified, in the same ways as the trademark policy specifies for Inkscape code and binary publications. 3. Must not use the inkscape name as a domain name, or an inkscape domain with a separate country level top level domain. Except where there is sufficient differentiation that it wouldn't be confused with being run by the project itself. 4. Must not be linked from the Inkscape website, etc. 5. May copy news, announcements, and participate in discussions about outreach where necessary. 6. Must not advertise themselves as official, or create confusion that posting, commenting, or sending private messages would be the same as communicating with the Inkscape Project. ---------------------------------------------------------- Sorry for the long read! Best Regards, Martin Owens

1 1

PLC Status Meeting
by Ted Gould 03 Oct '25

03 Oct '25

Hello Folks, There is a PLC Status Meeting scheduled for tomorrow (Oct 3). Unfortunately I'm going to have to send my condolences again. This time at Texas Linux Fest, which has all of its graphics done with free tools (including a lot of Inkscape). Sorry to miss two in a row. Could someone else run the meeting please? Thank you, Ted

2 1

Inkscape Developer Meeting, Oct 1st 2025
by Martin Owens 01 Oct '25

01 Oct '25

Hey Developers, Event: https://inkscape.org/cals/event/64/ Attending: Martin, Youstena, René, Tav Next Meeting: https://inkscape.org/cals/event/1/ Martin starts off with a quick introduction, and a short update on the website updates and the downtime people may have experienced. René looking into windows CI, it felt so bad that he felt he had to work on it. The goal is to make it faster and usable as being so slow sucks the joy out of everythig. The 7z archive builder is now running on a persistant runner which René said he would never run one again, but it was required to make it much much faster. The mechanism for depedancies was switched from 7z packaged, to a Microsoft based format which has advantages which can mounted and doesn't need to be 'extracted' as well as being more windows native. There's a bit of work more to do which is how easily it is to build depedencies, moving the config back into the main CI builder itself. Martin Martin talked abut Gtk and the need to keep the version we are building with and targeting for 1.5 will have to be a future version because of the known bugs that will have to be fixed in time for release. Martin's work on filter rendering and unit testing and is currently working on Light sources after completing the ConvolveMatrix work last week. A lot of tricky decisions will have to be made about interpolating in other color spaces but the new code will give us the flexibility to choose. Some backwards compatability will be needed for Integer calculations too. Tav has been working on CSS Color parsing and some of the found bugs, checking over our support introduced by Martin in 1.5. The Lch color conversion was wrong and has now been fixed, case insenstivity, and a range issue on Lch. Tav has questions about the color picker, we're currntly using Luv in the color picker. Martin and Tav had talk about color, rendering, document color space. Talking about how to achieve backwards compatibility and various other issues between Inkscape and SVG for color support. Youstena is a student from Egypt who is interesting in contributing to open source and introduced themselves. We asked around if anyone still needed to claim from the SFC, Tav was waiting on something but he'd put it in later too. We may want to make sure per-deim and travel between events where there is more than one event happening should be in the next vote. Thanks everyone for coming!

1 0