February 2017 - Inkscape Devel

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

Any progress on CMYK?
by John Culleton 02 Feb '17

02 Feb '17

My copy of the 4th edition of the Bah book says it is "under way." The absence is a pity because with the built-in perfect book layout facility Inkscape would be most useful in creating book covers. The ability to distort type faces makes for some interesting possibilities I recognize the size of the task of course. -- John Culleton Wexfordpress Book design and indexing.

2 1

Seeking Review: Inkscape Development for Users
by Martin Owens 01 Feb '17

01 Feb '17

Hi Everyone, Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development. http://grtuts.com/inkscape-development-builds/ He's asked me for advice on the details and I figure I'd throw it open to everyone. You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too. Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write) Thoughts? Best Regards, Martin Owens

5 5