linux-kernel - Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 10 Dec 2017 20:00:11 +0100
From:   Philippe Ombredanne <pombredanne@...b.com>
To:     Jonathan Cameron <jic23@...nel.org>
Cc:     harinath Nampally <harinath922@...il.com>,
        Martin Kepplinger <martink@...teo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Hartmut Knaack <knaack.h@....de>, linux-iio@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

On Sun, Dec 10, 2017 at 4:08 PM, Jonathan Cameron <jic23@...nel.org> wrote:
> On Sat, 18 Nov 2017 23:23:57 -0500
> harinath Nampally <harinath922@...il.com> wrote:
>
>> > This replaces the custom license information text with the appropriate
>> > SPDX identifier. While the information here stays the same, it is easier
>> > to read.
>> > Signed-off-by: Martin Kepplinger <martink@...teo.de>
>> > Acked-by: Peter Meerwald-Stadler <pmeerw@...erw.net>
>> Acked-by: Harinath Nampally <harinath922@...il.com>
>
> Applied.  I still not totally sure that the intent of introducing SPDX
> specifiers was to replace rather than supplement the license text.
> It's been pointed out for instance that some of the BSD licenses have
> explicit names in the text relevant to a particular file.  For GPL v2
> that isn't the case though so I suppose this one does no harm.

Thanks!
There might be indeed a few corner cases that would require some
discussions and the best way would be to have a proper sign off of the
authors when possible in these cases (or all cases)
But to me at least, reducing the boilerplate to the max (such as
replacing 50 lines of legalese with a single SPDX id line) is a big
boost of content/noise ratio that we should thrive for.
-- 
Cordially
Philippe Ombredanne