Re: [cups-devel] CUPS License Change Coming

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

--Boundary_(ID_zwfAcyElnDtljM7JJHYWQA)
Content-type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary=DtP23na27JrsBHAhiClFn1eF5a8QBLQCi

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--DtP23na27JrsBHAhiClFn1eF5a8QBLQCi
Content-Type: multipart/mixed; boundary="HqdW4F8VC8jDS342S4LiRN6DmTBUkpjSl";
 protected-headers="v1"
From: Zdenek Dohnal <[email protected]>
To: [email protected]
Message-ID: <3aae6aa4-f4e5-c8f8-f1bf-dc3c3f718c87-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [cups-devel] CUPS License Change Coming
References: <2E55FEEC-11BA-4789-B6F8-C6CCC27A8884-2kanFRK1NckAvxtiuMwx3w@public.gmane.org>
 <[email protected]>
 <BC8ED8CE-941C-4F90-94D3-045CCD2123D5-2kanFRK1NckAvxtiuMwx3w@public.gmane.org>
In-Reply-To: <BC8ED8CE-941C-4F90-94D3-045CCD2123D5-2kanFRK1NckAvxtiuMwx3w@public.gmane.org>

--HqdW4F8VC8jDS342S4LiRN6DmTBUkpjSl
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

On 11/08/2017 02:57 PM, Michael Sweet wrote:
> Didier,
>
>> On Nov 8, 2017, at 2:42 AM, Didier 'OdyX' Raboud <[email protected]> wro=
te:
>>
>> Le mardi, 7 novembre 2017, 15.05:19 h CET Michael Sweet a =C3=A9crit :=

>>> Apple is excited to announce that starting with CUPS 2.3 we will be
>>> providing CUPS under the terms of the Apache License, Version 2.0.
>>>
>>> For more information about the Apache License, Version 2.0, please se=
e the
>>> Apache Software Foundation licenses page at:
>>>
>>>    http://www.apache.org/licenses/
>> CUPS was so far licensed under what Debian nicknamed as "GPL-2.0 with =
AOSDL=20
>> exception"  [0] :
> Right, and we've added and removed exceptions over the years to deal wi=
th license incompatibilities.
>
>>> (=E2=80=A6) In addition, as the copyright holder of CUPS, Apple Inc. =
grants  the
>>> following special exception: (=E2=80=A6)
>> Is Apple going with "pristine" Apache License 2.0 [1] without further =

>> exceptions?
> Yes, you can see the license change in the Github repository - it is al=
ready live for the master branch which is tracking CUPS 2.3.x now...
>
>> This is going to make CUPS incompatible with GPL-2-only software=20
>> [2,3]. My understanding it that it doesn't affect dynamic-linking situ=
ations=20
>> (both software that CUPS needs, or software that need libcups*), aka n=
ot a=20
>> concern for distributors, but are there other potential impacts of thi=
s=20
>> license change that I'm missing ?
> I don't think static linking against libcups is common enough to be a s=
erious concern - CUPS is fairly ubiquitous and easily falls under the "OS=
-supplied library" exception in the GPL 2.  And existing GPL-2-only softw=
are that *does* statically link/copy CUPS code can continue to do so with=
 CUPS 2.2.x and earlier.
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>
> _______________________________________________
> cups-devel mailing list
> [email protected]
> https://lists.cups.org/mailman/listinfo/cups-devel
Hi Mike,

would you mind considering dual license - Apache License 2.0 and GPLv2+?
Because "OS-supplied library" definition is relative and it could end up
that any widely used library can be exception (not mention widely used
libraries differs across distributions - so library would be count as
"OS-supplied library" on one distro and not on a other) - and that will
lead into nullifying existing licensing rules.

--=20
Zdenek Dohnal
Associate Software Engineer
Red Hat Czech - Brno TPB-C



--HqdW4F8VC8jDS342S4LiRN6DmTBUkpjSl--

--DtP23na27JrsBHAhiClFn1eF5a8QBLQCi--

--Boundary_(ID_zwfAcyElnDtljM7JJHYWQA)
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Content-disposition: inline

_______________________________________________
cups-devel mailing list
[email protected]
https://lists.cups.org/mailman/listinfo/cups-devel

--Boundary_(ID_zwfAcyElnDtljM7JJHYWQA)--