- Inkscape Devel - Inkscape Mailman

Developer Meeting, July 10th 2024
by pulsar17 10 Jul '24

10 Jul '24

Hi all, Following are the meeting notes for the Developer Meeting on 10th July 2024: Attending: Rene, Tav, Ishaan, Elendil (Krlr17), Ravi Rene worked on dependencies and engaged in a few Windows related MRs. Also need to work on Documentation CI Tav working on bug report where there are no tooltips on menus. MacOS might not support tootips on menus. Elendil (Krlr17) informed Snap version is broken badly, so we shouldn't have it as default on Ubuntu. Export dialog does not work. A lot of issues reported for the snap version. We can ask Ted to join the next dev meeting to discuss the future of the snap. Ishaan managed to report a few bugs on MacOS. Was busy otherwise ^^ Ravi continued work on his GSoC Project (Node based filter editor). Opened an MR as well. More discussion on tooltips. Some history about Objective C and Swift from Rene. Rene discussed about not stopping jobs/pipelines on master as it breaks links. Next Meeting: Thursday, 18th July Thanks for everyone who was able to make it to the meeting! Best Ishaan Arora > A man’s not dead while his name is still spoken.

1 0

July Vectors Meeting
by Maren Hachmann 04 Jul '24

04 Jul '24

Hello Vectors (and everyone interested in what we do), our next Vectors team meeting is on Saturday! Here's the proposed agenda: https://gitlab.com/inkscape/vectors/general/-/issues/289 Please comment on items you think should be added (or add them yourself, if you have the necessary permission)! Please also have a look at the Working Group Policy (see agenda) in advance. Here's a shortcut to find the concrete time for your time zone: https://inkscape.org/cals/ (note: this is an hour later than before the time switch to summer time!) Maren

1 0

Developer Meeting Notes; 2nd July 2024
by Martin Owens 02 Jul '24

02 Jul '24

Hi Everyone, A quiet meeting this month, most issues were chatting about details, some omitted here. Event: https://inkscape.org/cals/event/1/ Attending: Mikekov, Martin, Tav, René, Ishaan Next meeting: July 10th 2024 * Martin and Tav reviewed the Bug accelerator program, making sure hours and tasks completed are reported and how the program might be improved next time. Finding issues to do was an issue for Tav who didn't have the link to the milestone page. * René wanted to review the release plan with Marc taking a break. We won't know more about if we'll have a tag this week or next but we'll try and keep everyone up to date. * Several people now don't have access to the Rocket Chat, because we are hesitant to upgrade it but at the same time need Jonathan and René and others to be able to continue to access the chat from their phones. * Tav reviewed the GSoC projects and each of the students. * We talked about macOS and some os the issues there now Tav has had a chance to look at some os the issues. We talked about the way the recent files' menu doesn't have tooltips and how to help remidy that. Some issues with fonts, some issues with Gtk4 were discussed. * Mikekov has been working on the supplimental color pickers and color wheel improvements. He's added a new color wheel type and has been looking of the speed issues with the new code. * Several people have had issues compiling on windows linking errors. Mikekov gave up trying to do development on windows for now. * We all reviewed the terrible delay in getting computers bought by the project and how we can work around the issue by buying the machines are getting reimbursed from the SFC instead. This is the action that Tav has taken, and Adam may also do this. Though we are aware of the restrictions this places on people who don't have the capital to purchas machines out of their own pockets. So we need a better system in any case. * Ishaan got a macOS from work and has been testing various things in 1.4 and 1.5. 1.5 seems to have the best experience on macOS. Has continued to work on selection changes, currently stuck on a problem with units. Martin helped walk through all the different coordinate systems in inkscape. * Ishaan also wanted to ask about a new contributor who is having issues building windows but is always communicating in private messages despite being asked not to. Ishaan wanted advice on how to handle it. Martin gave some advice about being clear and setting boundries and explaining why it's a problem to ask in the wrong channels. Hopefully it won't need more moderation. Best Regards, Martin Owens

1 0

Developer Meeting, June 24th 2024
by Martin Owens 24 Jun '24

24 Jun '24

Today is a combination SFC catchup and developer meeting. Event: https://inkscape.org/cals/event/1/ Attending: Martin, Ishaan, Mc, MikeKov, pono, Ravi, René, skippr, Tav, Vaibhav Next event: 2nd Jul 2024 First SFC item was computers for Adam, Tav and Vaibhav. Pono said he'd work on these items today after his two other meetings. Second pono mentioned that the SFC is on it's way to being able to set up Patreon for us. There's some questions about how we should position ourselves on the platform if we wanted to join, and we defer the discussion for later. Third SFC item is about reviewing our trademark policy after the last time we touched it with Chris Roger's book and he thinks it's time to review now while there are no issues outstanding. Update on the release and the beta2 so we can continue the process. René and Marc are happy to make a release in the coming week and Martin suggests Friday the 28th. Marc says he'll be able to tag on Thursday the 27th and then René and others can build and publish the beta2 release over the weekend to have the final beta2 published by Sunday 30th. We will inform Maren and the other people who are involved in documentation and release notes and how much time they might need for the final release. Tav has been getting inkscape to work on his new Inkscape provided mac mini. Eventually using the René is holding off buying an Arm processor surface windows machine as it's quite expensive. Despite the promises of them being better machines. René had a look at the gimp code and how they are building Gtk3 for macOS. There's still some issues with our build and there may be things we can learn from them. Though what we can learn in time for any Gtk3 release we plan to do is an open question. Mikekov has been working on color sliders and the replacements for the spin buttons. Incorperating Tav's spin button widget work on top of Martin's color slider replacement work alongside much improved visual representation of the widgets. Mike wanted to know if he'd covered everything in the new widget needed. Martin suggested inviting in an accessability person in to review the new widget and tell us what kind of accessability is needed. Mikekov and Martin talk about colors, the need for color module colors and what's available in CSS. Color wheels and the way we handle colors per document or per object. Vaibhav worked on text on path UX improvements to add handles to be able to change how the text on path is working on canvas. Exciting work. Ravi has been working on their Google Sumer of Code project the Node based Filter Editor. Nearing completion of the base of the editor, and hoping to have all the basic functionality in terms of usage to be completed by the next two weeks. Skippr has been working on GSoC on the pen tool improvements; they are working with Adam to decide the key bindings for the functionality. The first part was editing nodes during drawing with the pen tool the next part is switching to the node tool while using the pen tool which is more tricky. The team thanks René for his work in ensuring our community is writing good commit messages and is teaching new contributors how to write better commit messages. Ishaan got the rubber bans and select tools all merged, and is now working on the selection ques styles. The styles are controllable in a basic way via a css theme file. He has a question about the thickness of the lines and the difference in handle position on master might need to be fixed. Thanks everyone for comming to this week's meeting. The next one will be July 2nd.

1 0

Re: [Inkscape-docs] Small error in the 1.4 release notes draft
by Maren Hachmann 12 Jun '24

12 Jun '24

Hi José, thanks for letting us know, it's good that people look out for issues with documentation and help us out by informing the project. However, the location for the setting has recently changed, the text is correct, you'll see in the next beta. The mailing lists require a subscription to work properly, without subscribing, this is causing some amount of extra work for list administrators. Please subscribe if you'd like to use the mailing lists for informing the community. Otherwise, you can also use the chat at https://chat.inkscape.org (and for documentation, specifically, https://chat.inkscape.org/channel/documentation). Kind Regards Maren Am 12.06.24 um 03:38 schrieb contacto(a)geodestinos.ar: > Hi, sorry I did not know who to contact for it so I am mailing to the lists. > > > In the https://wiki.inkscape.org/wiki/Release_notes/1.4 > <https://wiki.inkscape.org/wiki/Release_notes/1.4>, under *New User > Interface - ( Experimental and Optional )*, where it says "If it is > activated under Edit > Preferences > Interface > Dialogs : Text and Font > dialog" should say "Edit > Preferences > Tools > Text Tool : Text and > Font dialog". > > (at least for the released official beta, the option is there) > > > Kind regards. > > -José > > > > _______________________________________________ > Inkscape Docs mailing list -- inkscape-docs(a)lists.inkscape.org > To unsubscribe send an email to inkscape-docs-leave(a)lists.inkscape.org

1 0

Developer Team Meeting, 8th June 2024
by Martin Owens 08 Jun '24

08 Jun '24

Dear developers, A big thank you to everyone who attended this meeting since it lasted two hours to do the drafting of the charter and all the other discussions as normal. Event: https://inkscape.org/cals/event/1/ Attending Martin, datalot, HendrikRoehm, Ishaan, Marc, MikeKov, Rafael, Ravi Arora, Tav, Vaibhav, Jonathan Next Event: Sunday June 16th Finalised the Developer team's new working group charter. This took most of the meeting, Jonathan will post the vote to the plc soon. We have tagged release 1.4 of lib2geom. Rafael is going to write release notes for it. Still to do: check out lib2geom submodule at release 1.4 in Inkscape repository, perhaps to be done in MR 6532. The team made a decision to release another beta. We reviewed all the merge requests targeting 1.4.x before we cut the beta release. Hendrik has an open merge request for master, he's new to the release and wants help to get it merged (backported) for the release 1.4. This was a fix for issues regarding to print settings and specifying page orientation as Portrait vs Landscape. We have looked at the Merge Request, decided that it's ready to merge, and merged it into the master branch. We talked about the beta release checklist and the possible dependencies being corect. One item on the checklist should be ensuring that all pending backports are integrated into the release branch. We mentioned the Python dependencies and discussed the way the versions of dependency packages are communicated. https://gitlab.com/inkscape/extensions/-/issues/575 Ishaan has been working on the selection user interface, making the "rubberbands" and the selection cues look prettier. The code is done and waiting for MR review (https://gitlab.com/inkscape/inkscape/-/merge_requests/6336). Mike, Rafael and Marc were all busy at their day jobs and didn't contribute much during the last week. Tav has been travelling which left him in a similar situation. For Vaibhav it was a light week, he fixed small problem with font selection in the Text Toolbar. Also started working on some on canvas TextPath improvements https://gitlab.com/inkscape/inkscape/-/merge_requests/6534 Martin managed to make a few fixes despite trying to take a mental break. He mostly worked on the Color Refactoring MR and starts to feel that the MR is ready to be merged. Although the MR is big and therefore risky, he believes that we should merge it instead of asking him to cope with comments that he views as sometimes overly strict and nit- picky. Although valuable clean-ups and theoretical future features were suggegsted, Martin believes that it might be more manageable to merge the MR first as it is and consider delivering those future improvements in later, smaller MRs. He pledges to be responsible for fixing any follow-up issues that may result. In addition, he fixed an issue related to URLs attached to semi- transparent objects during PDF export as a part of the Bug Accelerator program. Ravi is a GSoC member and is getting established and will be working on their project. Kyle (Vectors team) came to ask a question on whether any developers would be interested in participating in the creation of a video which highlights the fact that Inkscape is a project run by people, respects users' privacy, as opposed to commercial products. Martin and Marc agreed to participate and record short self-recorded clips the aim of which will be to further this message. Best Regards, Martin Owens

1 0

June Vectors Meeting
by Maren Hachmann 07 Jun '24

07 Jun '24

Hello Vectors (and everyone interested in what we do), our next Vectors team meeting is on Saturday! Here's the proposed agenda: https://gitlab.com/inkscape/vectors/general/-/issues/287 Please comment on items you think should be added (or add them yourself, if you have the necessary permission)! Here's a shortcut to find the concrete time for your time zone: https://inkscape.org/cals/ (note: this is an hour later than before the time switch to summer time!) Maren

1 0

call of 'virtualenv' with option 'p=python3' syntactically wrong
by fi＠igh.de 04 Jun '24

04 Jun '24

Dear Maintainers, after pulling revision 5448704355e03a97d2838e1ba30272db335f0dbb I have built inkscape according to https://inkscape.org/develop/getting-started/ Trying to manage extensions (Extensions -> Manage Extensions) I receive the following error message: There has been a problem creating the python environment: Return Code: 3: b'' b'The path =python3 (from --python==python3) does not exist\n' args: ['/usr/bin/virtualenv', '-p=python3', '/home/xx/.config/inkscape/extensions'] Indeed the call is syntactically wrong. Instead of '-p=python3' the option '-p python3' ### without equal sign should be used. As far as I understand, the problem seems to exist in inkscape/share/extensions/extension-manager-bootstrap.py:69 call('virtualenv', TARGET_DIR, p='python3') which then in inkex/command.py:to_args() is evaluated to the wrong sytnax. According to the (very good) comments in to_args() :Keyword Arguments: * *name* (``str``) -- Becomes ``--name="val"`` ... * *n* (``str``) -- Becomes ``-n=val`` ... it should become ``-n val``. I do not know whether a change would result in problems using other programs that want -n=val. Which should that be? Best regards Torsten -- ------------------------------------------------------------------------ Torsten Finke fi(a)igh.de ------------------------------------------------------------------------

3 2

Developer Meeting Notes 31st May 2024
by Martin Owens 31 May '24

31 May '24

Hey fellow Developers, Event: https://inkscape.org/cals/event/1/ Attending: Marc, Adam, Martin, Ishaan, Jonathan, Mikekov, Vaibhav, Rafael Next event: Sat June 8th We talking about quotation marks and spelling reform in European languages. This was just a bit of fun while wiating for people to join. --------- Jonathan starts of the meeting by sharing a link to the Working Group policy document. The PDF file was missing from the website so Martin is adding it to the PLC team on the website so everyone can download it and follow the template. Martin talked about the two pots of powers that the working group policy wants to help define. The first is the powers that the project leadership comittee vests int he team regarding things like spending money and using the trademark. Jonathan adds that making a release for example is using (or trading) on Inkscape's mark. The second set of powers are things that anyone from any team could do, but that we want to monopolise those tasks and decisions into the team. For example making and "official" facebook group could be done by anyone, but the vectors team would probably want to monopolise the decision making process for that. Jonathan: If you want to initalise something, it should be clear who you have to ask and who doesn't have veto power. Martin wants the list of reponsibilities to be more definitive if possible. The team works through the template for the working group policy to make a draft, each developer was invited to partipate and suggest things: ----------- DRAFT CHARTER -------------- Name of the Working group: Development team Purpose: • Development of the Inkscape software Delegation • Manage and maintain the Inkscape git repository (i.e. deciding what gets merged, creating protected branches) • Decide about the build system (which systems developers can work on, which systems are supported) • Decide about dependencies, technical consultation with up- and downstream projects • Schedule, perform and publish all release stages, assess the stability of the release • Paid development affecting the Inkscape git needs to consult the dev team first before going to the PLC Additional Responsiblities: • Manage the CI infrastructure and configuration • Point of contact for vulnerability reporting • Onboarding new developers who want to contribute, provide developer mentorship (internally or through programs like Google Summer of Code, Outreachy) • Maintain developer-facing documentation, including Getting Started resources Interactions with other teams / working groups: • informing the Documentation team about relevant changes for releases, such as new or changed features • coordinate with the Testing team to maintain the bugtracker(s), make decisions about available tags, priorities / schedule • changes in the user interfaces should be coordinated with the UX team Meetings and (internal) communication: approx. weekly meeting as video call, announced at least a week prior on the project calendar; regular communication via chat.inkscape.org in team_devel Decision making process: by consensus of a quorum of 3 or more people Membership criterion: Initial members: Jonathan Neuhauser, Marc Jeanmougin, Martin Owens, Mike Kowalski, PBS, Rafael Siejakowski, René de Hesselle, Tavmjong Bah, Vaibhav Malik New members are confirmed by at least two current members. After two years of inactivity, members can be removed. ----------- END CHARTER -------------- The plan is to draft this over the comming week and make a decsion about the WG charter. Please get in touch if you have comments and suggestions. -------------- Developer activity: Vaibhav wanted to talk with Mikekov about the font collections, the team discusses how stable 1.4 is and what issues we're fixing and targeting for the release. He worked on a bunch of UI fixes. Addressing a freeze in the file selector dialog. Most of the program hours are consumed, will be reporting to Martin tomorrow for the blog post. Jonthan is jumping into fixing C++ bugs and is mostly done with the work he wanted to do on extensions. Martin has been working mostly on the color branch and fixing some issues with the bug accelerator program, not many hours used this month. Mikekov asked about clipping colors. Mikekov trying to work on the proposal from adam for fill and stroke styles. A couple of MRs and Martin wanted to talk about sp_desktop_style Rafael, some time into the sp-marker refactoring. Rewriting how sp- shapes create markers with about half the amount of code. The goal is to fix a lot of the issues and write tests and also improve the speed of the drawing system. There is still a lot of work for future reafactoring. Ishaan has been investigating how cairo draws lines. How the device scaling works. Big thanks to everyone who came and stayed the extra time to process the charter with us. Best Regards, Martin Owens

2 1

Developer Team Meeting Notes, Thu May 23rd 2024
by Martin Owens 23 May '24

23 May '24

Hey everyone, Big thanks to the large number of people who were able to come to this week's meeting. We went long again because of how many great conversations we had about all sorts of things you can read below. Event: https://inkscape.org/cals/event/1/ Attending: Martin, Tav, Mikekov, Adam, René, ScislaC, skippr, Vaibhav, Ishaan. Marc Next event: Friday May 31st 2024 Tav wanted to talk about merge request 6446, a clarification and icon improvement set of changes to improve how icons get in toolbars get collapsed togther. Tav talked about the functionality and adam expressed how important it was to UX for this merge request to get in to 1.4. The developer team will ask translators to make sure the four extra strings won't be an issue. René has fixed the CI again for 1.4.x, the extensions were updated without checking if the tests were passing. René expresses his anger at having a broken CI for a couple of weeks and wants to make sure that everyone makes sure not to force merges in with test failures. Next week will be looking into the extensions deps requirement for FontConfig and text parsing. Martin talked about the review of the new text features in python/inkex extensions. This will likely get into 1.5 considering the large numbers of changes that will be needed in order to get it to the quality expected of the inkex internal API. Vaibhav, last week most of the week has been working on issues with the FontCollections dialog. Has fixed a bunch of issues and collected them into one MR. Adam has been testing a lot of merge requests and the developer team and we thank him. Vaibhav, Adam confirm they got an email from pono about the hardware purchases. Tav left early so we don't know, but assume he also got one. Marc, tried to find a good way to build master on all operating systems. Josh tested it on 24.04 and confirmed that this should now refix it. Marc is now 800 emails behind in his commitment to read all the activity because of the exceptional bug triaging by Adam these last two weeks. Mikekov, wants to thank Josh for testing his merge request finding an issue in the export dialog. It throws an exception because of it, but the display code keeps crashing out and hiding the real cause. Martin also got caught out with the problem since a thrown error doesn't show in the backtrace any more. Catching the error might be sensible. Marc wants to know when to when we should publish the next beta. Adam thinks there's still time. René asks if we should have a slot for bug triage for the bug accelerator program. Adam agrees. We still have some regressions, some blockers but we are making good progress. Jonathan has put some thinking into how to make released more fun to work on, especially bugs. Maybe some mugs and t-shirts to fix bugs. Jonathan fixed a third of the issues in tthe extensions tracker when he first joined and it's fun, it can be be for people to fix issues. Thought people do have different motivations. A good conversation was had by various people about how to improve developer attention on bugs in general. Jonathan and Adam have been thinking about how to ask users to help us fund these activities more and being more up front with our needs as a project. We've been looking at Thunderbird as a model for how to present these requests to users. Jonathan wanted to add it in for 1.4, though Martin and others suggest that with string freeze an exception might be required to get it in for 1.4 and a meeting with Maren would be a good idea. Martin suggests that spending the time and getting it right then releasing it as 1.4.1, and making sure we're coordinated to measure what the impact will be. We want to know what kind of response we get from users when we explain the situation we're in and designing the interface properly. Trying hard to get credit card transactions lined up beforehand if possible. Ishaan has had a slow week but was able to fix an issue with updating tiles with his new make selection in inkscape prettier merge request. Mikekov has some questions regarding colors, and mikekov and adam share their work on their ux issue which will take a while to get all working. Martin talked a little about the color branch and how this will all fit together. Jonathan wants to highlight the completion of the new working group policy. We will formalising how teams exist and their reponsibilities. We will be transforming the developer team to the developer working group, wwe need a charter which will be submitted to the plc. We'll review and spend next week's meeting May 31st. See everyone next week!

1 0