From: Matthew Wilcox <willy@infradead.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Christoph Hellwig <hch@lst.de>, 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: Tue, 24 Nov 2020 12:11:09 +0000 [thread overview]
Message-ID: <20201124121109.GY4327@casper.infradead.org> (raw)
In-Reply-To: <e424e24f-08d3-0b83-3d5b-ac500c753792@leemhuis.info>
On Tue, Nov 24, 2020 at 11:07:41AM +0100, Thorsten Leemhuis wrote:
> There is nothing special with this text, it's just that GPL is known to not
> be really ideal for documentation. That makes it hard for people to reuse
> parts of the docs outside of the kernel context, say in books or on
> websites. But it IMHO would be good for us if others could simply use this
> text as a base in such places. Otherwise they'd often face a situation where
> they had to write something completely new themselves, which afsics often
> leads to texts that can be incomplete, inaccurate or actually missleading.
> That can lead to bad bug reports, which is annoying both for reporters and
> kernel developers.
>
> That's why I came up with the thought "make the text available under more
> liberal license in addition to the GPLv2 is a good idea here". I considered
> MIT, but from what I see CC-BY 4.0 is a way better choice for documentation
> that is more known to authors.
>
> And I hope others pick up the idea when they write new documentation for the
> kernel, so maybe sooner or later it's not unusual anymore.
It's really tricky to make this work when, eg, including kernel-doc from
files which are unambiguously licensed under the GPL. I'd be happy to
sign up to licensing the files I control under GPL-with-CC-BY-SA-exception
that said something like "any documentation extracted from this file may
be distributed under the BY-SA license", but I'm not sure everybody would.
next prev parent reply other threads:[~2020-11-24 12:11 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 [this message]
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
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=20201124121109.GY4327@casper.infradead.org \
--to=willy@infradead.org \
--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=linux@leemhuis.info \
--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).