February 2018 - Inkscape Devel

Google Summer of Code - 2018
by Tavmjong Bah 13 Feb '18

13 Feb '18

Hi all, Inkscape has been accepted as a mentoring organization for this year's Google Summer of Code. Students, time to develop your proposals. https://summerofcode.withgoogle.com/organizations/5174841905250304/ Tav

1 0

Variables in Inkscape
by Robert Van Den Bergh 12 Feb '18

12 Feb '18

Hey, Is it possible to create variables in Inkscape that link to a database? Kind regards, Rob

3 2

new moderation procedure?
by brynn 09 Feb '18

09 Feb '18

Hi Friends, This is something which has never been discussed. But recently we've had some images being reported by a regular member, which moderators have approved, and they remain in the gallery. In one case they reported a member. Should we contact a member who reports an image, thank them for helping, and explain our decision, why we decided not to delete the image? In this particular case, I'm thinking we may need to contact him or her, just to try and prevent more unnecessary reports. But in general, I wonder if we should take the time to explain our motivation, since the member is taking the time to help us. (Hah, for these recent reports, maybe I should try to recruit him or her as a moderator....?) Thanks for any comments :-) brynn

2 1

Update on Inkscape hosting
by Bryce Harrington 09 Feb '18

09 Feb '18

As many of you already know, we've been looking for sponsors for providing hosting for some of our ancillary services (mailing lists, wiki, forums, et al). I put out a CFP to hosting providers a few months back, and with ample help from Ryan we've received a couple good offers. I'm currently in discussion with the Software Freedom Conservancy to get the legal/administrative bits sorted out, so not everything is 100% nailed down just yet. However that's proceeded to a point that I'm starting to turn attention to the more technical end of things. To refresh your memory, here's the background statement from the CFP: """ We currently have various services hosted at a number of different locations with widely varying administrative capacities. We would like to centralize the administration of these services, such as consolidating them onto one platform. We also want room and flexibility to easily install additional services as we grow. Services high on our priority list to migrate soon include mailing lists, Mattermost, and wiki. Bug tracking, web forum and gitlab are potential secondary priorities. Our Django-based main website may also be worth consolidating at some point in the future. """ Mailing list migration will be the first focus, possibly also with some DNS services. This would finally get us off SourceForge, allowing us to close that down. After that, I'm pretty open to what comes next; we can play it by ear depending on opportunities and manpower availability. If you have something you wish to put time into setting up and/or administrating, contact me to sort out details. While in the CFP I had preferred physical hosting, the virtual hosting provided by the cloud service providers offering sponsorship to us does have some advantage in terms of flexibility - being able to spin up VMs on a per-service basis, or temporary ones for development and testing. One common industry best practice I'd like us to adopt is to switch to use of automated scripts for setting up the systems and services. I.e., using cloud-config to bootstrap the raw VMs, and then something like Ansible or Puppet to do automatic configuration management. We can then consolidate the service setup scripts in a git repository. More on this later. I've added a new "Inkscape Infrastructure" subgroup for holding this configuration management repository. This will be a sysadmin-oriented repository - i.e. more focused on the setup/administrative end, not so much on the data or code. I'll work up some policy/procedure for membership management of this group, for now I'll handle it manually. I'm also going to move our 'credentials' repository into this Inkscape Infrastructure subgroup. Last board meeting we discussed migrating the credentials git repo, so that it's not hosted as a branch of the inkscape codebase (which causes it to take a long time to checkout). So this will implement that change. Bryce

3 4

Fwd: HLC-Farbatlas
by Maren Hachmann 07 Feb '18

07 Feb '18

Hi there, Christoph has asked me to forward his message, as it didn't get through: -------- Weitergeleitete Nachricht -------- Betreff: HLC-Farbatlas Datum: Wed, 7 Feb 2018 06:32:39 +0100 Hi all, After a year of hard work freieFarbe/freeColour is pleased to announce the completion of its first major project, the "HLC Colour Atlas", which is a truly open colour system based on mathematics and unrestricted by copyrights or trademarks. It has been created by colour professionals from Germany and Switzerland. The atlas comprises the following elements: - a printed reference (A4, ring binder) of 2040 colours, based on the intuitive HLC colour model (Hue, Lightness, Chroma), with increments of 10 between each hue. It also includes colours that can't be reproduced in regular CMYK workflows (spot colours). Unlike commercial products, its colour precision is extremely high, with a DeltaE00 of 0.5, i.e. colour differences between two copies of the atlas can only be measured but not perceived, even by a trained eye. Each atlas is being produced with a Fogra-certified high-end proof printer on Fogra-certified paper by a Fogra-certified company. Each copy is also being shipped with a production record (ISO 12647-7:2016); - a printed introduction and usage instructions in German and English; - colour palettes with LAB values for Adobe software (ASE format) and in Swatchbooker's SBZ format, as well as sRGB versions for LibreOffice (SOC), GIMP (GPL) and Scribus 1.4.x (XML). Please note that Scribus 1.5.x already includes the SBZ file, and an sRGB version is being shipped with LibreOffice since version 5.4.x, as well as the current officially stable Scribus 1.4.6. - A PDF master file of the atlas with layers for different output targets (e.g. sRGB, ISOCoatedV2); - XSLX files with colour conversion tables and QC report; - a CxF v.3 file which includes the colour data in spectral values. All files are available for download here: https://www.freiefarbe.de/thema-farbe/software/ The latter is important, because we want to enable others to create their own reliable references without having to ask for permission or paying licence fees. Thus, an ink manufacturer can simply load the CxF file into its formulation software and create the correct mix for his particular inks. Manufacturers of other colourants (e.g. paint, textile colours or plastics) can do the same, provided their software is supporting CxF, which is an open standard. This is also the reason for us not to publish any mixing recipes, because all necessary data to reliably recreate a colour are in the CxF file, so the recipes can be created and customised by software. Whilst the digital files are available for free download under a CC licence, the printed reference needs to be paid for, because production and certification are quite labour-intensive (introductory offer: EUR 99.-- until 31 March 2018, later: EUR 149.-- plus VAT and shipment costs; see: https://shop.proof.de/index.php?language=en). freieFarbe/freeColour are convinced that the "HLC Colour Atlas" is not only a true and open alternative to Pantone, HKS etc., but we also think that the very high quality standard of our printed reference will be hard to match. Our next step is to fill in the necessary paperwork to make this open colour system a DIN SPEC with the German industrial standards organisation DIN (April/May 2018). From there it will hopefully be moved on to ISO to make it an international standard (time frame unknown). Special credits go to Matthias Betz, Holger Everding, Jan-Peter Homann and Eric A. Soder, who did all the heavy lifting, as well as Gregory Pittman, who wrote a Scribus script that reduced the creation of the print PDF for the Atlas to a matter of seconds. freieFarbe/freeColour is also grateful to ColorLogic GmbH, Epson Deutschland GmbH and GMG GmbH & Co KG for generous technical support. The high quality of the atlas is owed to the producer, Proof GmbH. Christoph

1 0

0.92.3 Release Planning Meeting ~ Feb 2nd
by Bryce Harrington 07 Feb '18

07 Feb '18

After the last board meeting we discussed maybe starting 0.92.3 in Feb. I'd like to hold a kickoff meeting following this Friday's board meeting to get started. Hopefully this should be a straightforward release but worthwhile to touch base with everyone just in case. For this meeting I want to just get a handle on the status of everything and flag tasks needing done. I'd like to also get a rough timeline figured out. Date: Fri, 2nd Feb, 2018. Time: 11:00 PST / 19:00 UTC / 20:00 CET Where: #inkscape-devel on freenode What: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.3 Agenda: + Status of the 0.92 tree - Any pending patches we should track? - Are there more fixes worth cherrypicking from trunk? - Are the release notes up to date? + Status of platform packaging - Any new issues compared with 0.92.2? - Are all 0.92.2 packagers available for this go around? + Release cycle plans - One pre-release? - Rough dates + Conditions that might cause release delay + Looking forward --- 0.93 - Dependency versions needing revved? - Remaining licensing issues? - GTK+ 3 stabilization / Windows performance bug - Other stabilization work needed? + Next meeting? - March 2nd following board meeting? + Other business Bryce

1 1

inkscape-docs has a new home
by Eduard Braun 06 Feb '18

06 Feb '18

Hi all, I'm happy to announce that the former "inkscape-docs" (i.e. manpages, keys and mouse reference and tutorials) has a new home! You can now find the "Inkscape Documentation" at https://gitlab.com/inkscape/inkscape-docs/documentation After migrating the repo to GitLab some time ago I finally got around and tweaked some last bits, so it's now in a production-ready state again. Obviously there's still a lot to do (on my short list: getting updated docs onto the website and make translation statistics work again, preferably using some CI automation) but I think the repo is at a point were contributions should be possible without too much effort again and I'd appreciate any help in getting it updated in time for the 0.92.3 release! If you have any questions let me know! Happy documenting, Eduard

2 2

Boolean Operation LPE Question
by Miguel Lopez 06 Feb '18

06 Feb '18

Hi everybody on the mailing list, I have noticed on a inkscape development build that there doesn't seem to be a easy way to use boolean operation LPE. Copy and pasting, and pressing the button doesn't seem to work. Right now, I don't believe this is a bug as I'm thinking that it's a work in progress and thus no need to treat it as a bug, but I could be wrong. Is this a work in progress? Thanks, Miguel Lopez.

1 0

numpy: include, give warning or ...?
by Maren Hachmann 05 Feb '18

05 Feb '18

Hi there, the .deb packages for Ubuntu do not seem to include a dependency for numpy, but the gcodetools depend on it. It's included in the snap, and also seems to be present for Windows and macOS versions. Some other extensions give warnings when it's missing (measure, perspective, dxf_outline,...) So, my question is: Should the gcodetools also just output a warning message with install instructions, like the other extensions do, because there's a reason why numpy cannot be made a dependency? Or could numpy be made a dependency? (I guess that's more a question to packagers - do we make any recommendations anywhere? Or do they need to figure it all out by themselves?) Maren

6 10

Inkscape Board Meeting
by Bryce Harrington 03 Feb '18

03 Feb '18

Our monthly board meeting is scheduled for this Friday, Feb 2nd, 10am Pacific time in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings (Note that a Release Team meeting will follow immediately after. The Vectors Team will be meeting the next day, Saturday the 3rd.) Agenda: + Madras Printer's and Lithographers' Association + Boston Hackfest (March) [doctormo] + Merchandise sales [crogers] + Board election process review [tedg] + Infrastructure hosting [bryce] + LGM 2018 [Tav] + GSoC [ScislaC] + Other Business Action Items from last meeting: ♦ ACTION: Re-ping Madras Printer's and Lithographer's Assoc. [bryce] ♢ ACTION: Find out who did the Indian language translation [Tav/Moini] ♢ ACTION: Calls for fundraising for the hackfest [bryce/Moini] ♦ ACTION: Arrange vote for Boston hackfest [bryce] ♦ ACTION: Arrange vote for LGM [bryce] ♦ ACTION: Port credential repo changes from bzr to git [doctormo] ♦ ACTION: Move credentials repo to a new git project [bryce] ♦ ACTION: Ping Brett regarding DigitalOcean [bryce] ♦ ACTION: Investigate CloudScale.ch [bryce] ♢ ACTION: Kickoff the 0.92.3 release [bryce] ♢ ACTION: Arrange vote on Budget 2018 [bryce] ♦ ACTION: Connect with Diego about CMYK planning [bryce] ♦ ACTION: Kickoff GSoC 2018 registration [ScislaC] ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] ♢ ACTION: Pursue the RedHat option for the hackfest [doctormo] ♢ ACTION: Send invites to old Inkscapers to attend hackfest [bryce] ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] Bryce

1 1