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.
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
