From: Christoph Hellwig <hch@lst.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Matthew Wilcox <willy@infradead.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Christoph Hellwig <hch@lst.de>,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license
Date: Tue, 1 Dec 2020 15:43:14 +0100 [thread overview]
Message-ID: <20201201144314.GA14256@lst.de> (raw)
In-Reply-To: <20201130075137.3b551bef@lwn.net>
On Mon, Nov 30, 2020 at 07:51:37AM -0700, Jonathan Corbet wrote:
> We could also, if we saw fit, take the position that anything that has
> been processed through the docs build is a derived product of the kernel
> and must be GPL-licensed - any dual-licensing would be stripped by that
> act. That, too, should address this concern, I think.
>
> In general I'd rather see fewer licenses in Documentation/ than more. But
> Thorsten has put a lot of effort into this work; if he wants to
> dual-license it in this way, my inclination is to accommodate him. But
> that requires getting CC-BY-4.0 accepted into the LICENSES directory.
> (That said, I believe it should go into LICENSES/dual/ rather than
> preferred/).
I agree with everything said above.
next prev parent reply other threads:[~2020-12-01 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 8:00 [PATCH v3 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten") Thorsten Leemhuis
2020-11-24 8:00 ` [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license Thorsten Leemhuis
2020-11-24 9:18 ` Christoph Hellwig
2020-11-24 9:31 ` Thorsten Leemhuis
2020-11-24 9:36 ` Christoph Hellwig
2020-11-24 10:07 ` Thorsten Leemhuis
2020-11-24 12:11 ` Matthew Wilcox
2020-11-24 13:06 ` Thorsten Leemhuis
2020-11-30 14:51 ` Jonathan Corbet
2020-12-01 14:43 ` Christoph Hellwig [this message]
2020-12-01 20:45 ` Thorsten Leemhuis
2020-11-26 10:11 ` Thorsten Leemhuis
2020-11-24 8:00 ` [PATCH v3 2/3] docs: Add a new text describing how to report bugs Thorsten Leemhuis
2020-11-24 8:00 ` [PATCH v3 3/3] docs: make reporting-bugs.rst obsolete Thorsten Leemhuis
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=20201201144314.GA14256@lst.de \
--to=hch@lst.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.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).