- Inkscape Devel - Inkscape Mailman

Git Rebasing
by Martin Owens 29 Jan '17

29 Jan '17

Hi Developers, Just a heads up. I rebased the inkscape-web git repository on GitLab to sort out problems with it's cherry picks. This took 2 hours of picking through the rebasing as some of it could be automated. So I had to manually merge about two hundred of the 1600 commits to get it working. Not sure if this will bite the inkscape git repository some time in the future. But being aware of the non-linear repository created by a migration from bzr. Best Regards, Martin Owens

5 13

Fw: Lack of mac installer
by brynn 29 Jan '17

29 Jan '17

I received the original message (at the bottom) through the Contact form on Inkscape Community. Forwarding along to the list. You can see I suggested to subscribe to the list. But as of now, he isn't a subscribed. I didn't know exactly what to say about the change to depending on Macports, so hopefully you all can be more helpful. brynn -----Original Message----- From: admin@...3472... Sent: Sunday, January 29, 2017 6:42 AM To: kirk@...3473... Subject: Re: Lack of mac installer Hi Kirk, Wow, that's a fantastic offer! You've actually reached a forum which is only temporarily the official Inkscape forum, while we are working on getting the new official forum working. And for some reason which I find odd, Inkscape developers don't use bb style forums. Since I'm not a Mac user, I haven't paid very close attention to why they switched to Macports. But judging by all the complaints we've had about people trying to use Macports, maybe it would be good to have the DMG version. You'll want to subscribe to the developer's mailing list (https://inkscape.org/en/community/mailing-lists/), which is where this kind of issue is discussed and handled. I could go ahead and forward this to the list, so the people who need to know will see it. You won't be able to post to the list, until you subscribe. But you'll get any replies. And you can follow any discussion which might happen after I forward this, in the archives. The link to the archives is right beside the link to subscribe, on the page above. Actually, developers are about to release 0.92.1, so this could be good timing! Thanks for your generous offer, and I'll send this right along to the people who can answer your questions. All best, brynn -----Original Message----- From: kirk@...3473... Sent: Saturday, January 28, 2017 5:40 AM To: admin@...3472... Subject: Lack of mac installer Contact Page Form for Inkscape Community Name: Kirk Email: kirk@...3473... IP: 209.131.239.35 Message: Do you lack someone to create a dmg installer of v .92? Is that why macports is being used? I'm a mac guy and so understand why so many people have issues with macports. I'm not an expert but would like to volunteer my services to get this version created into a .dmg installer.

2 1

0.92.1 plan
by Bryce Harrington 29 Jan '17

29 Jan '17

The 0.92.x stable branch is reopened for changes. Consider it as under feature freeze but not string freeze. Bugfixes are welcome to be added. Please continue to check with me before landing things, but for the next few weeks I expect to be in rubber stamp mode and approve most anything that looks sensible. We do need to be cautious about not introducing regressions at this point. Write good changelog messages explaining the fixes in good detail please. Translation updates (and entirely new translations) are fine to land directly, no need to check with me. There are already a handful on the branch already that unfortunately came in just after I had cut the tarball. Extension updates and new extensions are probably low enough regression risk that I'll try to be liberal in approving them. The ones we have to be cautious about are the highly used extensions, since we risk breaking people's workflow. A few specifics I'm aware of, that sound worth including: + Tutorials and other .svg files we ship have the dpi scaling issue, and need updated for 0.92.1 + suv mentioned an extension to provide users a workaround to some line spacing issues, iirc. + A mechanism to backup / reset prefs settings + Fixes to some strings that were found post-string freeze + A gpl3 widget needs removed (or relicensed) I'd like to avoid maintaining a bugs-needing-fixed list, but rather focus time more on patch review and testing. I figure the important thing is to get 0.92.1 out in a timely manner, and if there's still bugs needing attention we can always do a 0.92.2 some time later on. Proposed Timing: Mon Jan 2 Feature Freeze 0.92.1pre0 Mon Jan 23 Hard Freeze 0.92.1pre1 Mon Jan 30 String Freeze 0.92.1pre2 Mon Feb 6 Release Candidate 0.92.1 Fri Feb 10 Cut Release Mon Feb 13 Announcement I know we've not got a strong history of staying to schedule, but I'm going to try hard to hit these dates at least within a day or so. That means we'll have to be strict about string changes after String Freeze, and strict about any changes after the Release Candidate. This schedule allows the weekend of Feb 11-12 for prepping website changes, finalizing packages, and so on. Anything you can think of missing from this plan? Bryce

4 6

Setting extension parameter defaults from svg objects
by Trever L. Adams 27 Jan '17

27 Jan '17

I am working with an already existing extension. One of my frustrations is that it remembers the last use. The extension sets values on the svg path directly. Is there a way that the params defined in the .inx file can be loaded from those same values? Thank you. Trever

2 1

Downloads Downtime
by Martin Owens 26 Jan '17

26 Jan '17

Dear Developers, Last night at 3:22am GMT the newly fixed web server ran it's cron jobs that had not run since November. It ran the automatic updater script, which pulled in new additions to the website without migrating the database. The database table for resources was then lacking a new "owner" string field and requests to downloads failed with an Error 500. The issue was corrected with a complete database migration at 7:42am EST and the website is working within it's known parameters. Between the issue starting and the fix, there were 241 error emails sent from the web server for 44,183 actual 500 errors. (Emails are paced). Blocking 13,228 attempts to download inkscape for windows file, 6,295 attempts at an msi file and 15,937 attempts at the portable inkscape download. >From users themselves, there were 42 emails to the website administrator. 38 in English, 2 in French, 1 in Portuguese, 1 in Indonesian and 1 from Donald Duck. 40 apologetic emails were sent back to real addresses, and two emails not sent to fake reply addresses. Best regards, Martin Owens

1 0

Trunk build broken (test case involving document-rotation)
by Bryce Harrington 25 Jan '17

25 Jan '17

[==========] Running 4 tests from 1 test case. [----------] Global test environment set-up. [----------] 4 tests from AttributesTest [ RUN ] AttributesTest.SupportedKnown [ OK ] AttributesTest.SupportedKnown (2 ms) [ RUN ] AttributesTest.NameRoundTrip [ OK ] AttributesTest.NameRoundTrip (1 ms) [ RUN ] AttributesTest.ValuesAreKnown /<<BUILDDIR>>/inkscape-trunk-0.92.0+devel+15444+85~ubuntu16.10.1/testfiles/src/attributes-test.cpp:613: Failure Value of: ids[i] > 0 Actual: false Expected: true Attribute string with enum 59 {inkscape:document-rotation} not handled [ FAILED ] AttributesTest.ValuesAreKnown (4 ms) [ RUN ] AttributesTest.ValuesUnique [ OK ] AttributesTest.ValuesUnique (2 ms) [----------] 4 tests from AttributesTest (9 ms total) [----------] Global test environment tear-down [==========] 4 tests from 1 test case ran. (9 ms total) [ PASSED ] 3 tests. [ FAILED ] 1 test, listed below: [ FAILED ] AttributesTest.ValuesAreKnown 1 FAILED TEST 3/5 Test #2: color-profile-test ............... Passed 5.74 sec 4/5 Test #3: dir-util-test .................... Passed 5.73 sec Start 5: object-set-test 5/5 Test #5: object-set-test .................. Passed 0.31 sec 80% tests passed, 1 tests failed out of 5 Total Test time (real) = 6.06 sec The following tests FAILED: 1 - attributes-test (Failed) Errors while running CTest Makefile:130: recipe for target 'test' failed ----- Forwarded message from Launchpad Buildd System <noreply@...1881...> ----- Date: Wed, 25 Jan 2017 05:27:43 -0000 From: Launchpad Buildd System <noreply@...1881...> To: Bryce Harrington <bryce@...961...> Subject: [Build #11913969] amd64 build of inkscape-trunk 1:0.92.0+devel+15444+85~ubuntu16.10.1 in ubuntu yakkety RELEASE [~inkscape.dev/ubuntu/trunk] Reply-To: Launchpad Buildd System <noreply@...1881...> * Source Package: inkscape-trunk * Version: 1:0.92.0+devel+15444+85~ubuntu16.10.1 * Architecture: amd64 * Archive: ~inkscape.dev/ubuntu/trunk * Component: main * State: Failed to build * Duration: 45 minutes * Build Log: https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk/+build/11913969/+… * Builder: https://launchpad.net/builders/lgw01-42 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of inkscape-trunk 1:0.92.0+devel+15444+85~ubuntu16.10.1 in ubuntu yakkety RELEASE https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk/+build/11913969 You are receiving this email because your team Inkscape Developers is the owner of this archive. ----- End forwarded message -----

2 2

Media Caching on Inkscape.org
by Martin Owens 25 Jan '17

25 Jan '17

Hi inkscapers, The inkscape website has been under stress recently. Higher load after the release mostly. But also a broken cron, failing logrotate, low disk space (in that order of knock on effect). I've fixed the cron, which fixes the logrotate and I've got a ticket out for increasing the disk space next Monday. The web server will be down for 30 minutes while I go through the process with OSUOSL. The load issue though was troubling me. Lots of media requests. I opened a ticket with Fastly, the very kind CDN service we use. They had a look at our logs and noticed that Fastly was asking if files had changed every 3 minutes. Which is a bit often. So I've set the expires to 30 days. This shouldn't effect any of the actual pages since it's just about the media / downloads. This is also one reason why uploads never use the same filename, appending -1 and etc to make them unique. So we shouldn't have an issue. But let me know if you spot anything odd or interesting. I'll keep monitoring. Best Regards, Martin Owens Website Administrator

1 0

Re: [Inkscape-devel] Google Summer of Code 2017 - Mentors?
by Krzysztof Kosiński 25 Jan '17

25 Jan '17

I can mentor too. On Jan 24, 2017 12:05, "Martin Owens" <doctormo@...400...> wrote: On Tue, 2017-01-24 at 10:35 -0800, Josh Andler wrote: > 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. I'm ready to do a spot of mentoring also. Thanks Josh! Martin, ------------------------------------------------------------ ------------------ 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

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