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