January 2017 - Inkscape Devel

Google Summer of Code 2017 - Mentors?
by Josh Andler 24 Jan '17

24 Jan '17

Hey All, The Org application period is currently open. We've had a couple potential students already reach out. Given those two things, who is willing and able to Mentor for our organization this year? I'm willing to Admin as usual, hence my bringing this up. Cheers, Josh

3 2

Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug
by C R 24 Jan '17

24 Jan '17

Sounds great to me! I'll read over what we have as well again this weekend and put some thought into the content and graphics, taking into account all suggestions made here. I think a bit of humour would be great to convey a friendly and fun atmosphere to welcome contributors while not being too cheesy. :) -C On 24 Jan 2017 6:03 a.m., "brynn" <brynn@...3133...> wrote: I think that's a brilliant idea. You're right that we have written bits > along these lines in the past, which could be extracted, dusted off, and polished to be more digestible to a more modern audience. You're right that there's probably a few different "types" of people so maybe a few different pages to message in different ways would make sense. I.e. one that talks to people who could get into coding work might focus on explaining branches and patch contributions, whereas another page might come from the angle of someone who isn't AT ALL interested in coding and instead just address good non-coding ways to contribute. Another one geared for translators, another maybe for evangelists, yet another specifically focused on usability testing. Or something like that. Would you like to take a shot at extracting the existing text and roughing it into a more useful shape? I think I could contribute verbage to the pages, or link in someone to help. Bryce __________________________________________________ Yeah sure, as long as we're waiting for OSUOSL, I have time to spare. I'll have to look in the FAQ to see what's left still there. Because now that I think of it, a lot of it has been brought to the Contribute page already, and some on the Promote page. https://inkscape.org/en/contribute/ https://inkscape.org/en/contribute/promote/ Should we split those sections up, and add more to them? I think what might be missing, to address this concern, is language that perhaps is more inviting (and maybe more warm and fuzzy?) as opposed to strictly informational. I know we had a report recently, where someone thought the info about helping with the website should be on the Contribute page, rather than Promote. I originally put it on Promote, because I was thinking that's what the website does, is promote Inkscape. Plus, it made a way to break into 2 pages evenly, while all on the same page, it's too long. Anyway, maybe there's a better way to organize all that? Ok, the only thing left in the FAQ is this: https://inkscape.org/en/learn/faq/#how-communicate-effective ly-throughout-inkscape-community-and-avoid-causing-flamewar which I deliberately left there, thinking it should probably be deleted, but not wanting to make that decision alone. I think we can definitely use that first paragraph. And maybe some other parts too? Since we have the CoC, we can probably lose the flamewar part. Hhmm....I'm thinking of an introduction to the Contribute page, which contains most of that info. Section title "So, You Want to Contribute to Inkscape? Here's how to get started" More warm and fuzzy, but maybe too corny? C R, jump in with comments too :-) All best, brynn PS - another thought - Maybe the CoC could have some language for bringing new people in without saying "patches welcome"? -----Original Message----- From: Bryce Harrington Sent: Sunday, January 22, 2017 7:51 PM To: brynn Cc: C R ; inkscape-devel Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug On Sun, Jan 22, 2017 at 08:50:49AM -0700, brynn wrote: > >"Patches welcome" has become a flippant and dismissive way to say, > >"well, fix it yourself". > > Most of my experience helping Inkscape users is in forums (approx 8 > years), as opposed to the mailing list (approx 2 or 3 years). I've > never seen this suggested in a flippant or dismissive way. > > I could see a webpage....or a section of a webpage, which has kind > of a pitch or invitation. Without looking, I don't remember > specifics, but I think parts of the faq (user faq on the website) > already do this. So it could be made into a page or section of a > page. Since people have all different kind of issues, we couldn't > provide the support info. But it could include generalized support > info, along with everything else I mentioned above. And then when > we find ourselves thinking "patches welcome", we could link to it, > rather than type it all out, every time. > > Or would that be too impersonal? If the Inkscape project is known > for being a friendly community (as someone said earlier) it could be > written in sort of a warm, fuzzy way.....if that would help? Just a > thought :-) > I think that's a brilliant idea. You're right that we have written bits along these lines in the past, which could be extracted, dusted off, and polished to be more digestible to a more modern audience. You're right that there's probably a few different "types" of people so maybe a few different pages to message in different ways would make sense. I.e. one that talks to people who could get into coding work might focus on explaining branches and patch contributions, whereas another page might come from the angle of someone who isn't AT ALL interested in coding and instead just address good non-coding ways to contribute. Another one geared for translators, another maybe for evangelists, yet another specifically focused on usability testing. Or something like that. Would you like to take a shot at extracting the existing text and roughing it into a more useful shape? I think I could contribute verbage to the pages, or link in someone to help. Bryce

1 0

Re: [Inkscape-devel] Inkscape 0.92 Portable version ?
by Gord Caswell 20 Jan '17

20 Jan '17

On 18 January 2017 at 16:47, Bryce Harrington <bryce@...961...> wrote: > > > Between this, and Eduard's request for help, I'm building it right now. > > Great, thanks for tending to it. > We've built & digitally signed the portable package, ready for upload: http://download2.portableapps.com/portableapps/inkscapeportable/InkscapePor… SHA1: 9f949bf3b77f4d529673ff43d597e7827b3b327b Gord PortableApps.com

1 0

Move Wiki to Git*b
by Martin Owens 20 Jan '17

20 Jan '17

Dear developers and wiki enthusiasts, Our current wiki hosted on wiki.inkscape.org is doing ok, but is running on an old machine that the hosting provider OSUOSL would like to retire if at all possible. Since we are moving to Git*b, this is an opportunity to also move the wiki to that service. This decreases our system-admin burden and the resources we ask from osuosl. It would also say that our wiki is more of a developer/contributor focused effort, leaving user content to the website. I expect things like hackfest planning and other plumbing to continue to use a wiki system. The process of moving it would entail waiting until our code is on git*b and then convert each of the existing pages from MediaWiki syntax to Markdown syntax. A script such as this https://bitbucket.org/wikier/mw2md could be used, but testing would be needed to see what kind of output we got. For all people involved in using and editing the wiki, I'd like your thoughts on how we should manage our wiki service going forwards. Thank you all. Best Regards, Martin Owens Website Administrator Hat

9 18

Mesh Gradients Polyfill
by Jayesh Salvi 19 Jan '17

19 Jan '17

Hello, I've implemented Javascript polyfill for SVG files that have mesh gradients in them, so that they can be rendered in browsers successfully. I ported the mesh gradient rendering code from Cairo to javascript in order to do so. The code and instructions on how to use it are available at https://github.com/zectorio/mesh-gradient-js This code could be run on SVG files created in inkscape and make them renderable in browser. Please take a look. I'm looking forward to your feedback. (There are still some rough edges, as this is still a proof-of-concept thing. But the code works for examples in samples directory) Thanks, -- Jayesh

4 4

Inkscape 0.92 Portable version ?
by Marc Jeanmougin 19 Jan '17

19 Jan '17

Hi all, For previous releases, we used to ship a portable version with portableapps, but there does not seem to be such a version for 0.92. Is it an oversight? I don't know who took care of those in the past. If no one is planning to do it, we had a portableapps developer on #inkscape-devel offering to build it Thanks, -- Marc

6 7

Todays trunk : some objects lacking after reloading files
by ivan louette 18 Jan '17

18 Jan '17

Hi That's one of the the most spectacular regression I never saw in trunk : today after reloading some of my files created with yesterdays trunk version some rectangles and even some text blocks are lacking ! Of course I didn't save these files again with the new version ;-) I work with Trunk on Kubuntu 14.04 ivan

1 0

extensions handling user-units and query-all in 0.92
by Pelle Nilsson 17 Jan '17

17 Jan '17

Hi, I just joined this list because after asking about extensions and handling of dpi etc in 0.92 on the Inkscape forums and on Launchpad I got several recommendations to bring it up with you developers here instead. (I should probably have lurked here a long time to keep updated about changes happening to Inkscape before major releases. My extensions have been online since 2008.) Either I am confused about how user-units are supposed to work (and my extension is even more confused) or there is a bug in Inkscape (possibly in inkex.py?). http://www.inkscapeforum.com/viewtopic.php?f=29&t=31525 https://answers.launchpad.net/inkscape/+question/431543 https://bugs.launchpad.net/inkscape/+bug/1654907 https://www.boardgamegeek.com/thread/299033/inkscape-extensions-boardgame-d… For testing I created a rectangle in 0.91, a 1x1-inch square at -3 inches x (I only bother with the x-coordinates in the following). Inkscape UI reports that it is at -270px. If I transform it by translate(270) it ends up at x=0, as expected. It also works in 0.92. Inkscape UI now reports -288px, but still a translate(270) works as expected, so Inkscape internally correctly understands that the user-unit in this document is 1/90 inches (I confirmed by calculating svg width and viewBox that it is indeed that). But the countersheetsextension running in 0.92 on a document from 0.91 gets confused and translates things too far. If the document was created in 0.92 it works (user-units for an A4 for instance being 1mm, and it translates properly). The extension works by reading coordinates using --query-all, and I had to make a small change to even support 0.92-documents in 0.92 (see https://github.com/lifelike/countersheetsextension/commit/aa454f5117fbd457d…), but this fails on a document created in 0.91. The calculations, done using unittouu, ends up with values as if the user-units were 1/96 inches, so in the example above the extension outputs translate(288), and the rectangle is translated 18 units too far to the right. So what I think is going on is that inkex.unittouu fails to properly calculate coordinates in user-units if they do not match some of the pre-defined values, but Inkscape internally does a better job? Trying to figure out a work-around. Perhaps write my own function to calculate user-units instead of using unittouu, or somehow detecting that the document was created using 0.91 (although I guess it will still fail for documents with any other possible user-unit lengths that might exist out there?)? Or maybe I just use the API in inkex the wrong way and what I try to do should already be possible? -- /Pelle

1 0

Independente Inkscape Survey Results
by Victor Westmann 16 Jan '17

16 Jan '17

I said previously that I would publish the results on January 31st but I believe there's no need to wait that much since the answers in the survey are the same for a couple of weeks now. So, attached, is the result of the survey. If anyone needs access anything else let me know. A nice insight we can have reading the survey is that a big part of the Inkscape Community is willing to contribute to the software with $$ to foster a number of different developments. Which is great! ;-) Happy new year! --Victor Westmann

3 4

Getting to git
by Bryce Harrington 14 Jan '17

14 Jan '17

"The time has come," the Walrus said, "To talk of many things: Of shoes — and ships — and sealing-wax— Of cabbages — and kings — And why the sea is boiling hot— And whether Inkscape should switch to gitlab or github or entirely other things." At Hackfest 2015 we broached the topic of moving to git, and while recognizing it as probably inevitable, decided to take care of a few other things like switching to cmake first, and getting a release out the door, and getting going with Gtk3 and C++-11. That release is out the door, cmake is done, Gtk3 is landed in trunk, C++-11 work is under way, and so I think it's time we start on tackling git. When we last visited this discussion, there was a consensus that yes we should move to git, and that rather than self-hosting a plain git repo (ala freedesktop), we would be better to look at an integrated platform like github or gitlab. But there was not a consensus as to which of those two to pick. So the task at hand is to discuss and deliberate the two and decide which should be our focus. Both have interesting pros and cons, and I don't think the decision is clear cut. Where should we go? In github's favor is that it holds the greater mindshare. Where we to go with it we'd potentially tap into a larger community of developers, which potentially could translate into a greater level of new participation in the project. github also seems like it's received a greater amount of polish and has some feature advantages (github's CI was seen as a huge pro last time we looked). gitlab is an up-and-comer and is actively acquiring analogous features to github. A big pro for us is that gitlab is FOSS whereas gitlab is free but proprietary. With gitlab we'd also hold the option of self-hosting, which might not matter or might be a huge advantage, it's hard to say. Both services provide broadly similar functionality and user experiences. The differences between them will be small compared with the differences we'll be facing moving from bzr+launchpad. Also, migration from github to gitlab or vice versa if we change our minds doesn't look like it'd be all that difficult. Those may be the best two options but they're not the only ones we have. There's other services, and of course git can be used serverside all on its own purely as commandline, or with cgit to provide a minimal web service. -- faqs ------------------------------------------------------------------- Why the need to move from bzr? One of the reasons why we switched from svn to bzr rather than git was because it was easier to learn; these days so many people know git and don't know bzr (and probably don't care to learn bzr) that this isn't quite such an advantage any more. git is also more actively maintained than bzr, and has a far bigger ecosystem of tutorials, tools and services. We also liked the integration between bzr and the LP bug tracker -- we'll lose this, although github/gitlab provide different integration opportunities that might compensate a bit. What services would we move? What we've discussed in the past is to keep the migration limited to VCS, branch management, and code review. The issue tracking in github/gitlab is quite different from what we've grown accustomed to in LP so changing that might be too much disruption. bzr->git is the main thing we're concerned with; transition of other services can be handled on a case by case basis. How would we undertake the transition? suv made a good point today that migration of smaller codebases first can be helpful so that the learning curve can be digested in pieces rather than in one big go. So perhaps we should begin by moving some of our more peripheral bzr repos, then maybe things like the website and then 2geom, and then do inkscape last. What about people who don't yet know git? I suspect a lot of us either already know git or have been working on learning it, that this isn't an issue. However, this transition is important enough I'd be willing to propose to the board that we fund book purchases and/or other forms of training for members that might need it. When would the transition be done? We've done some initial experimentation already. I would propose as soon as we have a strong consensus for github or gitlab that we proceed with moving the board's repository, inkscape-docs, and any other small / lesser-used repositories still relevant to Inkscape. Then second in perhaps a few months migrate inkscape-web and 2geom over. Once those are complete then migrate the inkscape repository itself over, with the goal of having the migration done. I'd like to see the transition completed prior to when we start getting heavily into the 0.93 release. Let me know your thoughts, and help us drive towards a consensus for github or gitlab. Thanks, Bryce

12 28