From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
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: Mon, 16 Oct 2017 10:31:58 -0400 [thread overview]
Message-ID: <20171016143158.GA2586@ebb.org> (raw)
In-Reply-To: <20171016134632.GA30345@kroah.com>
I want to thank everyone who has spent years putting together this Linux
Kernel Enforcement Statement. Conservancy issued a public thank-you today:
https://sfconservancy.org/news/2017/oct/16/linux-kernel-enforcement-statement/
Greg wrote:
> 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,
No problem! Here's the stable URL for that link when you add it:
https://sfconservancy.org/copyleft-compliance/principles.html
When Conservancy released those Principles of Community-Oriented GPL
Enforcement, we asked for the copyleft-using community (in general) and the
Linux community (in particular) to join us in discussing it and looking for
ways to adopt those Principles in everyday work. I'm thus really glad to see
this great outcome!
The additional permission in Greg's proposed patch is an excellent way to
begin incorporation of those Principles into Linux's license officially, via
an opt-in exception for copyright holders. Conservancy plans this week to
officially sign it for the Linux copyrights that have been assigned to us.
I also would like to invite everyone to the mailing list created specifically
for this subject, at
https://lists.sfconservancy.org/mailman/listinfo/principles-discuss . Folks
should feel free to Cc that list with this thread, and/or (if the discussion
becomes OT for LKML) start a new thread there.
Greg, finally, I noticed you had some links to resources about compliance in
your blog post. Your readers may also be interested in FSF and Conservancy's
Copyleft Guide, which is at https://copyleft.org/guide/. A direct link to
the chapters on GPL compliance are:
https://copyleft.org/guide/comprehensive-gpl-guidepa2.html#x17-116000II
https://copyleft.org/guide/comprehensive-gpl-guidepa3.html#x26-152000III
I think the latter (the case studies) are particularly useful and my talk on
the most recent case study was well-received at Embedded Linux Conference
2015.
--
Bradley M. Kuhn
Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter
next prev parent reply other threads:[~2017-10-16 14:42 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 [this message]
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
-- 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=20171016143158.GA2586@ebb.org \
--to=bkuhn@sfconservancy.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.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).