From: Jonathan Corbet <corbet@lwn.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Igor Stoppa <igor.stoppa@huawei.com>,
Rob Herring <robh@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
Andy Whitcroft <apw@canonical.com>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH v6] checkpatch.pl: Add SPDX license tag check
Date: Fri, 2 Feb 2018 09:17:20 -0700 [thread overview]
Message-ID: <20180202091720.447b8a2c@lwn.net> (raw)
In-Reply-To: <20180202161246.GA3188@kroah.com>
On Fri, 2 Feb 2018 17:12:46 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > What is the correct/acceptable license for documentation?
> > Creative Commons? AFAIK GPL is for source code.
> >
> > Googling didn't bring the wished-for enlightenment.
>
> It depends on what you want to allow the documentation to be used for.
> It's not a simple answer :(
Honestly, GPL (or more permissive) is the only thing that really makes
sense. Much of the documentation, once processed, includes an awful lot
of stuff directly from the kernel source; there's really no way to say
that it's not a derived product of the kernel. So the output of "make
htmldocs" or "make pdfdocs" really has to be GPL, suggesting that the
input should be GPL-compatible.
GPL isn't the best license for documentation. If we were starting today
I'd try to find a way to use CC-SA instead, but that's not where we're at.
And GPL is workable enough, I think.
At least that's how I see it, not that I really know any more than anybody
else.
jon
next prev parent reply other threads:[~2018-02-02 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:40 Rob Herring
2018-02-02 15:49 ` Igor Stoppa
2018-02-02 16:12 ` Greg Kroah-Hartman
2018-02-02 16:17 ` Jonathan Corbet [this message]
2018-02-02 18:27 ` Rob Herring
2018-02-02 19:06 ` Joe Perches
2018-02-02 20:18 ` Kate Stewart
2018-02-02 20:26 ` Kate Stewart
2018-02-02 20:55 ` Joe Perches
2018-02-08 14:41 ` Philippe Ombredanne
2018-02-02 20:57 ` Rob Herring
2018-02-02 21:10 ` Joe Perches
2018-02-03 13:41 ` Igor Stoppa
2018-02-08 14:44 ` Philippe Ombredanne
2018-02-08 14:35 ` Philippe Ombredanne
2018-02-08 17:24 ` Joe Perches
2018-02-08 18:09 ` Philippe Ombredanne
2018-02-02 21:18 ` Joe Perches
2018-02-09 0:35 ` Joe Perches
2018-02-09 5:58 ` Philippe Ombredanne
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=20180202091720.447b8a2c@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=igor.stoppa@huawei.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome