From: Michael Sweet <msweet@apple.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>,
James Cloos <cloos@jhcloos.com>
Subject: Re: [Printing-architecture] ippusbd license
Date: Wed, 25 Jun 2014 07:09:49 -0400 [thread overview]
Message-ID: <7231748A-31C3-4C70-9C91-19437661D464@apple.com> (raw)
In-Reply-To: <53A9D7F0.1010909@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
GPL3 is a poison pill for most corporations, thanks to the draconian patent terms and generally unfriendly stance towards any other OSS license. Apple has a blanket policy of not allowing any GPL3/LGPL3 use without special authorization, and an absolute prohibition of inclusion of GPL3/LGPL3 licensed software or documentation in any products.
On Jun 24, 2014, at 3:56 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
> What are the advantages of GPL2 against GPL3?
>
> Till
>
> On 06/24/2014 09:27 PM, Ira McDonald wrote:
>> Hi Till,
>>
>> I agree with Mike about preferring GPL2 over GPL3, from comments
>> from some of my colleagues at printer and OS vendors.
>>
>>
>> On Tue, Jun 24, 2014 at 3:06 PM, Michael Sweet <msweet@apple.com
>> <mailto:msweet@apple.com>> wrote:
>>
>> Till,
>>
>> GPL3 is fine when linking against libcups (LGPL2). I'm not 100%
>> sure about the other libraries he'll need to use.
>>
>> That said, I am not a fan of the GPL3 and would prefer this be
>> released under GPL2.
>
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4881 bytes --]
next prev parent reply other threads:[~2014-06-25 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m38up3ymxw.fsf@carbon.jhcloos.org>
2014-06-24 18:35 ` [Printing-architecture] ippusbd license Till Kamppeter
2014-06-24 19:06 ` Michael Sweet
2014-06-24 19:27 ` Ira McDonald
2014-06-24 19:56 ` Till Kamppeter
2014-06-24 19:59 ` James Cloos
2014-06-25 11:09 ` Michael Sweet [this message]
2014-06-25 14:26 ` Till Kamppeter
2014-06-25 16:05 ` Daniel Dressler
2014-06-25 16:24 ` Michael Sweet
2014-06-25 17:36 ` Daniel Dressler
2014-06-25 20:51 ` Ira McDonald
2014-06-25 21:14 ` Daniel Dressler
2014-06-25 21:28 ` Ira McDonald
2014-06-25 21:42 ` Daniel Dressler
2014-06-25 21:49 ` Till Kamppeter
2014-06-25 22:00 ` Daniel Dressler
2014-06-26 1:59 ` Michael Sweet
2014-06-26 7:59 ` Daniel Dressler
2014-06-26 8:19 ` Daniel Dressler
2014-06-25 7:56 ` Johannes Meixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7231748A-31C3-4C70-9C91-19437661D464@apple.com \
--to=msweet@apple.com \
--cc=cloos@jhcloos.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.