- Inkscape Board of Directors

Developer Meeting Augus 27th 2024
by Martin Owens 27 Aug '24

27 Aug '24

Hey everyone, Thanks to everyone that came to today's meeting. A lot of focus on the release and the tasks needed to get us over the line today. Event: https://inkscape.org/cals/event/1/ Attending: René, Martin, Jonathan, Mikekov, Marc, Tav Next Most exciting thing from René, he has seen the future of macOS CI, because after having talked to someone who is doing this for gstreamer, the tech that allows having the virtualised runners which means you don't need to spend time on build and installation configuration because that's baked into how that would work. The only down side is it requires more hardware resource than we currently have available. the hardware we currently have from mac stadium is currently the smallest size. Though we do want to move towards this virtualisation. René is going to meet with Macstatium tomorrow to explain why we need an upgrade to our hardware setup. If that doesn't pan out René will probably make the setup by himself. René has an open MR which is holding up beta3. We had a look at how important it was to have this fix in time for beta3. We've decided to make a beta3 without the raster image extensions so we can get things tested. The pencil target for RC target for September 13th. Jonathan reports his mentoring of the GSoC project for the aidesign file format by Manpreet. The project is pretty much done and has a fantastic release ready code which will be in 1.4. There was a fraudulent zendesk help site which sent users to a fraudulent website. This was taken down. Jonathan gave the background to the previous adobe illustrator importer. He believes we understand what went wrong and we think we can continue the work with a known developer who knows how to develop these kinds of extensions. He will make a vote to fund the proposal after this meeting. Tav talked with pono yesterday about the rate and a base rate of $40 per hour extendable for local conditions. We're looking for 100 hours. The team held a vote to formally request the funding from the PLC. The vote was 6 in favor, zero against. Scour is now inside the inkscape project, if no one comes to help it it will be on the GSoC list of available project. It's not written with the new extensions system and has a lot of duplicate code. Mikekov is working on the popup editing feature for inkscape in the object properties. It's a work in progress. Martin suggests splitting out any refactoring so it's easier to review if there is any. Martin asked Tav if he could do an assessment on the open bugs for 1.4. Marc completely rewrote the debian packaging for the PPA, this only works on 24.10 because that is the first version that has all the packages we require for Gtk4. And only for AMD64 as there are some test failures on other platforms. There are a bunch of extra fixes for the debian packaging for language and extensions including splitting out inkex. We have a look at fininasing what's needed for 1.4 See you all next time! Best Regards, Martin Owens

1 0

Developer Meeting Aug 19th 2024
by Martin Owens 19 Aug '24

19 Aug '24

This week we had a highly technical meeting with our core developers. Meeting: https://inkscape.org/cals/event/1/ Attending: Martin, Jonathan, Mikekov, pbs, Rafael, René Next Meeting: August 27th, 2024 Issue with the windows build for 1.4, a missing dep maybe for ImageMagic, Marc edited it just an hour ago. The way 2geom is imported has been corrected, but the CI builder doesn't do the right thing for testing. PBS presents the issue of using asyinc coroutines for the Gtk4 dialogs. There's a way to wrap the gtkmm calls to be coroutine compataible. PBS asked about using getThing() or jsut thing() in API design. Martin tends towards using get when calculating but goes for whatever is around it when editing code. Martin takled with René about the crossink status and how much work we have to do to get windows builds to work in wine. We talked about using a VM vs. using crossink and how important it is to get developers to comile and test issues with windows builds. We talked about getting fixes into upstream Gnome, Gtk project and some of the technical and social barriers to to doing that. Is Gtk portable or is it crossplatform? We need to know what Gtk thinks these mean to know what their mission is so we can best fit their expectations. Jonathan talked about mentoring his GSoC student for the afdesigner importer. The student needs to write up what he's done and most of the things are supported in the donated files. He found out what clipboard data is available, curiously afdesigner makes an x-inkscape-svg clipboard type. But we'd still use the afdesigner importer for that. Jonathan brought up how we want to re-organise extensions. Mikekov has gotten back into reviewing some of the designs and implimenting them for the object properties dialog. We talked about how the update process works which is too corse at the moment. Rafael was working on the marker tools and is doing a top down rewrite including the on canvas marker editing. Martin talked about doing the color stuff in python and support and testing it. Will support a couple of the new CSS module 4 color formats for exporting. That's it for this week. Thanks everyone for coming to this week's meeting. Best Regards, Martin Owens

2 1

Developer Meeting, Aug 11th 2024
by Martin Owens 11 Aug '24

11 Aug '24

Hey everyone! Meeting: https://inkscape.org/cals/event/1/ Attending: Martin, skipper, Marc, René, Raven King, Ishaan, Tav, pbs Next meeting: 19th August We talked briefly about the hardware program and Adam leaving and the SFC's failure. Further details about this will be sent to the plc mailing list soon. # GSoC Skipper wanted to ask about problems with UX follow up now that Adam has left. Vaibhav is the mentor and suggested coming into the meeting to find out how to proceed. Martin talked about a similar issue currently being felt in the node delete tool. Suggested coming to the chat or post an issue where the discussion could be done. Marc recommends making a proposal and use that as a starting point, especially since people who are not happy about it will have to give their arguments. # Beta3 for windows The background is that we have a beta2 which is not functioning for windows users and since we have significant windows issues, then we need to make a beta3 as soon as possible. René says that if we need a beta4 or beta5 because we can't get it working, then so be it. René wants to know if some of the deps need to be updated or not. There are a few things to do. # Release procedure Moving everything to the CI builder so there's much less work to do and we can all know how a release is done. We're still building the 32-bit windows in order to have access to Arm builds. If we had a machine that built for Arm we wouldn't need this. We briefly talked about support and what Inkscape supporting users means. Pbs wants to talk about the broken Debian packaging link and how it's stopped working. We talk about how Debian packaging on launchpad is done and some of the details about how that system works for us as a sort of CI builder. He also fixed some issues with the AppImage builder, specifically to do with CJK support. But the fix isn't available to Inkscape 1.4 because of how it would be built with upstream libraries. Philip wanted help with the AppImage but there weren't anyone in the meeting who knew AppImage very well. Recommended to post to the mailing list. # Procedures We talked about how to create merge requests, and what is expected of developers. Assigning themselves to issues, reviewers and keeping their local admin clean to help other contributors. We talked about spaghetti code and various issues with trying to keep the code tidy. We talked about limiting the merges to master to people who have two factor authentication enabled on Git Lab. # Other items Is there still font issues on windows for user installed fonts? We think this is fixed, but we're not sure. Spellchecking has stopped working on master. It looks like an upstream issue. Philip was working on GUI free Inkscape and tab based Inkscape, which was too much to do at once. Tav did some of the groundwork for this with things like SPDesktop. # Activity We worked on merge requests for 1.4.x at the end of the meeting. Best Regards, Martin Owens

1 0

W3C WG Charter
by Martin Owens 05 Jul '24

05 Jul '24

Hey guys, Is this anything we need to pay attention to? https://lists.w3.org/Archives/Public/public-new-work/2024Jun/0012.html They've been posting it on social media, is this part of the move to part svg into a non-active mode within their org? Martin,

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

VOTE: Working group policy
by Jonathan Neuhauser 14 Jun '24

14 Jun '24

Dear all, ===== Background ===== Following discussions at the Bensberg Hackfest, we have drafted a Working Group policy. From a PLC perspective, this makes "teams" well-defined entities, to which we can assign responsibilities and give decision powers. I've incorporated the comments I received since last week, so now we vote on it. ===== Ballot ===== A: I accept the Working group policy as attached. B: I don't want a working group policy at all. C: Other / I require the following modifications: ___ Thanks in advance, Jonathan

5 5

Vote: Affinity License for GSoC student
by Jonathan Neuhauser 14 Jun '24

14 Jun '24

Dear board, = Background = My GSoC student is working on .afdesign import and is making very good progress. He’d like to purchase a license for Affinity Designer to continue the work. You probably all got the Adobe news on the weekend, and due to that, there is currently a flash sale. The price in the EU is currently 37€ (50% off). So please vote quickly so we can make use of that. = Vote = A) Authorize reimbursement of Manpreet Singh for an Affinity Designer 2 / Affinity Suite license, up to $100. B) No reimbursement. C) Other: … Best regards Jonathan

7 10

Mastering Academic Essay Writing: Crafting Essays That Capture Attention
by pidrenisto＠gufum.com 12 Jun '24

12 Jun '24

Academic essay writing is an indispensable skill that students must cultivate to succeed in their educational endeavors. Essays serve as a platform for students to articulate their understanding of a subject, demonstrate critical thinking abilities, and effectively communicate their ideas. Whether you are writing a persuasive essay, an analytical piece, or a narrative, the goal remains the same: to engage and inform your reader effectively. "Learn how to make your essay capture https://speedypaper.com/blog/cause-and-effect-essay-topics the reader's attention" is a pivotal aspect of writing compelling essays. Here’s how you can achieve this: Crafting Engaging Introductions The introduction sets the stage for your essay and plays a crucial role in capturing the reader's attention from the outset. Start with a hook—an intriguing question, a compelling anecdote, or a startling statistic—that piques the reader's curiosity and motivates them to continue reading. The hook should be relevant to your topic and set the tone for the rest of the essay. Developing a Strong Thesis Statement After capturing your reader's attention with a hook, present a clear and concise thesis statement. This statement should articulate the main argument or purpose of your essay. It acts as a roadmap that guides your writing and helps maintain focus throughout the essay. A well-crafted thesis statement not only informs the reader of your essay's direction but also generates interest in exploring your arguments further. Structuring Your Essay Effectively Once you have established your thesis statement, structure your essay in a coherent manner. Organize your ideas logically into paragraphs, with each paragraph focusing on a distinct aspect of your argument. Use topic sentences to introduce each paragraph's main idea and support them with evidence, examples, and analysis. Ensure smooth transitions between paragraphs to maintain the flow of your essay. Using Vivid Language and Descriptive Detail To keep your reader engaged, use vivid language and descriptive detail throughout your essay. Paint a clear picture with your words, appealing to the reader's senses and emotions. Use concrete examples and specific details to illustrate your points effectively. Avoid vague language and clichés, opting instead for precise and evocative descriptions that enrich your writing. Incorporating Counterarguments and Rebuttal A persuasive essay often benefits from addressing counterarguments to strengthen your position. Anticipate opposing viewpoints and acknowledge them in your essay. Then, provide a reasoned rebuttal that reinforces your thesis statement and demonstrates your understanding of the topic's complexity. This approach not only enhances the credibility of your argument but also demonstrates critical thinking skills. Concluding with Impact End your essay with a strong conclusion that leaves a lasting impression on your reader. Summarize the main points discussed in the body paragraphs and restate your thesis statement in different words. Avoid introducing new information in the conclusion but instead, offer a thought-provoking insight or call to action that encourages further reflection on the topic. Editing and Proofreading Once you have completed your essay, revise it carefully for clarity, coherence, and conciseness. Edit for grammar, punctuation, and spelling errors to ensure your writing is polished and professional. Consider seeking feedback from peers or instructors to gain valuable insights and improve your essay further. By mastering these techniques and strategies, you can effectively craft essays that capture the reader's attention and communicate your ideas with clarity and impact. Academic essay writing is not only a skill but also an art form that evolves with practice and dedication.

1 0

Creation of the developer working group
by Jonathan Neuhauser 12 Jun '24

12 Jun '24

Dear PLC, = Background = We have recently adopted the working group policy. The developer team has used the its last two meetings to settle on a charter draft, which now needs to be approved by the PLC for the developer team to become the developer working group. The submitted charter below is the consensus of these developer meetings. The PLC’s task is now to evaluate a) whether the charter fulfills the requirements of a working group, and b) whether the responsibilities and interactions are well-defined, don’t intersect with the responsibilities of other working groups (currently: none) and align with the general needs of the project. If approved, the charter is published on the working group’s subpage. We also authorize the dev team to change the “teams” in the “interactions” section with “working groups” if/when these teams become such in the future. = Charter = Name of the Working group: Development team Purpose: Development of the Inkscape software 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 Initial members: Jonathan Neuhauser, Marc Jeanmougin, Martin Owens, Mike Kowalski, PBS, Rafael Siejakowski, René de Hesselle, Tavmjong Bah, Vaibhav Malik, Jabiertxof, Thomas Holder, Diederik van Lierop, Patrick Storz Membership criteria: - New members need two significant contributions before requesting to join. - After two years of inactivity, members can be removed. Decision Making: • Manage and maintain the Inkscape git repository - Deciding what gets merged - Creating protected branches - Managing user access levels • Decide details on the build system • Decide which developer platforms the project supports • Decide which platforms to release and publish to the website • Decide technical architecture and dependencies of the software • Represent the Inkscape project with upstream and downstream projects for technical consultation • Schedule, perform and publish all release stages - Decide on freeze schedules • Decide on paid development affecting the Inkscape git repository before going to the PLC Responsiblities: • Manage the CI infrastructure and configuration • Act as the point of contact for vulnerability reporting • Onboarding new developers who want to contribute, provide developer mentorship (i.e. GSoC and Outreachy) • Maintain developer-facing documentation, including Getting Started developer resources • Assess the stability of the release Interactions with other teams or working groups: • Coordinate with the Documentation team about relevant changes for releases, such as new or changed features. • Coordinate releases with the Vectors team for publicity and official announcements • Coordinate with the Testing team to maintain the bugtracker(s), make decisions about available issue tracker labels, priorities and schedules. • Coordinate with the UX Team for changes in the user interfaces = Ballot = a) Create the developer working group by approving the above charter. b) Deny the creation of a Developer working group in principle. b) Request the following changes: __ If a majority requests changes, the Developer team will iterate on the charter and re-submit the vote. Thanks in advance Jonathan

5 4