linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy
Date: Tue, 17 Oct 2017 10:06:55 +0200	[thread overview]
Message-ID: <20171017080655.GA3139@kroah.com> (raw)
In-Reply-To: <20171016134632.GA30345@kroah.com>

On Mon, Oct 16, 2017 at 03:46:32PM +0200, Greg KH wrote:
> On Mon, Oct 16, 2017 at 02:11:01PM +0100, David Woodhouse wrote:
> > On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> > > Documentation: Add a file explaining the requested Linux kernel
> > > license enforcement policy
> > > 
> > > Here's a pull request to add a new file to the kernel's Documentation directory.
> > > It adds a short document describing the views of how the Linux kernel community
> > > feels about enforcing the license of the kernel.
> > > 
> > > The patch has been reviewed by a large number of kernel developers already, as
> > > seen by their acks on the patch, and their agreement of the statement with
> > > their names on it.  The location of the file was also agreed upon by the
> > > Documentation maintainer, so all should be good there.
> > > 
> > > For some background information about this statement, see this article
> > > written by some of the kernel developers involved in drafting it:
> > > 	http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement/
> > > and this article that answers a number of questions that came up in the
> > > discussion of this statement with the kernel developer community:
> > > 	http://kroah.com/log/blog/2017/10/16/linux-kernel-community-enforcement-statement-faq/
> > > 
> > > If anyone has any further questions about it, please let me, and the TAB
> > > members, know and we will be glad to help answer them.
> > 
> > It's a shame you don't explicitly mention the FSF's / Conservancy's
> > Principles of Community-Oriented GPL Enforcement:
> > https://www.fsf.org/licensing/enforcement-principles
> 
> What?  I thought I did in my blog post!  Ugh, you are right, it's not
> there, my fault, it was in an earlier draft, I swear, sorry about that,
> must have gotten lost when I turned it from text into a
> markdown-formatted document.  I'll go add it and push out the updated
> post in a bit.

Ok, in reviewing my previous drafts, and my notes for this, I see why I
didn't include it in the final version, so I'll just leave my post
as-is.

thanks,

greg k-h

  parent reply	other threads:[~2017-10-17  8:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  9:25 [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy Greg KH
2017-10-16  9:28 ` [PATCH] Documentation: Add a file explaining the Linux kernel license Greg KH
2017-10-16 13:16   ` Sumit Semwal
2017-10-18 17:21     ` Greg KH
2017-10-16 13:11 ` [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-19 15:28 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
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

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=20171017080655.GA3139@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).