linux-kernel - Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

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] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 9 Dec 2017 12:03:55 +0100
From:   Philippe Ombredanne <pombredanne@...b.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Jonathan Corbet <corbet@....net>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@....de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <rob.herring@...aro.org>,
        Jonas Oberg <jonas@...e.org>, Joe Perches <joe@...ches.com>,
        xfs <linux-xfs@...r.kernel.org>,
        Charlemagne Lasse <charlemagnelasse@...il.com>,
        Carmen Bianca Bakker <carmenbianca@...e.org>
Subject: Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe
 how to properly identify file licenses

Thomas,

On Mon, Dec 4, 2017 at 10:19 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
[...]

> +The common way of expressing the license of a source file is to add the
> +matching boiler plate text into the top comment of the file.  Due to

I would likely go with boilerplate instead. Unless you are talking
about the real flat thing [1][2] of course!

[1] http://www.virtualmuseum.ca/Exhibitions/Railway/en/ag/lg16.jpg
[2] http://whynameitthat.blogspot.be/2013/10/boiler-plate.html

> +formatting, typos etc. these "boiler plates" are hard to validate for
> +tools which are used in the context of license compliance.

Same as above, "boilerplates" might be better.

> +
> +An alternative to boilerplate text is the use of Software Package Data

And that's the correct way to go IMHO, so going boilerplate all the
way makes sense.

I shall add that while they --the boilerplates-- may be a source of
unexpected excitement for first-year law students, each time someone
sends a patch with these, there is a kitten that dies somewhere. And
we all love kitten, do we?

Thank you for using some of your precious real time writing this doc.

Jonathan,
As an English Major, does this make sense to you? (using boilerplate
as a single word, not the kitten thing)

-- 
Cordially
Philippe Ombredanne