- Inkscape Devel - Inkscape Mailman

GSoC Mentoring
by Tavmjong Bah 04 Mar '17

04 Mar '17

Hi, We've been accepted to participate in this year's Google Summer of Code. We need to submit a list of mentors. If you are interested in mentoring, please reply to this email. Thanks, Tav

3 2

RSVP: Inkscape Hackfest, Portland Oregon Apr 28 - May 3, 2017
by Bryce Harrington 04 Mar '17

04 Mar '17

You're invited! We will be hosting a hackfest in Portland Oregon this spring for 5 nights. Tell me ASAP if you might be interested in joining us. We're trying something a bit different for this hackfest. We're renting a house that's been set up for business meetings, with a front unit and a rear unit. We've reserved one, and if enough people will be coming we'll grab the other as well. The event will focus on stabilization of the 0.93 branch, infrastructure development, and fundraiser planning. See the attached PDF for details, and email me offlist if you may be able to come. Bryce

1 0

gitlab migration plan
by Bryce Harrington 04 Mar '17

04 Mar '17

Thanks everyone who provided feedback on the plan to migrate to gitlab. I've updated the plan to incorporate all the feedback (see attached diff for what changed). With 0.92.1 now out the door, this seems like an opportune time to proceed with Step 2 of the migration, if no one objects? So, Martin, Maren, jazzynico, and others who have been maintaining inkscape-related products on gitlab, would you mind sharing your experiences with gitlab, and whether you recommend for or against migrating inkscape itself at this time? Bryce ------------------------------------------------------------------------ [DONE] 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? + Retrospective on the 2/1/2017 hack + loss of backups - https://www.theregister.co.uk/2017/02/01/gitlab_data_loss/ - Issue itself is bad. Transparency they showed is good. - It's been a month, have they adequately sorted things out? + Is gitlab's CI build system up to the task for Inkscape? What provisions will we need to make (e.g. supplying our own build hosts) + 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 + tweenk has a script to fix up discrepant author names and e-mails. Can't be shared publically since has personal info (but could be passed to a board member via pgp encrypt). + At least one dry run should be done, to ensure that revision history, branches, tags, etc. are successfully converted. + Functionality that uses 'bzr revno' (like the about screen) will need modified to use git. - Formatting for about screen should be something resembling: "Inkscape 0.92+devel (2017-01-18 f0e47570)" - git describe --tags --dirty will tell the last tag, whether there are changes to the checkout (the --dirty), the short hash of the last commit and also the number of commits since the tag. It's not too hard to clean up the tag name (remove "release-") and add the commit date. - Use the commit date rather than the author date + Issues encountered with gitlab will be recorded in our bug tracker with the 'gitlab-migration' tag. + 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 + Assemble an outreach/advocacy team + 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.

6 13

Using libpotrace - any easy examples ?
by Ken Moffat 03 Mar '17

03 Mar '17

Among the changes for 0.92, I saw that libpotrace was no longer shipped, and therefore an external library was needed. Therefore, for those of us who build without that external library (I'm from BLFS - Beyond Linux From Scratch) we are apparently losing functionality compared to 0.91. But proving it to my colleagues is a different matter. My searches suggested that the Paintbucket tool would no-longer work, and that that could be confirmed by drawing a box with a foreground colour to fill it. But that continued to work, so I have been unable to prove that error on our part. Meanwhile, we had other fish to fry (/me wonders if that is the right phrase for a vegetarian to use, but whatever ...). Now that I'm back to looking at upcoming things, asking a question here looks like a nice diversion from upcoming changes in other packages (particularly firefox and its reputed requirement for rust), even if I end up showing my ignorance. So: is there a *simple* series of actions which even an artistic numpty like me can do, which will work on 0.91, but which on 0.92 *without* libpotrace will fail ? Thanks. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods

2 2

is it possible to speed up CMake?
by alvinpenner 03 Mar '17

03 Mar '17

on Windows 10, current trunk, I normally execute the following two Cmake commands: mingw32-make -j 2 mingw32-make install The time required for this is 300 seconds, 150 seconds for each step. This time is the same no matter how small the change, even if I just insert one single blank character somewhere. Previously, using btool, the total time required for this would be about 10 seconds or so, for a complete rebuild of Inkscape. So CMake is about 30 times slower than btool, which makes it almost impossible to do diagnostic work with Inkscape, any way of speeding it up? Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/is-it-possible-to-speed-up-CMake-tp4979104… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

11 19

Simple Templates
by Deepti sharma 02 Mar '17

02 Mar '17

I am attaching some of the simple graphics made by using Inkscape. -- Regards Deepti Sharma Blog: https://deepti96.wordpress.com/ Github: https://github.com/dsdeeptisharma Gitlab: https://gitlab.com/u/dsdeepti "Great works are not performed by strength but by perseverance"

2 1

Re: [Inkscape-devel] is it possible to speed up CMake?
by Olof Bjarnason 01 Mar '17

01 Mar '17

On 1 Mar 2017 22:01, "alvinpenner" <penner@...1856...> wrote: >> A complete *rebuild* of Inkscape in 10 seconds using one computer only? sorry, I got carried away with my own rhetoric. I meant take an existing build, make one trivial change in one file, and rebuild. I am tracking down bugs, so I typically do many recompiles with only trivial changes between them. Ah yes. Rebuild means clean+build in my toolchain might be a little blind. Hope cmake build cycle improves with time... Alvin -- View this message in context: http://inkscape.13.x6.nabble. com/is-it-possible-to-speed-up-CMake-tp4979104p4979107.html Sent from the Inkscape - Dev mailing list archive at Nabble.com. ------------------------------------------------------------ ------------------ 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

1 0

Introduction
by Deepti sharma 01 Mar '17

01 Mar '17

Hi, I am Deepti Sharma pursuing Bachelors of Technology (B.Tech) 3rd year in CS. I love to pick challenges and this is an opportunity for me to indulge in open source community. I have worked with some of the open source communities during the time of GCI and it was a great experience for me. I have used Inkscape in past for simple graphics and now I am putting my hands into it again. I am extending my knowledge by reading about capabilities of Inkscape. Soon I will post some of the graphics I have made using Inkscape. -- Regards Deepti Sharma Blog: https://deepti96.wordpress.com/ Github: https://github.com/dsdeeptisharma Gitlab: https://gitlab.com/u/dsdeepti "Great works are not performed by strength but by perseverance"

2 1

GSOC
by Jabier Arraiza 27 Feb '17

27 Feb '17

This year I do not go to propose me as a mentor, but if anyone is interested in my proposal from last year I could co-mentor in the dark -if posibol-. Cheers, Jabier.

1 0

Re: [Inkscape-devel] Roadmap for Inkscape 0.93 on Windows - GTK3, devlibs, MSYS2 and support for Windows XP
by C R 27 Feb '17

27 Feb '17

May I suggest migrating to Ubuntu? You may actually have some luck running those older programs in WINE. Just a thought. :) Dosbox still runs my very first Pascal programs! You may also find good open source replacements for your old software too, and probably for free! Sorry to hear about your troubles with Windows 10. If you must have Windows, maybe win 7 would be better at this point. You could also try running XP in a VM in Ubuntu, then you could have your cake and eat it too. :) -C On 27 Feb 2017 11:20 a.m., "alvinpenner" <penner@...1856...> wrote: >> If they are still on XP, they can still use older builds of Inkscape. People stuck on XP must surely be used to new software not working on their old deprecated OS by now. Actually in my experience the situation is the exact opposite. Windows 10 has not offered me access to any new software that is of any interest to me. Instead it has forced me to abandon two old, legacy, pieces of software that I had used daily for about 15 years on XP, and now can no longer use because they are 16 bit software. So the switch to Windows 10 has been a significant step backwards in terms of functionality and in terms of user-friendliness. Windows 10 is incredibly unfriendly when it comes to simple things like copying files, and it is full of bugs and glitches. I upgraded to Windows 10 because I was literally forced to do so, not because I wanted to, and certainly not because it offered me anything that I was actually interested in. Alvin -- View this message in context: http://inkscape.13.x6.nabble. com/Roadmap-for-Inkscape-0-93-on-Windows-GTK3-devlibs-MSYS2- and-support-for-Windows-XP-tp4979046p4979062.html Sent from the Inkscape - Dev mailing list archive at Nabble.com. ------------------------------------------------------------ ------------------ 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

3 2