linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: Pavel Nikulin <nikulinpi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy
Date: Sat, 21 Oct 2017 22:28:19 -0400	[thread overview]
Message-ID: <87mv4j6hmk.fsf@ebb.org> (raw)
In-Reply-To: <CAN3U_kUf488dXnWznifLbecMjOZrFFOLZVT8mrk0qHzr0+3LJA@mail.gmail.com> (Pavel Nikulin's message of "Sat, 21 Oct 2017 22:16:12 +0300")

> On Thu, Oct 19, 2017 at 06:28:12PM +0300, Pavel Nikulin wrote:
> Modification of GPL V2 terms are explicitly disallowed.

Greg KH replied at 03:29 (US/Eastern) on Friday:
>> Again, we are not modifying the license, so all should be fine

I agree with Greg; the Linux Kernel Enforcement Statement does not change
the license of Linux as a whole, and it does not modify the GPLv2.

Pavel Nikulin wrote at 11:28 (US/Eastern) on Thursday:
> Greg, are you trying to put a new addendum to the terms of GPL v2?
...
Pavel Nikulin wrote further at 15:16 (US/Eastern) today:
> If you say that your lawyers have comprehensively researched that,
> I can't say they did a good job. Almost every line sounds close to
> being a contractual agreement.
...
> And even this last phrase does not states explicitly that the nature of
> the document as non-legally binding.
...
> Moreover, you put "additional permissions under our license" wording
> there,

Certainly this issue is complicated.
https://sfconservancy.org/blog/2017/oct/20/additional-permissions/ might
help.  I decided yesterday to write a blog post digging deep into the weeds
on this, for those interested.
-- 
Bradley M. Kuhn
Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

  reply	other threads:[~2017-10-22  2:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 15:28 [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy Pavel Nikulin
2017-10-20  7:29 ` Greg KH
2017-10-20 18:25 ` Alan Cox
2017-10-21  8:03   ` Greg KH
2017-10-21 19:16   ` Pavel Nikulin
2017-10-22  2:28     ` Bradley M. Kuhn [this message]
2017-10-23  7:50     ` Greg KH
2017-10-23 13:11       ` Pavel Nikulin
2017-10-23 14:35         ` Theodore Ts'o
2017-10-23 17:47           ` Damian Tometzki
2017-10-23 18:26           ` Damian Tometzki
  -- strict thread matches above, loose matches on Subject: below --
2017-10-16  9:25 Greg KH
2017-10-16 13:11 ` David Woodhouse
2017-10-16 13:46   ` Greg KH
2017-10-16 14:31     ` Bradley M. Kuhn
2017-10-16 14:50     ` David Woodhouse
2017-10-17 14:57       ` Greg KH
2017-12-10  8:21       ` Pavel Machek
2017-10-17  8:06     ` Greg KH

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=87mv4j6hmk.fsf@ebb.org \
    --to=bkuhn@sfconservancy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikulinpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).