linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Christoph Hellwig <hch@lst.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
	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: Thu, 26 Nov 2020 11:11:37 +0100	[thread overview]
Message-ID: <f3113ffc-3fae-a53e-4aef-ffdd333a3c6a@leemhuis.info> (raw)
In-Reply-To: <20201124093658.GA13174@lst.de>

Am 24.11.20 um 10:36 schrieb Christoph Hellwig:
> On Tue, Nov 24, 2020 at 10:31:33AM +0100, Thorsten Leemhuis wrote:
>> Am 24.11.20 um 10:18 schrieb Christoph Hellwig:
>>> On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote:
>>>> For context: Patch 2 of this series adds a text to the Documentation/ directory
>>>> which (for now) uses "GPL-2.0+ OR CC-BY-4.0", as I want to make it easy and
>>>> attractive for others to base their work on it. I'm not strongly attached to
>>>> CC-BY-4.0, but it seemed like the best choice: it's designed for such usage and
>>>> afaics better than using MIT for text files.
>>> And you've not Cced me on that patch 2 or patch 3, which makes Ccing
>>> me on this pretty useless as I can't judge the context.
>> Argh, sorry, slipped through. You can find it here:
>> https://lore.kernel.org/linux-doc/2f314e58cb14c1579f843f8c72bdb4bbb83ac20a.1606137108.git.linux@leemhuis.info/
> 
> [...]  How to we make sure people
> don't accidentally end up including things they can't?

A quick question for this part of your mail; I'm getting on thin ice 
with it (hope I won't regret this), but I guess it's worth it to make me 
understand the problem better:

How is having a CC-BY text that tracks in part from GPL2 text or code in 
this case any different than having MIT code that links or includes 
GPLv2 licensed code? Both CC-BY and MIT are compatible to the GPL (see 
[1]) and the processed result is only available under GPL (see [2]).

Ciao, Thorsten

[1]
https://www.gnu.org/licenses/license-list.en.html#ccby

[2]
https://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense

  parent reply	other threads:[~2020-11-26 10:12 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
2020-12-01 20:45                 ` Thorsten Leemhuis
2020-11-26 10:11         ` Thorsten Leemhuis [this message]
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=f3113ffc-3fae-a53e-4aef-ffdd333a3c6a@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).