- Inkscape Devel - Inkscape Mailman

Inkscape 0.92 review in German
by "Christoph Schäfer" 21 Feb '17

21 Feb '17

Hi guys, I've published a review of Inkscape 0.92 in the Swiss "Publisher" magazine (http://publisher.ch/fachzeitschrift_detail.php?t=Zwischen%2Ballen%2BSt%25C3…). While I did my best to highlight the major improvements, the overall judgement was: "half-baked" and largely negative. I'm sorry for that, but I hope you get your act together soon. And please add adequate PDF export for print workflows and also make sure that Inkscape SVGs can be used and displayed universally. This is more important than new design features, because Inkscape is already one of the most feature-rich vector programmes. Best, Christoph

19 84

Wiki bug template
by Alex Valavanis 21 Feb '17

21 Feb '17

Hi All, I've added a new template to the wiki for linking to Launchpad bugs. See: http://wiki.inkscape.org/wiki/index.php/Template:Bug Basically, you can just do something like: {{bug | id = 123456 | status = triaged}} to generate a color-coded link to the relevant Launchpad page. AV

1 0

About Most Suitable IDE (Integrated Development Environment) in Windows
by Niraj Dave 21 Feb '17

21 Feb '17

Hi, Which Integrated Development Environment (IDE) is most suitable in Windows operating systems for Inkscape from following: 1) Eclipse Name: (ie. Neon) Version: ? 2) Microsoft Visual Studio with VisualGDB Version: ?2) Microsoft Visual Studio with WinGDB Version: ? Please guide me..1) How to decrease compilation time? 2) Is there any automated Tools? which is most suitable? Please give detail steps to configuring development environment in windows for coding and debugging. Note: I have already generated Executable using following commands: >cmake -G "MinGW Makefiles" .. & >mingw32-make -j 2>mingw32-make install but which IDE is most suitable for Inkscape. Thank you, Niraj Dave

1 0

Inkscape 0.92.1pre1 macOS test build
by Tim Sheridan 21 Feb '17

21 Feb '17

Hi all, I've been working on getting the macOS packaging for the 0.92.x working again. The branch is here: https://code.launchpad.net/~tghs/inkscape/0.92.x_mac_packaging I've put a 10.7/i386 test build up for people to try at: https://inkscape.org/en/gallery/item/10660/Inkscape-0.92.1pre1-tghs_0-x11-1… Build info is on the file information page: https://inkscape.org/en/~tghs/★inkscape-0921pre1-tghs_0-x11-107-i386dmg As with the old official 0.91 release, this is an X11 build so you'll need XQuartz installed. Since it's not yet merged, please report any issues encountered in this thread, or to me directly. Known issues: * App not signed (probably wontfix for 0.92 as users put up with it for 0.91, but worth looking at for 0.93) * Built without poppler (need to check whether old releases included it) * Toolbar icons getting cropped slightly on the edges (not a blocker IMO, but would be nice to fix) Cheers, Tim

6 12

0.92.2 plan
by Bryce Harrington 19 Feb '17

19 Feb '17

With 0.92.1 now finished, the 0.92.x branch is reopened for targeted bugfixes, and it's time to look forward to 0.92.2. There are a few other activities that were gated on 0.92.1 which will be proceeding in parallel, most notably of which is the git migration plan, which is hard to guess how long it'll require. I figure since that's obviously going to be disruptive that we focus on completing that before initiating the 0.92.2 release. So exact dates are going to be infeasible, but to establish some basic mileposts: 0.92.1 Now Feature Freeze 0.92.2pre0 TBD Hard Freeze + String Freeze 0.92.2pre1 +2 weeks Release Candidate 0.92.2 +1 week Cut Release I am guestimating earliest we might see 0.92.2 would be late April / early May, but depending on how things go could be more of the May/June timeframe. == 0.92.2 Development Goals == 1. The replacement for DPI dialog is a top goal for 0.92.2. The wording of the dialog in particular needs review, but much of the implementation work is solid and just needs to be landed and tested. Translation of this to other languages is also quite important, and should receive special attention. A 2 week period is scheduled post-String Freeze in particular to help ensure translators have adequate time for this dialog. 2. A GPLv3 widget needs to be removed (or relicensed) to allow Inkscape to return to being covered as GPLv2. While I'd love to see this undertaken for 0.92.2, but if it isn't it doesn't need to hold up the release. Beyond this, changes that fix bugs or address user reported problems are welcome. Please try to keep patches minimal so they're easy to review, and avoid doing refactoring work. Larger works such as new user interface pieces, should be done on branches, proposed for review, and tested thoroughly on trunk before landing on 0.92.x. If you have any doubts over the appropriateness of a particular large change, please feel free to run it by me first. Provide detailed descriptions in your commit messages, including ref to bug #'s and an explanation of the user-visible problem that the patch fixes. This helps testers isolate regressions and assists in creating the release notes.

1 0

Post-Mortum: Line height bug
by Martin Owens 17 Feb '17

17 Feb '17

Developers, As someone how changed the line-height code prior to release, I feel somewhat responsible for the issue in 0.92. I really didn't have enough time to focus on bugs before the release, but should have spent more time on things I'd changed. I'm really sorry Inkscape. This thread isn't for figuring out how we're going to solve the issue though. I'll let the 0.91.1 discussion cover that. What I'd like to pick apart is our bug management and how a release blocker like this line-height issue didn't put an all stop on our release schedule while we figured it out. There's a couple of possibilities: 1. The bug wasn't discovered in time 2. The bug wasn't reported in time 3. The reported bug wasn't triaged in time 4. The bug wasn't prioritised as important 5. There wasn't a way to communicate a major issue to the release manager. 6. We just didn't have the resources to do the release properly and let things slide. What information can Mc and su_v add about the issue? What can we fix to make the process better? I feel bad asking for your help to really figure this out, but I think this might help us as a project overall if we know what happened and how to defend against it. Thanks everyone. Best Regards, Martin Owens

9 44

Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug
by brynn 16 Feb '17

16 Feb '17

I didn't include it in the job description part. But I was just discussing user testing of new releases (before release) and it occurred to me that perhaps an Advocacy Team could take the lead on potentially organizing user testing? I'm not sure if that makes sense, but if it does, I'll add it in. brynn -----Original Message----- From: brynn Sent: Thursday, February 16, 2017 4:49 PM To: Bryce Harrington Cc: C R ; inkscape-devel ; Martin Owens Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug I couldn't find the exact message where I mentioned making a new item on the To-Do List page about an Advocacy Team leader. But this point in the discussion was pretty close. So it's at the bottom of the list. Please feel free to tweak, or if you don't have website access, tell me what to change, and I will. https://inkscape.org/en/contribute/to-do-list/?edit_off=true All best, brynn -----Original Message----- From: Bryce Harrington Sent: Monday, January 30, 2017 12:19 PM To: brynn Cc: C R ; inkscape-devel ; Martin Owens Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug On Sun, Jan 29, 2017 at 01:29:31PM -0700, brynn wrote: > (Martin copied in, just fyi, no specific reply needed) > > Sorry, fairly long reply (tldr for most readers) Ditto, but I'll try and be brief in reply. > The sections look good. Would it make sense to reverse the order? > ____________________ > > That's interesting thought. I seem to recall my first version of > the page, the sections were reversed. I was thinking - list them > from easiest to hardest, or things that take less skill, to things > that take more skill. > > But someone else said to have the coding stuff at the top, because > that's what the project needs the most. I'm personally neutral on > this, and I'm happy to make whatever changes are needed. If you remember who that person was, might be worthwhile to loop them in on this discussion. (Heck, could have even been me!) It's certainly true coding is important but again we have the whole Develop top section devoted to it, so I really think we're ok on that count. Other things beyond coding are also critical to the project, and as most visitors to our site are probably non-coders I feel we really need to ensure we have an inviting-looking place for them, and I would worry leading with Coding might put them off. > >(E.g. the opening sentence > of Contribute and Promote ought to be more engaging.) > > I agree that would be a good idea, and I'll make a rough draft, > maybe using the first paragraph of that last bit of info in the wiki > (which I like). But C R has offered to make suggestions too. > Should I just make working page, that we could all access and tweak > on? I don't remember if C R is a website editor. Sounds like a good starting point. > >I really like the Community To-Do List page (contribute/to-do-list) and > > I had hoped that this would be a useful page. But no one seems to > be interested in those projects that are listed. Maybe because a > lot of them need significant experience with the project. I think that may be true. They did strike me as a bit advanced. I will try and help with ideas of more things we can include here. Bug me if I forget. It's also likely people just aren't aware of the page, so once we flesh it out more it would be good to evangelize it a bit (more on this below). > I don't see "non-coding" as less important. When I read the title, > I get excited, because here's something I could actually help with. > It doesn't make me feel bad about myself, and I think my self-esteem > is fairly intact. *Grin* Fair enough! > But I understand that "non-" is a negative, and > something more positive might be better. I just can't think of a > good alternative. Suggestions? What's the opposite of coding or > programming or hacking? "Other" would probably be too vague. Yeah Other would be too vague, I almost suggested General but that's also vague. I suppose since I don't have any better ideas leave it as is and if I think of something later or someone else comes up with a brilliant idea, we can tackle it then. Maybe a differing perspective would give some better ideas. > I'm not sure if the Promote page might be ill-conceived or not. All > of it really contributes to the project (everything on both > Contribute and Promote pages), but it's too much material for one > page. And Promote was the best thing I could come up with for a > page name. Open to suggestions. How about "Evangelism"? I've heard that term used in other FOSS projects and it has a nice ring to me. I do think this is an important role in the project, one that I wish we had more people engaged on. Announcing releases would be a crucial duty here, and a number of the activities the Board is engaged in would work much better if we had a better organized team focusing on this. As I've written previously, what makes FOSS projects like Inkscape successful is not vast userbases or lots of income - it's people like us contributing to the code and community in myriad ways both tangible and intangible. So a #1 purpose for an evangelism team would be contributor community building. Not necessarily like hard-sell 'recruitment' but more building connections between people and ensuring there are easily accessible on-ramps for people to join in. A lot of things would fall under such a group, from establishing presence in software and artistic communities both online and off, sending reps and presenters to artist-focused events, arranging training opportunities (both user-focused and development-focused), writing, pushing news items on our site, and more. > >The Helping Other Inkscape Users should be moved from the Promote page > to its own page. > > That section is a little longer than Spread the Word, but still > makes for a pretty short page, by itself. I guess I wouldn't have > any objections. But if it could be expanded, would be better, imo. > I just can't think of any other ways for helping other users. Ok, seems sensible. It can always be broken out later if/when there's more content for it. > >The Translations section looks fine. > > Yes, I think Maren has tweaked that page to perfection. > Unfortunately, I think she wants to take a break from website > editing, except for translation-related things. I'll try to use it > as a guide for the others. And if anyone else wants to help, of > course let us know! Understandable, and yes this would be a great area to bring in more people. > >The Bugs section I think could be made more specific to just Review and > Verify Existing Bug Reports. > > For the Bugs section, Testing, and Working with Code, I don't have > the knowledge for making all the changes you described. I can move > Report Bugs into the Testing section. But I can't make any of the > other changes to Testing that you mentioned. I just don't have that > knowledge. Yes, totally understood. I mentioned it more because it is something that "needs to be on our collective todo list" and realize drafting something sensible will be a large project. I will try and work on it as I have time and keep an eye out for folks that could assist. > I can move Packaging to the top level Develop page, and delete the > Write Extensions section, if you like. I don't follow your logic, > but it's probably because I don't understand programming. Sounds good. > Are you saying you want a page on the website, rather than a wiki > page, for Website Development? I don't have the right kind of > knowledge to be able to write such a page. All I could do is copy > the wiki page over to the website. Glad to do it, but also welcome > help in spicing it up. Right, exactly. I'm anticipating that Martin will have a place in mind to direct potential web developers to for orientation on website work, so am just suggesting we should point to that from here. Thanks, Bryce

1 0

Inkscape 0.92.1 now available
by Bryce Harrington 16 Feb '17

16 Feb '17

The Inkscape project announces an update to its 0.92.0 release, bringing important bug and regression fixes, updated translations, and improved documentation. Download 0.92.1 packages from: https://inkscape.org/en/download/ Inkscape 0.92.1 is a stability and bugfix release. Below lists the main changes. For a more complete list, see: https://launchpad.net/inkscape/+milestone/0.92.1 == Regression fixes == * Text: baseline-spacing related issues with regular and flowed text in legacy Inkscape SVG files (Bug #1655483 and others). * Text: Default baseline spacing stored in relative units is always converted to document units (Bug #1645016) * Path effects: Crash on ungroup if group contains elements with path effects (Bug #1657591) * Clipboard: Pasting a path effect from clipboard fails (Bug #1656093) * Clipboard: Fix copy&pasting of groups which contain elements with path effects (Bug #1656527) * Selection: Node tool can selected objects on locked layers (Bug #1656141) * Clones: Critical warnings with clones and symbols (Bug #1653184) * About screen missing for several UI languages (Bug #1659426) * Selection: Missing transformation handles after reset of rotation center (Bug #1657874) == Important bugfixes == * Bitmap images: Crash when opening files with invalid image links (Bug #1660142) * Bitmap images: Fix path separators in relative image links (Windows) (Bug #1659347) * File import: Failure to open CDR/Visio/WPG files from paths with special characters (Windows) (Bug #1656763) == Translations == * Catalan: Tutorial translation ("Basic") added * Czech: UI translation updated * English (GB): UI translation updated * French: UI translation updated * French: Man page, Readme and Keys & mouse reference updated * German: Man page and Keys & mouse reference updated * Icelandic: UI translation updated * Italian: UI translation updated * Latvian: UI translation updated * Russian: Tutorial translation ("Tracing Pixel Art") added * Russian: UI translation updated * Spanish: UI translation updated * Slovak: Tutorial translation ("Tracing Pixel Art") added * Slovak: UI translation updated * Ukrainian: UI translation updated == Documentation == * Shortcuts: Add shortcut '7' for cycling through path effect parameters in node tool (Bug #1656713) * Shortcuts: Add new Shift+I shortcut to keys and mouse reference (Bug #1644609) * Man page: Add new --no-convert-text-baseline-spacing command line option (Bug #1661811) == Known issues == * DPI Change: Dialog needs better explanation of available options (Bug #1659229) * DPI Change: Provide command line options for batch-processing legacy files (Bug #1659489) * DPI Change: known issues with 'Scale elements' option (Bugs 1653230, 1653230, 1653236, 1654342, 1654796, 1654880, 1654903, 1655005, 1655053, 1660228) * DPI Change: Default grids in documents created with Inkscape 0.91 don't scale correctly (Bug #1653893) * Renderer: Artifacts in Gaussian blur effects with default quality settings (Bug #1656383) * Node editor: Deselecting selected nodes of complex paths takes a long time (Bug #1652100) * Fill and Stroke: HSL color selector may show corrupted colors, defunct 5th slider (Bug #1635982) == Help Support Inkscape == We are already at work both on another bugfix update (0.92.2) targeted in a few months and a future development release (0.93) with more fundamental changes to the codebase. If you wish to track either of these developments, you can learn more at: https://inkscape.org/en/download/development-versions/ The Inkscape Project thrives due to your support. We are a volunteer-driven community built from thousands of contributions of time, skill, and funds, to create a powerful open source tool that is made available for free to everyone in the world. We invite you to join our community and participate in helping advance Inkscape towards new objectives. Come help us chart out the new directions that Inkscape needs to take! Inkscape is created *by* the community *for* the community. Your donations also help further Inkscape's mission. You can donate to Inkscape's general fund, or target your donation to support our SVG Standards work or Hackfests. -------------------------------------------------------------------- Join Inkscape at: https://inkscape.org/community/ Become a donor at: https://inkscape.org/support-us/ Download Inkscape at: https://inkscape.org/download/ Watch our showcase at: https://www.youtube.com/watch?v=EI1hxXt9U4c --------------------------------------------------------------------

1 0

Flatpak for Inkscape 0.92
by Matthias Vogelgesang 15 Feb '17

15 Feb '17

Hi, is anyone of you interested in a Flatpak recipe or hosting the repo and/or bundle for Inkscape 0.92? You can find the flatpak-builder recipe at https://github.com/matze/inkscape-flatpak Personally I do not have the resources to host the repo (93 MB) nor the bundle (18 MB) for a large amount of users. However I think it adds value for distro users that do not support snaps. Best regards, Matthias P.S.: I know there used to be a Flatpak for Inkscape but I haven't found anything at all about it. -- Matthias Vogelgesang | bloerg.net

3 7

Feedback on measuring tool
by Bryce Harrington 15 Feb '17

15 Feb '17

----- Forwarded message from mike abbey <mabbey1985@...400...> ----- Date: Thu, 9 Feb 2017 17:30:07 -0500 From: mike abbey <mabbey1985@...400...> To: Bryce Harrington <bryce@...961...> Subject: Re: [Inkscape] [Inkscape-devel] Inkscape 0.92.1pre2 (release candidate) now available that would be fine. make sure that they all know that they do great work. i use it to make a few scrollsaw patterns and it does everything i need for that and more. thanks for all the hard work. On Thu, Feb 9, 2017 at 2:06 PM, Bryce Harrington <bryce@...961...> wrote: > Great to hear Mike, do you mind if I forward your email along to the > development list? I didn't work on that feature myself but am betting > those who have would love to hear your feedback. > > Thanks, > Bryce > > On Thu, Feb 09, 2017 at 06:55:16AM -0500, mike abbey wrote: > > i have to tell you that with the measuring tool in the .92, well, i love > > it. in .91 holding the mouse to make it stay was a pain. but now click > > click and it stays on its own. with the awesome work you and your team > have > > done with this i would never go to a paid program. keep up the good work. > > > > On Wed, Feb 8, 2017 at 5:45 PM, Bryce Harrington < > bryce@...961...> > > wrote: > > > > > On Wed, Feb 08, 2017 at 02:33:27PM -0800, Bryce Harrington wrote: > > > > This is a pre-release for the upcoming stable bugfix release 0.92.1. > > > > Download it at: > > > > > > > > https://inkscape.org/en/download/development-versions > > > > > > > > The release is: > > > > > > > > 0.92.1pre2 Source Tarball Bzip > > > > https://inkscape.org/en/gallery/item/10661/inkscape-0. > > > 92.1pre2.tar.bz2 > > > > > > > > We are now in final freeze prior to release. Barring any last minute > > > > issues, 0.92.1 will be identical to the above tarball except for the > > > > version number. We'll let things settle for a few days and hopefully > > > > finalize the release this weekend. > > > > > > And release notes are here: > > > > > > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.1 > > > > > > > == Translations == > > > > > > > > Translation work is done. Please hold off on further updates until > > > > we're ready to start work on 0.92.2. > > > > > > > > > > > > == Future Releases == > > > > > > > > 0.92.2-targeted bugfixing work can begin on the 0.92.x branch once > > > > the 0.92.1 tarball's been cut, probably this weekend. A schedule > will > > > > be established at that time as well, targeting a 0.92.2 release in > > > > April. > > > > > > > > A 0.92.3 release sometime around July seems likely. I'm hoping to > > > > continue with subsequent point releases on a roughly 2-3 month > interval, > > > > so users can depend on the 0.92 series as a 'long term stable' (LTS) > > > > product. > > > > > > > > Work towards 0.93 is already underway in Inkscape's trunk repository. > > > > In order to modernize Inkscape for ongoing maintenance, there are > > > > several large transitions we need to undertake, including a move to > > > > Gtk3, re-engineering the Mac OS X installation packaging, > introduction > > > > of C++-11 code constructs, dropping of our legacy automake build > system, > > > > migration of the project to git, and more. We had elected to hold > off > > > > on these transitions for 0.92 so that release could focus on long > term > > > > stability first and foremost, with 0.93's focus being on taking the > more > > > > aggressive steps to move Inkscape forward. > > > > > > > > I am hoping a 0.93 release can be achieved within the calendar year, > > > > though much work remains. Assistance with testing is invaluable and > I > > > > hope many people will join in following the trunk codebase; however, > I > > > > know that building Inkscape can be a challenge, and we lack nightly > > > > builds on a few platforms, so I may attempt some form of interim > > > > snapshot preview release this summer to enable some broader testing > > > > before we're too far through 0.93's development cycle. > > > > > > > > Bryce > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1 > > > > > > > > iEYEARECAAYFAlibnLcACgkQEaMBVuDmdhEKOwCeKgWKHLllZtGTsb877b9+8WQz > > > > hmEAnAhKdRKjn25SYLVBGMZ5pfuHMj1f > > > > =aOtL > > > > -----END PGP SIGNATURE----- > > > > > > > > > > ------------------------------------------------------------ > > > ------------------ > > > > Check out the vibrant tech community on one of the world's most > > > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > > > > _______________________________________________ > > > > Inkscape-devel mailing list > > > > Inkscape-devel(a)lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > ------------------------------------------------------------ > > > ------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Inkscape-announce mailing list > > > Inkscape-announce(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/inkscape-announce > > > > ----- End forwarded message -----

1 0

Inkscape 0.92.1pre2 (release candidate) now available
by Bryce Harrington 12 Feb '17

12 Feb '17

This is a pre-release for the upcoming stable bugfix release 0.92.1. Download it at: https://inkscape.org/en/download/development-versions The release is: 0.92.1pre2 Source Tarball Bzip https://inkscape.org/en/gallery/item/10661/inkscape-0.92.1pre2.tar.bz2 We are now in final freeze prior to release. Barring any last minute issues, 0.92.1 will be identical to the above tarball except for the version number. We'll let things settle for a few days and hopefully finalize the release this weekend. == Translations == Translation work is done. Please hold off on further updates until we're ready to start work on 0.92.2. == Future Releases == 0.92.2-targeted bugfixing work can begin on the 0.92.x branch once the 0.92.1 tarball's been cut, probably this weekend. A schedule will be established at that time as well, targeting a 0.92.2 release in April. A 0.92.3 release sometime around July seems likely. I'm hoping to continue with subsequent point releases on a roughly 2-3 month interval, so users can depend on the 0.92 series as a 'long term stable' (LTS) product. Work towards 0.93 is already underway in Inkscape's trunk repository. In order to modernize Inkscape for ongoing maintenance, there are several large transitions we need to undertake, including a move to Gtk3, re-engineering the Mac OS X installation packaging, introduction of C++-11 code constructs, dropping of our legacy automake build system, migration of the project to git, and more. We had elected to hold off on these transitions for 0.92 so that release could focus on long term stability first and foremost, with 0.93's focus being on taking the more aggressive steps to move Inkscape forward. I am hoping a 0.93 release can be achieved within the calendar year, though much work remains. Assistance with testing is invaluable and I hope many people will join in following the trunk codebase; however, I know that building Inkscape can be a challenge, and we lack nightly builds on a few platforms, so I may attempt some form of interim snapshot preview release this summer to enable some broader testing before we're too far through 0.93's development cycle. Bryce

3 9

FreeBSD as a step to OSX
by JT 11 Feb '17

11 Feb '17

I downloaded 0.92 Beta2 source code before Xmas, and tried to build it on mac mini running OSX 10.11 using cake and clang. At that stage the cake files were obviously unfinished (for example, there was no OSX cake file...). Also there were lots of hard-coded directories in the cake files, which are implicitly non-portable. Can I suggest/ask that someone familiar with Inkscape and its cake files, try to add FreeBSD support: 1) It would be good have a FreeBSD build for its own sake. 2) It is easier to spin up a VM for FreeBSD for building and testing, than for OSX. 3) Having two slightly different posix build/cake configs will help separate "Linux" from "Posix" config switches. Which will make it easier to then add third config switch for OSX. 4) FreeBSD kernel is closer to OSX Darwin kernel (both BSD family) but is a different platform, so it may shake out some issues on its own. The result will be a more portable code base, which will be make it easier for OSX developers less familiar with Inkscape to help. regards, -JT PS Im travelling at present, and the connection is poor, so I dont want to clone a git repo; but I do have Xcode on my mb-air.

1 0

Fwd: Participating in Outreachy
by Bryce Harrington 08 Feb '17

08 Feb '17

----- Forwarded message from Karen Sandler <karen@...3057...> ----- Date: Tue, 07 Feb 2017 21:10:41 -0500 From: Karen Sandler <karen@...3057...> To: project-reps@...3057... Subject: Participating in Outreachy Reply-To: karen@...3057... Hi Project Reps! The Outreachy program[1] (which is also a Conservancy member project) is working on its next round, set to open on February 16. If you are interested in participating as an "organization", now's a good time to get started[2]! The sooner your project is listed, the more likely you'll get strong applicants. best, karen [1]http://outreachy.org [2]https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs#Requirements_for_Organ… ----- End forwarded message -----

1 0

360 Total Security
by jelle 07 Feb '17

07 Feb '17

360 Total Security That you've never heard of this virus scanner is not that strange. However it has an installed base on 99.99999999% (my estimate) of all windows PCś in China. The only PCś that I know without it are those I laid my hands on. We're talking about every windows installation in China, 64 and 32 bit. That these guys managed to report anything on launchpad is a small miracle and shows their persistence. Now of course that entails only about 700 Million PC's in the country, so hardly a popular browser. That said, I wouldn't be surprised if someone dropped a big red envelope on Qihoo (the company) to make this happen or someone asked his uncle Wu for a favor. In any case I would recommend any user of 360 to remove the software (virtually impossible b.t.w. it acts like a virus once installed. I tend to boot into Linux to clean up the crap, then have to purge registry manually taking care not to remove another thingy called 360 that will bork the machine if removed.) Qihoo takes care of a steady stream of virus that will be found by their scanner and doesn't find anything really dangerous. Is total nonsense but will do some nice keyboard logging, sends data to 3rd parties and makes lots of ads pop up while you're watching movies. Oh,.. I believe DNS poisoning is also one its tricks. This is standard practice for 'free software' in China, so letś not make too much of it. It adds to the overall surveillance of subversive terminology here. No doubt it is one of the reasons you've never heard of it as only an idiot will install it voluntarily. In any case it might be worthwhile to contact those rogues at Qihoo and ask kindly whether their software is corrupt or someone in the blacklist department has bought a new car lately. On the other hand I cannot exclude a man in the middle attack or the people downloading Inkscape from a 3rd party website as that is a common way of getting software for free. Whether that is Illustrator or Inkscape doesn't really matter. The reason being mainly that any software downloaded from outside China is prone to package loss due to latency. The fact that Inkscape is on their radar at all is quite impressive. 90% of all software here is pirated and the rest is for free except for the government installed windows and whatever comes with high end brands pre-installed. I have never been able to access launchpad before I was given special access by Maren some year ago. If they did they must have had the patience of Job to do so. BTW, as one of my Yahoo accounts was hacked I lost that access. > Relevant bug report (I don't know if this was one of thetwo reports): > https://bugs.launchpad.net/inkscape/+bug/1658812 > If you want feel free to contact them (I didn't know that Virusscanner > either and I doubt it's that popular, so I didn't bother to take action > in the first place). > Regards, > Eduard Just about anyone in China, except the 1 million expats. Cheers, Jelle

4 3

[UX] Font sIze and line height
by Jabier Arraiza 07 Feb '17

07 Feb '17

Hi all. Im getting feedback about how complex is use new UX for font size and line height. Is very dificult to some users, myself for example, use and undertand well the new features. So become a cracy war in each new document. I have three ideas on mind: 1.- Force in each new document line height units be unitless, as previous inkscape. 2.- Double GUI seleced by prefs: First and default mimic previous inkscape values and positions and the other for advanced users. I hope not open too much the pandora-box Cheers, Jabier.

3 3

false positive virus on 0.92 Windows 64-bit, exe installer
by brynn 07 Feb '17

07 Feb '17

Hi Friends, We've had 2 separate reports now (at Inkscape Community), on 0.92 for Windows, 64-bit, exe installer, of a false positive for a virus. Both users are using a security program called 360 Total Security. Should we try and contact them so they can fix it? Just from a quick search, it looks like it might be a fairly popular program (although I had never heard of it before). And 2 reports are just 2 who bothered to report it. It's easy to imagine there must be people who didn't report, and just didn't install it. Thanks, brynn

2 2

UX help
by Máirín Duffy 07 Feb '17

07 Feb '17

Hi everybody, I've been using Inkscape and sodipodi before it for maybe 12 years now; it's my primary design tool. I'm a UX designer for Red Hat and specialize in mocking up page/screen designs for new features and modifications, drafting text for user interfaces, as well as user testing and feedback. I noticed some of the comments about the 0.92 release text height issueand the critique of the dialog that pops up in 0.92 about old Inkscape files. I would just like to offer my services any time you might need advice or help in figuring out how to design such dialogs or handle various conditions like this. I'm mizmo on freenode or you can email me. Please consider me a resource you can tap anytime for this; I don't code but I'm always happy to helpwhether it's some quick advice or something more involved like mockups. Cheers, ~m

15 48

Strict builds
by Alex Valavanis 07 Feb '17

07 Feb '17

Hi All, I've added a new "Strict" build type to CMake. This is designed to fail if any deprecated symbols are used in the main Inkscape code. To use it, just enter "Strict" in the CMAKE_BUILD_TYPE field in ccmake and then reconfigure. Best wishes, Alex

1 0

Inkscape 0.92.1pre1 now available
by Bryce Harrington 04 Feb '17

04 Feb '17

This is a pre-release for the upcoming stable bugfix release 0.92.1. Download it at: https://inkscape.org/en/download/development-versions The release is: 0.92.1pre1 Source Tarball Bzip https://inkscape.org/en/gallery/item/10650/inkscape-0.92.1pre1.tar_TMk7wbg.… String Freeze is now in effect, as well as Hard Freeze. This means no changes will be taken that change any translatable strings. Bug fix patches will still be considered, but only if they're completely safe; patches should be extremely minimal, reviewed by more than one person, and well-tested. Nothing that looks even slightly risky, uncertain, or unfinished please, but I'll consider on a case by case basis, so give me a ping to take a look. == Translations == With String Freeze in effect, no string changes in code are permitted and translations can now be completed. Please finalize your work prior to Monday, Feb 13th. == Future Releases == It's my fault we're running about a week past-schedule (I was trying to fit the dpi dialog work in before the cutoff, but that patch needs a bit more attention.) So I'd like to bump the schedule back by one week to make up for it: Proposed Timing: Original New Date √ Mon Jan 2 Feature Freeze √ 0.92.1pre0 Mon Jan 23 Hard Freeze √ 0.92.1pre1 Mon Jan 30 Fri Feb 3 String Freeze 0.92.1pre2 Mon Feb 6 Mon Feb 13 Release Candidate 0.92.1 Fri Feb 10 Fri Feb 17 Cut Release Mon Feb 13 Mon Feb 20 Announcement Looking forward, point releases on the 0.92.x branch will continue onward, including after we've migrated to git. I am thinking a cadence of a couple months per point release seems to be about the right balance of time, so that'd put 0.92.2 in the April timeframe and 0.92.3 out around July. Further forward, we discussed 0.93 a bit today. I know there's lots of work still to be done to get trunk to a releasable state. I would like to start gathering status on it, to get a better feel for about when we can start planning the release. I'll be posting more about this later, but for now if you have work in process in trunk, I'd love to hear of your plans. Thanks, Bryce

1 0

GSoC Text Help (you don't need to be a developer to help with this)
by Josh Andler 04 Feb '17

04 Feb '17

Hey All, So, I'm looking to complete the application for this year's GSoC (Google Summer of Code, for those unfamiliar). Unlike previous years, they actually want our application hosted with them as opposed to a link to what we want in our wiki. It supports markdown, which is awesome, but when I go to pull what we have and put it in a text editor that counts characters, we're at 2035 characters when we need to be at 1500. Again, this is with the relevant markup which unfortunately counts against us. The source I speak of (for those with a wiki account is): http://wiki.inkscape.org/wiki/index.php?title=SOC_Application_Template&acti… Is there anyone with the time and inclination to help keep the substance while cutting down on the fat? (It looks lean to me as a start, but as you can tell by this email, brevity isn't normally a strong point for me) Our application needs to be complete by the 9th and this is one piece of it that I could really use a hand on due to my obligations for SCALE which are overlapping right now. I don't know that the main text itself that we host needs to be cut down as much as we should start a second copy that is intended for brevity, with shorturls and all that to help too. Any volunteers? Cheers, Josh

4 5

Inkscape Board Meeting + Release Meeting Feb 3rd
by Bryce Harrington 04 Feb '17

04 Feb '17

== Board Meeting == Already time for another board meeting. Come join us Friday, Feb 3rd at noon Pacific in #inkscape-devel. Any community member is welcome to attend! http://wiki.inkscape.org/wiki/index.php/Board_Meetings Agenda: + Inkscape Forum status - Update on receipt of forum data - Update on OSUOSL hosting provisioning + Inkscape gitlab - experience so far - self-hosting feasibility? + Inkscape Website disk space + Merchandise sales + Sponsorship levels followup == Release Meeting == Agenda: + 0.92.1 release status + (Help needed) writing release notes + Promotion/advocacy team recruitment + kickoff

1 1

Re: [Inkscape-devel] Inkscape 0.92 via homebew on macOS
by Julian Rendell 04 Feb '17

04 Feb '17

Dipping my toes into the inkscape-devel list. I think there’s need for an “official” MacOS build for Inkscape. e.g. this message: https://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/9B4B6CD283… There are a few non-core(???) developers/advanced users trying to get MacOS packaging working again; both on this thread and e.g. https://sourceforge.net/p/inkscape/mailman/message/35584561/ (There’s a great gist with a working procedure, including patches linked in Atsuyoshi’s post: https://gist.github.com/atuyosi/ab5499a176b0b456bca98c44e2775cbb) Question for core team: If the packaging is figured out, does the Inkscape team have the resources to create and publish a Mac binary that can be hosted the same as the Windows/Linux builds? (I’m not sure what the CI/build infrastructure is for Inkscape.) Extra: could the builds be signed so that they don’t raise security warnings? For Kirk, Tim, Brynn, Windell, Chris, Lyndsy, Atsuyoshi- do you want to work together to try and solve this? I’m most comfortable with git/github, and a quick google reveals there are some git to/from bzr tools (e.g. https://github.com/felipec/git-remote-bzr) My suggestion would be to setup a git repo/project and manually pull in the latest 0.92 branch. Then pull in Atsuyoshi’s work, get it working locally, then in CI (travis?) In the interim, packages could be hosted as releases on the GitHub project page; hopefully the Inkscape project would be able to eventually pick up this work and make the github repo obsolete. (I’d suggest deleting the github repo at that point. No need for historic projects to add to user confusion ;-) ) I’m also happy to see it hosted elsewhere. Let me know if you’d be interested in this and I’ll set up a repo/try to participate in figuring out the patches. Thanks everyone! Julian

7 16

Fw: The results of your email commands
by Niraj Dave 03 Feb '17

03 Feb '17

I have windows 7 32 bit operating systems and installed all the required software as per below guideline: Show original message http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows I have some problems when I generate makefiles: Looking for fpsetmask - not foundLooking for gtk_window_set_default_icon_from_file - not foundLooking for include file ieeefp.h - not foundPerforming Test HAVE_STRUCT_MALLINFO_FORDBLKS - FailedPerforming Test HAVE_STRUCT_MALLINFO_FSMBLKS - FailedPerforming Test HAVE_STRUCT_MALLINFO_HBLKHD - FailedPerforming Test HAVE_STRUCT_MALLINFO_UORDBLKS - FailedPerforming Test HAVE_STRUCT_MALLINFO_USMBLKS - FailedLooking for include file sys/filio.h - not foundLooking for C++ include unordered_set - not found etc... How to resolve this error Thanks with regards Niraj Dave

2 6

Inkscape 0.92.1pre0 source tarball
by Bryce Harrington 02 Feb '17

02 Feb '17

This is a pre-release for the upcoming stable bugfix release 0.92.1. Download it at: https://inkscape.org/en/download/development-versions The release is: 0.92.1pre0 Source Tarball Bzip https://inkscape.org/en/gallery/item/10613/inkscape-0.92.1pre0.tar.bz2 Hard Freeze is now in effect. Do not land any code changes on the 0.92.x branch without release manager approval. In particular, I would prefer to see only critically important fixes, or carefully reviewed refinements of fixes recently landed, and leave the rest to 0.92.2, but I'll consider all proposals on a case by case basis, just give me a ping. == Translations == Next Monday will mark String Freeze. Between now and then, string changes in code are permitted, but due to Hard Freeze there will probably be few. Thus I encourage translators to start updating translations at this time, with a plan to finalize next week. == Packaging == Packagers for Linux and Windows should use this source tarball for creating test packages, and upload to the website. == Future Releases == The 0.92.1pre1 pre-release will be in one week's time. I plan to try to stick pretty strictly to the previously announced release schedule, but of course release delays may be necessary depending on testing. A subsequent 0.92.2 release will be planned for 1-2 months after 0.92.1's release, so some sort of April timeframe seems likely. Thanks, Bryce

3 5

[RFC] gitlab migration plan
by Bryce Harrington 02 Feb '17

02 Feb '17

Thank you everyone for considering the options and rasing good points and concerns, including: * Gaining contributors is a motivation here * Performance might be problematic with gitlab * FOSS options fit Inkscape values, and we should prefer to support FOSS projects, but not if it inhibits us too badly * Other choices do exist besides just github vs. gitlab A lot of people are voicing preference for gitlab, perhaps a majority, but we're certainly not at a full consensus. I sense that we need some actual experience under our belts, and we should plan to reassess our decision as we get into it. Performance is, at least, something we can test. If gitlab has severe performance issues, then that should be obvious and likely measurable if we just try it. Github certainly would give us more visibility, however there's no guarantee this would translate into more contributors. Will Entriken made a good point that being on github would enable more drive-by contributions based on general experience in various small/medium projects, however Mc makes a strong counter-argument that what we are really after are dedicated contributors, and with Inkscape already having a fairly widespread profile those folks will find us just fine regardless of the popularity of the hosting platform. Perhaps a separate outreach effort to recruit contributors after the git migration has been done would be more likely to generate good results? So given the above, I'd like to propose a migration to githab but with several checkpoints, according to the following plan: 1. Migrate inkscape_web. + Keep a particular eye on performance. + Evaluate code review UX + Evaluate CI + Experiment with other features 2, Once 0.92.1 is released, we'll have a first checkpoint Checkpoint for inkscape_web. + Make recommendations for utilization of code review, CI, and other gitlab functionality. + Was performance a hinderance? Is the user experience acceptable? In general do the inkscape_web participants still feel as supportive of gitlab? + What concerns or issues remain, that should be watched during our initial migration? + We'll ask everyone involved in inkscape_web for a thumb's up or down. If there are thumb's down, we'll halt and re-evaluate. 3. Migrate inkscape to gitlab. + All bzr committers are eligible for gitlab commit access, but will need to place a request for access + At least one dry run should be done, to ensure that revision history, branches, tags, etc. are successfully converted. + Issues encountered with gitlab will be recorded, either in a dedicated bug tracker or just a simple 'complaints' web page. + Transition of wiki pages can start as desired (see separate plan proposal). + Bugs stay on LP for now 4. Outreach effort to bring in contributors + Leverage our release marketing procedures and contacts + Coordinate with GSoC, releases, hackfests + Ensure we have reviewers/mentors on hand 5. Following the 0.93.0 release is a second checkpoint. + Review the recorded issues encountered. Collect further feedback. + How has use of gitlab affected contribution levels to the Inkscape codebase? If contribution levels have not grown then we need to reassess. + All active users of the service are asked to give thumbs up/down on their experience using gitlab. If most everyone gives thumb's up, we will proceed and stick with gitlab at least until 1.0.0. Otherwise, we need to re-evaluate our plans. + Plan follow-on work to investigate/address top issues. 6. Following the 1.0.0 release, we have another reassessment of all project technologies and services. cmake, git, gitlab, C++11, gtk3, and so on. We should then plan transitions from those to whatever is next, over the course of several 1.x releases. If you've read this far - thanks! Feedback is most appreciated. Bryce

5 9