From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
Matthew Wilcox <mawilcox@microsoft.com>,
LKML <linux-kernel@vger.kernel.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text
Date: Mon, 23 Apr 2018 07:21:14 -0300 [thread overview]
Message-ID: <20180423072114.6d1bd99b@vento.lan> (raw)
In-Reply-To: <20180423082635.GB20868@kroah.com>
Em Mon, 23 Apr 2018 10:26:35 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:
> On Mon, Apr 23, 2018 at 09:37:14AM +0200, Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:
> > > On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:
> > > > Add the full text of the CC-BY-SA-4.0 license to the kernel tree. It was
> > > > copied directly from:
> > > >
> > > > https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
> > > >
> > > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > >
> > > As we only have 1 user of this, do we really need it?
> > >
> > > Willy, it's your file, Documentation/core-api/idr.rst that is needing
> > > this addition to the LICENSES directory. While I'm all for CC licenses
> > > for Documentation, we don't seem to be very consistent with them.
> > > Should this be the "default" license we choose for documentation for now
> > > on?
> >
> > I'm all for it. If we can agree than this should move to preferred/ and not
> > to other/
>
> Ok, that sounds good, Jon? I know you have looked into picking a decent
> license for documentation, any thoughts here?
My 2 cents here: I'm a big fan of using C-BY-SA-4.0 for documentation.
IMO, it fits better than GPL for docs. For a pure .rst file that doesn't
use kernel-doc, that is the best choice on my PoV.
Yet, I'm not sure if we can import something from a GPL (using kernel-docs)
on a CC rst file. Perhaps it needs some exemption to explicitly allow that.
Thanks,
Mauro
next prev parent reply other threads:[~2018-04-23 10:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 22:02 [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers Thomas Gleixner
2018-04-22 22:02 ` [patch 1/9] x86/jailhouse: Fix incorrect SPDX identifier Thomas Gleixner
2018-04-23 6:52 ` Jan Kiszka
2018-04-23 8:22 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2018-04-22 22:02 ` [patch 2/9] pinctrl: sh-pfc: r8a77965: Fixup " Thomas Gleixner
2018-04-23 9:17 ` Geert Uytterhoeven
2018-04-22 22:02 ` [patch 3/9] ARM: S3C24XX: Fix invalid " Thomas Gleixner
2018-04-23 15:26 ` Krzysztof Kozlowski
2018-04-24 13:27 ` Christoph Hellwig
2018-04-22 22:02 ` [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers Thomas Gleixner
2018-04-23 6:52 ` Greg Kroah-Hartman
2018-04-23 7:19 ` Hans Verkuil
2018-04-23 10:14 ` Mauro Carvalho Chehab
2018-04-24 8:01 ` Thomas Gleixner
2018-04-23 18:24 ` Kate Stewart
2018-04-22 22:02 ` [patch 5/9] LICENSES: Add X11 license Thomas Gleixner
2018-04-23 6:50 ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 6/9] LICENSES: Add CDDL-1.0 license text Thomas Gleixner
2018-04-23 6:51 ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 7/9] LICENSES: Add Apache 2.0 " Thomas Gleixner
2018-04-23 6:51 ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 8/9] LICENSES: Add CC-BY-SA-4.0 " Thomas Gleixner
2018-04-23 6:54 ` Greg Kroah-Hartman
2018-04-23 7:37 ` Thomas Gleixner
2018-04-23 8:26 ` Greg Kroah-Hartman
2018-04-23 10:21 ` Mauro Carvalho Chehab [this message]
2018-04-23 12:29 ` Jonathan Corbet
2018-04-22 22:02 ` [patch 9/9] LICENSES: Add Linux-OpenIB " Thomas Gleixner
2018-04-23 6:55 ` Greg Kroah-Hartman
2018-04-23 6:57 ` [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers Greg Kroah-Hartman
2018-04-23 7:34 ` Thomas Gleixner
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=20180423072114.6d1bd99b@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=pombredanne@nexb.com \
--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