Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 16 Nov 2017 12:46:39 +0100
From:   Jonas Oberg <jonas@fsfe.org>
To:     Thomas Gleixner <tglx@linutronix.de>
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
Message-ID: <20171116114639.GA16946@silk.coyote.org>
References: <20171112191821.240484206@linutronix.de>
 <20171112192142.614461013@linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20171112192142.614461013@linutronix.de>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.

>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


Best,

-- 
Jonas �berg
Executive Director

FSFE e.V. - keeping the power of technology in your hands. Your
support enables our work, please join us today http://fsfe.org/join

From 1584228485505897353@xxx Thu Nov 16 13:13:37 +0000 2017
X-GM-THRID: 1583890223818683742
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread