GSoC Mentor Summit/Reunion
by Josh Andler
Hello Board,
TL;DR first: Does the board want to fund any additional delegates travel &
room expenses for the reunion if we have anyone chosen by the lottery?
This year for the 10th anniversary of Summer of Code, Google is holding a
special Mentor's Summit (Reunion) which is a little different than in the
past. In addition to the normal 2 delegates we get to send where Google
funds up to $2200 (up to $1100 per person) in travel expenses plus covering
the room, they will hold a lottery for others to be able to attend as well
(however, it is at their own expense as well as the room cost). The people
eligible to attend the Reunion and enter the lottery are any of our
previous GSoC participants (admins, mentors, as well as students).
I wanted to find out if the board would be in favor of funding the travel
and room for anyone from our organization should we have anyone enter the
lottery and be chosen. I have not brought this up to any of our previous
participants yet for obvious reasons, but need to do so soon. One of the
other things that is different this year is that we need to decide far in
advance who will be attending. We need to have everything finalized by
6/20, so people responding to this soon would be appreciated.
Cheers,
Josh
9 years, 1 month
google+ page management
by Alexandre Prokoudine
Hello board,
Since I'm not really involved with the project anymore, I only post
relevant stuff from the Inkscape's Google+ page when I have time,
which is once a month at best. I don't believe this is good for the
project. Hence I'd like to transfer the ownership of the page to
someone else who can be around regularly.
Currently these people are managers of the page: Josh Andler, Tavmjong
Bah, Uwe Schöler. ~suv was invited, but she never accepted the role.
Please use your own judgment who should be owner (there can be only
one), and who should gain (currently missing) management access, then
let me know.
Thanks.
Alex
9 years, 4 months
Legal Statement for Output
by Martin Owens
Hello,
I've been following a Gimp thread about the restrictions or limitations
on the creative output in Gimp. Of course there is no restriction and
our license covers the software not the output. But some companies are
concerned or have questions.
So the question is: Should we put a notice/disclaimer/information in the
about screen stating in plain [local-language] that output from inkscape
is not restricted/copyrighted/limited and is owned by the creator suject
to local laws etc etc.
I'm not sure of the wording and maybe the SFLC could help bake a nice
sentence for multiple Free Software creative groups.
Thoughts?
Martin,
9 years, 4 months
[REFERENDUM] LGM Attendance 2014
by Bryce Harrington
The board is requested to vote on the following matter:
Proposal:
[ ] a. Cover travel and hotel expenses for up to 5 Inkscape
developers to participate in LGM 2014, maximum of $500
per developer.
[ ] b. Do not cover expenses for Inkscape developers to attend LGM.
Background:
LGM is an important meeting for the Libre graphics movement. This is
a good place to showcase our upcoming release, Inkscape 0.91. Having
Inkscape developers get together is always a good thing. Having
Inkscape developers talking with others in the Libre Graphics
movement might even be better.
Unfortunately, it is probably too late to have a developer propose to
give a talk on Inkscape at the meeting.
-- Tavmjong Bah
"Developer" is defined as someone listed in Inkscape's AUTHORS file as
of Feb 19, 2013. -- Bryce Harrington
9 years, 4 months
[karen@...41...: reimbursement for travel on or before March 1]
by Bryce Harrington
----- Forwarded message from Karen Sandler <karen@...41...> -----
Date: Wed, 28 May 2014 22:09:40 -0400
From: Karen Sandler <karen@...41...>
To: project-reps@...41...
Subject: reimbursement for travel on or before March 1
Reply-To: karen@...41...
Hi project reps,
We are finalizing our bookkeeping for the last fiscal year (which
ended at the end of February). If someone in your project has traveled
on or before March 1, 2014 please make sure they file for
reimbursement by June 10 at the latest. According to the travel
policy, there are 90 days to file without needing special approval
from Conservancy's board of directors so hopefully there should be
very few of these still pending!
thanks!
karen
Karen Sandler
Executive Director
Software Freedom Conservancy
----- End forwarded message -----
9 years, 4 months
Re: [Inkscape-board] license incompatibility in inkscape 0.48.4
by Bryce Harrington
The .doc seems to not load in libreoffice; can anyone repost it as .txt?
On Thu, May 15, 2014 at 03:42:34PM +0000, Kanefeyer, Jan wrote:
> Hi,
>
> Attached you will find our fossology scan report. The report lists all licenses and the files where the licenses were found.
>
Wow that's huge.
It looks like there's a bunch of false positives (e.g. we have a
'distribute' feature in the application, but this is detected as a
licensing keyword), slight variations in wording or formatting of the
same license over and over, copyrights claimed by various people, etc.
But, I'm given to understand the only actual tangible problem here is
with the Apache 2 code?
The file lists as covered by Apache 2, two extensions and the SIOX code.
For the extensions scour.py and yocto_css.py, you're right we should not
be distributing these with the codebase. In 4.8.4 you can simply prune
them; they're extensions and not required for compilation or use of the
code. Looking at our codebase, I see a third extension svg_transform,
with the same problem.
rm inkscape-0.48.4/share/extensions/scour.*
rm inkscape-0.48.4/share/extensions/yocto_css.*
rm inkscape-0.48.4/share/extensions/svg_transform.*
I'll take the action to raise this issue on the list to ensure it gets
resolved for 0.91 and 0.48.5.
For the SIOX files, siox.h and siox.cpp, both of those have already been
rewritten to be GPL friendly:
revno: 12370
fixes bug: https://launchpad.net/bugs/357043
committer: Martin Owens <doctormo@...23...>
branch nick: inkscape
timestamp: Tue 2013-06-11 23:48:35 -0400
message:
Fix Apache2 license conflict with GPL with re-license from SOIX
upstream
I don't know that this can be quite as easily ripped out as with the
extensions. Perhaps the fix can be cherrypicked into 0.48.5?
Josh, can you ask Martin if he'd be willing to apply this fix for the
0.48.5 branch?
> In the meantime we checked the installer and found another issue. There are a lot of dll’s and executables (see attached binary list) which cannot be matched with the provided source code. E.g.: There is the file freetype6.dll. But we do not get any search result for freetype in the sources.
freetype is a standard dependency for cairo and gtk (www.freetype.org).
Skimming through the list I think the bulk of the other files are
similar gtk dependencies.
> Where does these binaries come from?
> Are these files taken from other OSS? If yes, can you provide the licenses and sources for these OSS?
Josh and Ted, can you follow up on this?
I think as a general rule we should include a manifest file with the
windows and osx binary packages that lists the component, their license,
and source urls. Josh, that file you pointed to would be a good place
to include this info; a column for license and a column for source url.
Bryce
> Regards
> Jan
>
>
> Von: Josh Andler [mailto:scislac@...23...]
> Gesendet: Donnerstag, 15. Mai 2014 17:22
> An: Ted Gould
> Cc: Kanefeyer, Jan; bryce@...2...; goejendaag@...65...; tavmjong@...47...; Vogler, Andrea; Inkscape Board
> Betreff: Re: license incompatibility in inkscape 0.48.4
>
> More detailed info would definitely be helpful. I've also gone ahead and added the board list via CC since this was intended to go to the board.
> Just to throw out there, I am aware of a couple things. At least Jon Cruz (I believe also Felipe Sanches) has committed multi-licensed code at some point. At least some of the MPL was also licensed as GPL. Regarding the GPL2 vs 3 issue, we still haven't run across anything that explicitly states GPL2 only and what is there says GPL2 or later... so according to discussions with SFC, we are technically still a GPL2 project just with some GPL3 code.
> One example of a multi-licensed file can be viewed at http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/e...
> Cheers,
> Josh
>
> On Thu, May 15, 2014 at 7:38 AM, Ted Gould <ted@...1...<mailto:ted@...80....>> wrote:
> Hello Jan,
>
> I personally am not aware of any licensing issues that we have in Inkscape, thanks for bringing this to our attention! Do you have a report that has more detail of which files/directories are which license so we can look into it with more detail?
>
> Thanks,
> Ted
>
>
> On Thu, 2014-05-15 at 12:43 +0000, Kanefeyer, Jan wrote:
> Hello Inkscape board,
>
> We are planning to use inkscape. Thus we scanned the source code of inkscape 0.48.4 for OSS licenses. So we found out that inscape 0.48.4 includes the following licenses:
>
> GPL 2.0
> GPL 3.0
> LGPL 2.1
> MPL 1.1
> Apache License 2.0
> creativecommons Attribution-ShareAlike 3.0 Unported
> BSD-2-Clause
> BSD-3-Clause
> MIT
> Zlib
> W3C
>
> Unfortunately there are license incompatibilities between some on the licenses. E.g.:
> Apache 2.0 <-> GPL 2.0
> GPL 2.0 <-> GPL 3.0
> MPL 1.1 <-> GPL 2.0 + GPL 3.0 + LGPL 2.1 + Apache License 2.0
>
> This leads to a serious problem: The creator of the code published under Apache License 2.0 can prohibit a publishing of his code under GPL 2.0. So we are not allowed to publish it at all.
>
> So here are my questions:
> Is the community aware of this problem?
> Is there a general statement regarding this topic available?
> Are there any counter measures planned/implemented?
>
> Kind Regards
> Jan Kanefeyer
>
> Mit freundlichen Grüßen
> Jan Kanefeyer
>
> Siemens AG
> Infrastructure & Cities Sector
> Smart Grid Division
> Energy Automation
> IC SG EA SOL D 1
> Humboldtstr. 59
> 90459 Nürnberg, Deutschland
> Tel: +49 911 433-8044<tel:%2B49%20911%20433-8044>
> mailto:jan.kanefeyer@...76... <mailto:jan.kanefeyer@...76...>
>
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Klaus Helmrich, Hermann Requardt, Siegfried Russwurm, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
>
>
>
>
> DLLs :
> ------
> \inkscape-0.48.4-1-win32_Installer\bzip2.dll
> \inkscape-0.48.4-1-win32_Installer\freetype6.dll
> \inkscape-0.48.4-1-win32_Installer\iconv.dll
> \inkscape-0.48.4-1-win32_Installer\intl.dll
> \inkscape-0.48.4-1-win32_Installer\libatk-1.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libatkmm-1.6-1.dll
> \inkscape-0.48.4-1-win32_Installer\libcairo-2.dll
> \inkscape-0.48.4-1-win32_Installer\libcairomm-1.0-1.dll
> \inkscape-0.48.4-1-win32_Installer\libexpat-1.dll
> \inkscape-0.48.4-1-win32_Installer\libfontconfig-1.dll
> \inkscape-0.48.4-1-win32_Installer\libgcc_s_sjlj-1.dll
> \inkscape-0.48.4-1-win32_Installer\libgdk-win32-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgdkmm-2.4-1.dll
> \inkscape-0.48.4-1-win32_Installer\libgdk_pixbuf-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgio-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgiomm-2.4-1.dll
> \inkscape-0.48.4-1-win32_Installer\libglib-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libglibmm-2.4-1.dll
> \inkscape-0.48.4-1-win32_Installer\libgmodule-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgobject-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgomp-1.dll
> \inkscape-0.48.4-1-win32_Installer\libgthread-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgtk-win32-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libgtkmm-2.4-1.dll
> \inkscape-0.48.4-1-win32_Installer\libintl-8.dll
> \inkscape-0.48.4-1-win32_Installer\libjpeg-7.dll
> \inkscape-0.48.4-1-win32_Installer\liblcms-1.dll
> \inkscape-0.48.4-1-win32_Installer\libMagick++-3.dll
> \inkscape-0.48.4-1-win32_Installer\libMagickCore-3.dll
> \inkscape-0.48.4-1-win32_Installer\libMagickWand-3.dll
> \inkscape-0.48.4-1-win32_Installer\libopenjpeg-2.dll
> \inkscape-0.48.4-1-win32_Installer\libpango-1.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpangocairo-1.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpangoft2-1.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpangomm-1.4-1.dll
> \inkscape-0.48.4-1-win32_Installer\libpangowin32-1.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpixman-1-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpng12-0.dll
> \inkscape-0.48.4-1-win32_Installer\libpng14-14.dll
> \inkscape-0.48.4-1-win32_Installer\libpoppler-5.dll
> \inkscape-0.48.4-1-win32_Installer\libpoppler-glib-4.dll
> \inkscape-0.48.4-1-win32_Installer\libpopt-0.dll
> \inkscape-0.48.4-1-win32_Installer\libsigc-2.0-0.dll
> \inkscape-0.48.4-1-win32_Installer\libtiff-3.dll
> \inkscape-0.48.4-1-win32_Installer\libwpd-0.9.dll
> \inkscape-0.48.4-1-win32_Installer\libwpd-stream-0.9.dll
> \inkscape-0.48.4-1-win32_Installer\libwpg-0.2.dll
> \inkscape-0.48.4-1-win32_Installer\libxml2.dll
> \inkscape-0.48.4-1-win32_Installer\libxslt.dll
> \inkscape-0.48.4-1-win32_Installer\mingwm10.dll
> \inkscape-0.48.4-1-win32_Installer\msvcr70.dll
> \inkscape-0.48.4-1-win32_Installer\msvcr71.dll
> \inkscape-0.48.4-1-win32_Installer\perl58.dll
> \inkscape-0.48.4-1-win32_Installer\pthreadGC2.dll
> \inkscape-0.48.4-1-win32_Installer\python26.dll
> \inkscape-0.48.4-1-win32_Installer\zlib1.dll
> \inkscape-0.48.4-1-win32_Installer\$PLUGINSDIR\InstallOptions.dll
> \inkscape-0.48.4-1-win32_Installer\$PLUGINSDIR\System.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\DLLs\sqlite3.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\engines\libpixmap.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\engines\libsvg.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\engines\libwimp.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-am-et.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-cedilla.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-cyrillic-translit.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-ime.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-inuktitut.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-ipa.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-multipress.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-thai.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-ti-er.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-ti-et.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\immodules\im-viqr.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-ani.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-bmp.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-gif.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-icns.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-ico.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-jpeg.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-pcx.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-png.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-pnm.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-ras.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-tga.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-tiff.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-wbmp.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-xbm.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\libpixbufloader-xpm.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\2.10.0\loaders\svg_loader.dll
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\gtk-2.0\modules\libgail.dll
> \inkscape-0.48.4-1-win32_Installer\share\tutorials\$PLUGINSDIR\LangDLL.dll
> \inkscape-0.48.4-1-win32_Installer\share\tutorials\$PLUGINSDIR\md5dll.dll
> \inkscape-0.48.4-1-win32_Installer\share\tutorials\$PLUGINSDIR\UserInfo.dll
>
>
> EXE files :
> -----------
> \inkscape-0.48.4-1-win32_Installer\gspawn-win32-helper-console.exe
> \inkscape-0.48.4-1-win32_Installer\gspawn-win32-helper.exe
> \inkscape-0.48.4-1-win32_Installer\inkscape.exe
> \inkscape-0.48.4-1-win32_Installer\inkview.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-6.0.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-6.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-7.1.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-8.0.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-9.0-amd64.exe
> \inkscape-0.48.4-1-win32_Installer\$_OUTDIR\Lib\distutils\command\wininst-9.0.exe
> \inkscape-0.48.4-1-win32_Installer\python\python.exe
> \inkscape-0.48.4-1-win32_Installer\python\pythonw.exe
9 years, 4 months
[REFERENDUM] Inkscape Funded Development Model
by Bryce Harrington
A majority vote of the current board members is required for this
matter.
Proposal:
1. Adoption of the procedure described below for handling fundraisers
and funded development work.
2. Board chairman will document this procedure on the Inkscape
website, and announce to the developer and user mailing lists.
[ ] a. Yes, adopt this procedure and announce it
[ ] b. No, do not adopt this procedure
------------------------------------------------------------------------
[See Appendix B for changes made based on feedback from Inkscape community.]
Inkscape Funded Development Model
---------------------------------
1. Fundraising
===============
Using the model we'll describe below, anyone may start an official
fundraiser for Inkscape development. We leave it to your imagination
how to structure and run your fundraising campaign, and empower you with
selecting from a list of defined development goals to fund, so long as a
few requirements are met.
First, the person who organizes and supervises a fundraising campaign is
termed a Fundraising Coordinator. We may have multiple coordinators if
we have multiple campaigns, but only one coordinator per fundraiser.
They have three duties:
a) Administration of the fundraiser
b) Allocate raised funds to projects
c) (Optionally) Be involved in final signoff of completed projects
The first duty is left to the Fundraising Coordinator's discretion.
The second duty should be straightforward. When the fundraiser is
completed, all funds must be allocated to one or more projects in the
official Jobs List. No guarantee is made that any given project will be
undertaken if there is insufficient developer interest, but future
fundraisers can up the funds allocated to it to stimulate interest.
We expect some campaigns will wish to target one or more specific
projects, and announce this upfront to stimulate donations. This is
fine to do, but keep in mind that projects can change (or get
implemented) while the campaign is under way. So instead of naming
specific projects, it may be better to describe the types of projects
the campaign is aiming to fund, and make the specific decision(s) when
the fundraiser is over.
For ongoing fundraisers, the coordinator responsible for setting it up
can specify the distribution programmatically (e.g. "distribute evenly
to the four oldest projects in the list as of the end of the campaign",
or "10% to each of the ten projects with the highest funding from past
campaigns", or "allocated evenly across all documentation projects
registered as of the start of this campaign". The coordinator will
remain responsible for administrative duties both during and after the
fundraiser. Should they need to step down, they may name a replacement
to hand the remaining duties down to. If they disappear without naming
a replacement, or if there are any other irregularities or questions,
the issue should be escalated to the Inkscape Board for resolution.
The third duty - signing off on completion of the project - is described
in more detail below. The Fundraising Coordinator *can't* do this if
they personally contribute most of the funding, because it'd run us
afoul of IRS rules.
2. Proposing New Projects
==========================
We maintain a listing of proposed (unfunded) projects. Anything can be
proposed, including feature development, bug triaging, documentation,
administration, etc. but it must include a detailed description (>100
words) of the work to be done. Anyone may adopt these projects as
regular (unfunded) development tasks, GSoC projects, etc. (This is so
that any proposed projects that are fun or easy get done by volunteers,
and money can be focused on harder unsexy work, and to make abuse
harder.)
Once a proposed project has reached a certain age, it will be eligible
for funding. We'll call these eligible projects 'jobs', once they meet
the following conditions:
a. Has been on the Proposed Projects list for >=6 months
b. A Deliverable has been defined
c. Acceptance Criteria has been defined (see appendix)
d. A Time Limit has been estimated for how long the work should take
e. Proposal has been Seconded by another Developer that the proposed
change is, in concept, worth including in the Inkscape codebase
Once a proposal meets all 5 of these conditions it is considered an
Approved Job.
3. Fundable Jobs List
======================
The money from these fundraisers goes to the Inkscape Foundation account
administered by the Software Freedom Conservancy, who takes a small
percentage of each donation. Conservancy is a US 501(c)(3) public
charity, and all donations are tax deductible in the United States as
allowed by law.
We maintain a list of allocations-to-jobs so we can keep track of what
money "belongs" to which job, so the correct amount is paid when the job
is done. This amount is displayed on the web for developers to browse
when selecting a job to do.
Anyone in the Inkscape AUTHORS file is eligible to apply for a job.
The applicant must submit a Job Proposal, which will identify the
applicant's qualifications for doing the job, and outline how they
intend to do the implementation.
The Inkscape Board will delegate one of its members to review and vet
applicants to help ensure the best candidates are selected for each job.
For larger, longer, or more complicated jobs the vetting may take some
time, but for moderate sized jobs the intent is for a decision to be
made within a few days. The Inkscape Board may elect to mark some jobs
(such as smaller ones) as Pre-Approved; once an applicant files an
application they may begin the job immediately, no vetting required.
Board members are excepted from this process due to conflict of
interest; they may apply for the jobs but must still be vetted.
No one may assign themselves more than one Pre-Approved job at a time,
and the Board reserves the right to subsequently review the application
and disapprove it in case of problems.
When an applicant is assigned the job, the clock starts ticking. The
applicant must post at least one progress report each month (e.g. to a
blog or to the Inkscape wiki). During the time limit, so long as the
monthly reports are being clearly posted, no one else can apply to do
the same job. If two months pass without a report, or when the 6 months
time runs out, and the job is not completed, the assignee doesn't
receive the funds and can't attempt the same job again for 6 months.
The job is considered completed when the identified deliverables are
delivered according to the specified criteria.
4. Completion Criteria
=======================
The Reviewer makes the decision as to whether the job has been
adequately completed, using the originally specified criteria.
By default, the Fundraising Coordinator is the Reviewer; if the project
was funded from multiple sources, the one that allocated the largest
amount of funding (or their chosen delegate) is the Reviewer. This
person must formally accept the Reviewer role by email within 1 week.
For any reason, they may opt to decline the Reviewer role. If they are
unresponsive or opt to decline the role, it passes to the next
Fundraising Coordinator. If no Fundraising Coordinators take or
delegate the role, then the Inkscape Board will delegate a Reviewer.
However the Reviewer is decided, he or she must be a different person
than the original Project Proposer, and neither the Reviewer nor the
Reviewer's employer may contribute more than 50% of the total funds for
the given project. We want to avoid a situation where a person or their
employer has an independent business interest in seeing the job
completed, and is over-involved in the management of the work.
5. Termination and Modification
================================
The original proposer of the Project or Job may withdraw it or modify
its definition at any time, so long as someone is not signed up for it.
If the Project is withdrawn, all funds allocated to it return to the
general Inkscape fund.
Unassigned Jobs expire 24 months after their initial project proposal.
This is intended to clear out deadwood projects and to encourage
developers to adopt projects with allocated funds before they expire,
and to discourage proposing projects that are unlikely to get attention
in 24 months. Any funds allocated to untaken jobs are moved to
Inkscape's general fund.
At its discretion, by majority vote the board may elect to extend the
expiration date of about-to-expire Jobs with funds allocated by 12
months.
6. Process Exceptions
======================
Historically, all development work funded by the Inkscape Project
required authorization by the Inkscape Board of Directors; this funding
model is to establish a structure for development funding that does not
require Board involvement. However, the Board retains the ability to
authorize exceptions for anything outside the bounds of this policy, to
be handled on a case-by-case basis, with decisions made by a majority
vote.
In particular, the Board may select by vote certain projects to be
immediately fundable, without needing to wait the normal 6 month period.
They may also withdraw any project or job at any time, by majority vote,
including even assigned, in-progress jobs (though this should be highly
unusual).
The Board may also make changes to this policy via a normal majority
vote.
7. Conflict Resolution
=======================
If there are any problems or disagreements once a project has been
assigned to a Developer, a Meeting can be called by any stakeholder
(Project Proposer, Developer, Fundraising Campaigns, Reviewer, or
Inkscape Board Member). For proper quorum, at a minimum the Meeting
must be attended by the Developer, either the Project Proposer or the
Reviewer, at least one Fundraising Coordinator involved in the funding
of the project, any one Board Member, and a Colleague Developer (whom
can be anyone in the Inkscape AUTHORS file selected by the Developer).
Any unanimous decision reached in this Meeting is binding on all
parties.
Any conflict that can't be resolved via a Meeting may then be escalated
to the Inkscape Board of Directors, who will be the ultimate arbiter.
Conflicts of interest, including conflicts with the board, are governed
by the Software Freedom Conservancy's org-wide conflict of interest
policy.
Appendix A: Example Delivery and Acceptance Criteria
=====================================================
# This is a sample set of delivery and acceptance criteria; each project
# may use, alter, or replace any of these conditions as appropriate.
a. Test cases are provided to add coverage for all newly added
functionality.
b. Documentation patches provided for describing all newly added
functionality.
c. Updates provided for release notes, NEWS, bug reports, etc.
d. All patch(es) have landed in the official upstream repository. Either
in the mainline tree, or in an officially designated branch as per
upstream policy.
e. Code builds and runs on the major platforms supported by the
project.
f. Code passes the upstream project's designated style/lint checking
tools.
g. User-visible strings are translatable as per project policy.
h. Unit and regression test suites pass with no new test failures.
At project completion, once the above criteria is met, 70% of the
payable funds are delivered. 30% is held in reserve for bug fix
followup: One month after completion, a list of identified bugs can be
specified by the Reviewer to be fixed; if all are fixed within a month,
the remaining 30% of the funding is released to the developer. If no
bugs exist, or none are specified before 6 weeks after completion, then
the developer is paid the remainder directly.
Appendix B: Changelog
=====================
Changes v5
* Exclude the board from pre-approved jobs, to avoid conflict of
interest.
* Drop the section for handling the case where a non-assigned
developer does the assigned task. This will probably be an unusual
situation, and the board can decide on a case-by-case basis.
* In the example Acceptance Criteria, adjusted payments to 70% for
project completion and 30% for bugfix / final acceptance. Don't
set a limit to the number of bug reports; this should be determined
organically - in case of abuse there is a conflict resolution
mechanism available.
* In the opening paragraph clarify that the allowed development goals
are selected from a pre-defined list.
* Elaborate on how a rough proposed idea becomes an approved job for
selection.
* Jobs that are about to expire can be extended 12 months by a
majority Board vote.
* For Conflict Resolution, renamed 'Neutral Developer' to 'Colleague
Developer', since this person is selected by the Developer and thus
likely will be partial to their cause; 'Neutral' would suggest a
level of impartiality which is neither realistic nor really
necessary.
Changes v4:
* Drop the requirement for allocating no more than 25% per project.
* If a project is withdrawn by its original proposer, any money
allocated for it goes back to the general pool.
* Avoid ambiguous "Fundraiser" verbage. Use either "Fundraising
Coordinator" or "Fundraising Campaign".
* Fix Software Freedom Conservancy name.
* Give advice on allocation of funds to projects to not be too
specific upfront.
* Require job applicants to submit applications, which will be vetted
and approved by the board. Allow board to delegate this work to an
elected member. Allow for smaller tasks to be marked Pre-Approved,
that can be undertaken with no vetting.
* Require job assignees to post monthly progress reports, or else
job can be reassigned to someone else.
* Prohibit the Project Proposer from also being the Reviewer.
* Prohibit person from being a Reviewer if they or their employer
contributed over half the funds.
* Various spelling and grammar fixes.
Changes v3:
* Reordered sections for clarity. Start with fundraising.
* Discuss the duties of Fundraising Coordinators in more detail.
* Reviewers cannot have contributed more than 50% of the funds for the
project. This is due to IRS restrictions we must follow in order to
remain covered as non-profit. "50%" is just a WAG and may need
adjusted down (possibly to 0%) pending legal advice from SFC.
* Expire unassigned jobs after 24 months rather than 30.
* Note that SFC can be used for resolving conflicts of interest.
Changes v2:
* Added subheadings
* Added Exception section clarifying board powers
* Jobs expire after 30 months
* Gave original proposer power to modify or terminate projects
* Defined the Reviewer role
* Added example Delivery and Acceptance Criteria as an appendix
9 years, 4 months
Re: [Inkscape-board] license incompatibility in inkscape 0.48.4
by Josh Andler
Hi,
Is the fossology report generated in Word format? Is it possible to
generate it in either plain text or in a format that is an open standard?
Unfortunately I am unable to open it in LibreOffice.
As for the libraries included in windows bundles, please see the following
for more information:
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/view/hea...
Cheers,
Josh
On Thu, May 15, 2014 at 8:42 AM, Kanefeyer, Jan
<jan.kanefeyer@...76...>wrote:
> Hi,
>
>
>
> Attached you will find our fossology scan report. The report lists all
> licenses and the files where the licenses were found.
>
>
>
> In the meantime we checked the installer and found another issue. There
> are a lot of dll’s and executables (see attached binary list) which cannot
> be matched with the provided source code. E.g.: There is the file
> freetype6.dll. But we do not get any search result for freetype in the
> sources.
>
> Where does these binaries come from?
>
> Are these files taken from other OSS? If yes, can you provide the licenses
> and sources for these OSS?
>
>
>
> Regards
>
> Jan
>
>
>
>
>
> *Von:* Josh Andler [mailto:scislac@...23...]
> *Gesendet:* Donnerstag, 15. Mai 2014 17:22
> *An:* Ted Gould
> *Cc:* Kanefeyer, Jan; bryce@...2...; goejendaag@...65...;
> tavmjong@...47...; Vogler, Andrea; Inkscape Board
> *Betreff:* Re: license incompatibility in inkscape 0.48.4
>
>
>
> More detailed info would definitely be helpful. I've also gone ahead and
> added the board list via CC since this was intended to go to the board.
>
> Just to throw out there, I am aware of a couple things. At least Jon Cruz
> (I believe also Felipe Sanches) has committed multi-licensed code at some
> point. At least some of the MPL was also licensed as GPL. Regarding the
> GPL2 vs 3 issue, we still haven't run across anything that explicitly
> states GPL2 only and what is there says GPL2 or later... so according to
> discussions with SFC, we are technically still a GPL2 project just with
> some GPL3 code.
>
> One example of a multi-licensed file can be viewed at
> http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/e...
>
> Cheers,
>
> Josh
>
>
>
> On Thu, May 15, 2014 at 7:38 AM, Ted Gould <ted@...1...> wrote:
>
> Hello Jan,
>
> I personally am not aware of any licensing issues that we have in
> Inkscape, thanks for bringing this to our attention! Do you have a report
> that has more detail of which files/directories are which license so we can
> look into it with more detail?
>
> Thanks,
> Ted
>
>
>
> On Thu, 2014-05-15 at 12:43 +0000, Kanefeyer, Jan wrote:
>
> Hello Inkscape board,
>
>
>
> We are planning to use inkscape. Thus we scanned the source code of
> inkscape 0.48.4 for OSS licenses. So we found out that inscape 0.48.4
> includes the following licenses:
>
>
>
> GPL 2.0
>
> GPL 3.0
>
> LGPL 2.1
>
> MPL 1.1
>
> Apache License 2.0
>
> creativecommons Attribution-ShareAlike 3.0 Unported
>
> BSD-2-Clause
>
> BSD-3-Clause
>
> MIT
>
> Zlib
>
> W3C
>
>
>
> Unfortunately there are license incompatibilities between some on the
> licenses. E.g.:
>
> Apache 2.0 <-> GPL 2.0
>
> GPL 2.0 <-> GPL 3.0
>
> MPL 1.1 <-> GPL 2.0 + GPL 3.0 + LGPL 2.1 + Apache License 2.0
>
>
>
> This leads to a serious problem: The creator of the code published under
> Apache License 2.0 can prohibit a publishing of his code under GPL 2.0. So
> we are not allowed to publish it at all.
>
>
>
> So here are my questions:
>
> Is the community aware of this problem?
>
> Is there a general statement regarding this topic available?
>
> Are there any counter measures planned/implemented?
>
>
>
> Kind Regards
>
> Jan Kanefeyer
>
>
>
> Mit freundlichen Grüßen
>
> Jan Kanefeyer
>
>
>
> Siemens AG
>
> Infrastructure & Cities Sector
>
> Smart Grid Division
>
> Energy Automation
>
> IC SG EA SOL D 1
>
> Humboldtstr. 59
>
> 90459 Nürnberg, Deutschland
>
> Tel: +49 911 433-8044
>
> *mailto:jan.kanefeyer@...76... <jan.kanefeyer@...76...>*
> <jan.kanefeyer@...76...>
>
>
>
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard
> Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Klaus Helmrich,
> Hermann Requardt, Siegfried Russwurm, Ralf P. Thomas; Sitz der
> Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin
> Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
>
>
>
>
>
>
>
>
>
9 years, 4 months
Re: [Inkscape-board] license incompatibility in inkscape 0.48.4
by Josh Andler
More detailed info would definitely be helpful. I've also gone ahead and
added the board list via CC since this was intended to go to the board.
Just to throw out there, I am aware of a couple things. At least Jon Cruz
(I believe also Felipe Sanches) has committed multi-licensed code at some
point. At least some of the MPL was also licensed as GPL. Regarding the
GPL2 vs 3 issue, we still haven't run across anything that explicitly
states GPL2 only and what is there says GPL2 or later... so according to
discussions with SFC, we are technically still a GPL2 project just with
some GPL3 code.
One example of a multi-licensed file can be viewed at
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/e...
Cheers,
Josh
On Thu, May 15, 2014 at 7:38 AM, Ted Gould <ted@...1...> wrote:
> Hello Jan,
>
> I personally am not aware of any licensing issues that we have in
> Inkscape, thanks for bringing this to our attention! Do you have a report
> that has more detail of which files/directories are which license so we can
> look into it with more detail?
>
> Thanks,
> Ted
>
>
> On Thu, 2014-05-15 at 12:43 +0000, Kanefeyer, Jan wrote:
>
> Hello Inkscape board,
>
>
>
> We are planning to use inkscape. Thus we scanned the source code of
> inkscape 0.48.4 for OSS licenses. So we found out that inscape 0.48.4
> includes the following licenses:
>
>
>
> GPL 2.0
>
> GPL 3.0
>
> LGPL 2.1
>
> MPL 1.1
>
> Apache License 2.0
>
> creativecommons Attribution-ShareAlike 3.0 Unported
>
> BSD-2-Clause
>
> BSD-3-Clause
>
> MIT
>
> Zlib
>
> W3C
>
>
>
> Unfortunately there are license incompatibilities between some on the
> licenses. E.g.:
>
> Apache 2.0 <-> GPL 2.0
>
> GPL 2.0 <-> GPL 3.0
>
> MPL 1.1 <-> GPL 2.0 + GPL 3.0 + LGPL 2.1 + Apache License 2.0
>
>
>
> This leads to a serious problem: The creator of the code published under
> Apache License 2.0 can prohibit a publishing of his code under GPL 2.0. So
> we are not allowed to publish it at all.
>
>
>
> So here are my questions:
>
> Is the community aware of this problem?
>
> Is there a general statement regarding this topic available?
>
> Are there any counter measures planned/implemented?
>
>
>
> Kind Regards
>
> Jan Kanefeyer
>
>
>
> Mit freundlichen Grüßen
>
> Jan Kanefeyer
>
>
>
> Siemens AG
>
> Infrastructure & Cities Sector
>
> Smart Grid Division
>
> Energy Automation
>
> IC SG EA SOL D 1
>
> Humboldtstr. 59
>
> 90459 Nürnberg, Deutschland
>
> Tel: +49 911 433-8044
>
> *mailto:jan.kanefeyer@...76... <jan.kanefeyer@...76...>*
> <jan.kanefeyer@...76...>
>
>
>
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard
> Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Klaus Helmrich,
> Hermann Requardt, Siegfried Russwurm, Ralf P. Thomas; Sitz der
> Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin
> Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
>
>
>
>
>
>
>
>
9 years, 4 months
