All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jonas Oberg <jonas@fsfe.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	Andrew Morton <akpm@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Kate Stewart <kate@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christoph Hellwig <hch@lst.de>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Rob Herring <rob.herring@linaro.org>,
	Joe Perches <joe@perches.com>,
	linux-xfs@vger.kernel.org,
	Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [patch 2/7] LICENSES: Add the GPL 2.0 license
Date: Thu, 16 Nov 2017 14:12:19 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1711161410150.2191@nanos> (raw)
In-Reply-To: <20171116114639.GA16946@silk.coyote.org>

Jonas,

On Thu, 16 Nov 2017, Jonas Oberg wrote:

> Hi Thomas,
> 
> I do appreciate your work on this, it's a welcome addition!
> 
> > +SPDX-License-Identifier: GPL-2.0  // GPLv2 only
> > +SPDX-License-Identifier: GPL-2.0+ // GPLv2 or later
> 
> I am concerned about this though, as the SPDX-License-Identifier is well
> known to refer to the license of the document in which it appears, and
> it would be beneficial to avoid a situation where a tool reading this
> make the assumption the license text itself it under a particular
> license. Essentially, let's avoid overloading if we can.

Makes sense

> >From my reading, there are two intentions with the above reading:
> 
>  1) To give usage guidelines and signal that for any source file, adding
>     this exact line would be a valid license identifier, and
>  2) To make the license identifiers computer understandable such that
>     tools can be updated to validate whether source code includes a
>     license identifier which corresponds to one of the licenses in
>     LICENSES/
> 
> I'd propose to not try to do both at the same time and would propose
> a 'Valid-License-Identifier' tag to meet your second criteria, and
> a 'Usage-Guidance' tag to meet your first one. The header would then
> be:
> 
> Valid-License-Identifier: GPL-2.0
> Valid-License-Identifier: GPL-2.0+
> Usage-Guidance:
>  To use this license in source code, you can use either of the following tags
>  and values:
>  .
>  SPDX-License-Identifier: GPL-2.0   // For GPLv2 only
>  SPDX-License-Identifier: GPL-2.0+  // For GPLv2 or any later version

I can live with that.

Thanks for looking over this!

       tglx

  reply	other threads:[~2017-11-16 13:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 19:18 [patch 0/7] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-11-12 19:18 ` [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-11-12 19:54   ` Joe Perches
2017-11-12 19:57     ` Thomas Gleixner
2017-11-12 20:07   ` Jonathan Corbet
2017-11-12 20:19     ` Thomas Gleixner
2017-11-13 10:04   ` [1/7] " Charlemagne Lasse
2017-11-13 12:26     ` Thomas Gleixner
2017-11-13 12:40       ` Charlemagne Lasse
2017-11-13 13:26         ` Thomas Gleixner
2017-11-16 15:07   ` [patch 1/7] " Jonathan Corbet
2017-11-16 15:15     ` Jonas Oberg
2017-11-16 18:03       ` Thomas Gleixner
2017-11-17  7:37       ` Philippe Ombredanne
2017-11-17  8:57         ` Greg Kroah-Hartman
2017-11-17 10:53           ` Philippe Ombredanne
2017-11-17 12:29             ` Greg Kroah-Hartman
2017-11-12 19:18 ` [patch 2/7] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-11-14 18:02   ` Rob Herring
2017-11-14 19:05     ` Greg Kroah-Hartman
2017-11-16 11:46   ` Jonas Oberg
2017-11-16 13:12     ` Thomas Gleixner [this message]
2017-11-12 19:18 ` [patch 3/7] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-11-12 19:18 ` [patch 4/7] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-11-12 19:18 ` [patch 5/7] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-11-12 19:18 ` [patch 6/7] LICENSES: Add the MIT license Thomas Gleixner
2017-11-12 19:18 ` [patch 7/7] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-11-12 20:02 ` [patch 0/7] LICENSES: Add documentation and initial License files Joe Perches
2017-11-12 20:55   ` Thomas Gleixner
2017-11-13 13:54 ` Philippe Ombredanne
2017-11-14 10:15 ` Russell King - ARM Linux

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=alpine.DEB.2.20.1711161410150.2191@nanos \
    --to=tglx@linutronix.de \
    --cc=akpm@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=jonas@fsfe.org \
    --cc=kate@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rob.herring@linaro.org \
    --cc=torvalds@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.