Inkscape Board of Directors

Download

inkscape-board@lists.inkscape.org

February 2026

3 participants
2 discussions

Bugfix Accelerator 2026.1
by Martin Owens 20 Feb '26

20 Feb '26

Dear Project Leadership, The developer team discussed requesting a fund for bug fixing in the 1.5 branch specifically. This is before a release, it's more about focusing our attention on the many issues in the 1.5 branch and giving us some funding for administration to the bug tracker. Because this may need to be an ongoing program, I will request funding in blocks of three months and we can re-vote the next block on review. I request a budget of $36,000 for 2 x 280 hours of engineering work targeted at bug fixing in the 1.5 release which is approximately 20 hours per week. And like last time $13,500 for 180 hours (15 hours per week) of administration, writing, issues management, priorities, testing and merge requests. Total budget: $49,500 If fewer hours are used per week they can be used and we don't have to vote quite so soon. The recruitment team will be made up of myself and one other Inkscape member who will not be allowed to bid for the work. We will send out a call for interested and available workers to apply for one of the three positions. Reports and meetings as described in the attached document. a. Approve the budget for BFA 2026.1, b. Disapprove c. Something else Thanks everyone. Best Regards, Martin Owens

7 12

Inkscape Meeting Notes, Feb 14th 2026
by Martin Owens 14 Feb '26

14 Feb '26

Hey everyone, We had a focused discussion this week about the AI Policy, including a demonstration of Mikekov using UI to do work and what that looks like for him. Event: https://inkscape.org/cals/event/1/ Attending: Mikekov, Vaibhav, Martin, Elendil Next Event: https://inkscape.org/cals/event/64/ Mikekov gave a full report on his testing of windsurf running claude, the system seems to work well for him for code viewing and understand and then on to planning. The system needs to be driven at each point and driection is added at each point. The output might not be optimal, but with enough prodding he gets good output. Martin has concerns about the ownership and the way in which a Free Software project can reasonable document or recommend tools which are fundermentally unfree. Unfortunatly the amount of hardware needed makes an actually free and capable system unlikely, even for a large project with a shared machine. Vaibhav asked some great questions about the AI system. Martin asked Mikekov to do a demonstration using a task Martin is currenly doing in the rendering engine work. As a team we worked through the prompt and asked Mikekov's personal subscription to work through the small refactoring problem. It's was fairly successful, though Martin will be reviewing it's output for accuracy. We talked about how these tools are available, and their costs. And the ability for summary text to be used in commit messages, and if that is an appropriate way to document code changes or if programmrs should be required to write their own messages. Adding plans and other meta data to the commit or repository or if we should require them to be attached for example with disclosure. We also reviewed a new merge requests for Elendil at the end of the meeting. Thanks to everyone who was able to come. See you next week. Best Regards, Martin Owens

1 0