linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: 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: Mon, 30 Nov 2020 07:51:37 -0700	[thread overview]
Message-ID: <20201130075137.3b551bef@lwn.net> (raw)
In-Reply-To: <20201124121109.GY4327@casper.infradead.org>

On Tue, 24 Nov 2020 12:11:09 +0000
Matthew Wilcox <willy@infradead.org> wrote:

> > 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. 

As Thorsten points out, there are no such directives in this particular
document.  I don't really see how any such could come to be introduced; we
could add a comment at the top saying that none should be added if that
would help.

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/).

Thanks,

jon

  parent reply	other threads:[~2020-11-30 14:52 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 [this message]
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=20201130075137.3b551bef@lwn.net \
    --to=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 \
    --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).