linux-kernel - Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171017080655.GA3139@kroah.com>
Date:   Tue, 17 Oct 2017 10:06:55 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     David Woodhouse <dwmw2@...radead.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested
 Linux kernel license enforcement policy

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