From: Theodore Ts'o <tytso@mit.edu>
To: Joe Perches <joe@perches.com>
Cc: Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Rob Herring <rob.herring@linaro.org>,
Jonas Oberg <jonas@fsfe.org>, xfs <linux-xfs@vger.kernel.org>,
Charlemagne Lasse <charlemagnelasse@gmail.com>,
Carmen Bianca Bakker <carmenbianca@fsfe.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses
Date: Fri, 29 Dec 2017 13:54:04 -0500 [thread overview]
Message-ID: <20171229185404.GD11757@thunk.org> (raw)
In-Reply-To: <1514564399.10256.7.camel@perches.com>
On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote:
>
> Has it been legally reviewed and accepted that removal
> of the BSD license text from individual source files is
> appropriate and meets the legal requirements of
> following the BSD license on a per-file basis?
>
> And if so, who did this review?
>
> Is there any license that does not allow removal of the
> license text and does not allow simple substitution of
> the SPDX license identifier in each individual file?
The work to use SPDX lines instead of individual licenses was done by
Greg K-H in close consultation with Linux Foundation counsels, so I
would assume that they did look at that particular issue.
IANAL, but I've talked to lawyers about this issue, and in my
experience if you talk to three lawyers you will easily get six
opinions. As far as I know, none of the licenses explicitly say
copyright license must be on each file. Just that the distribution of
source must include the copyright and license statement. Exactly how
that is done is not explicitly specified.
- Ted
next prev parent reply other threads:[~2017-12-29 18:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 15:27 [patch V5 00/11] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-12-28 15:27 ` [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-12-28 22:17 ` Thomas Gleixner
2017-12-29 13:21 ` Philippe Ombredanne
2017-12-29 16:19 ` Joe Perches
2017-12-29 18:54 ` Theodore Ts'o [this message]
2017-12-29 22:17 ` Philippe Ombredanne
2017-12-30 4:15 ` Theodore Ts'o
2018-01-02 2:35 ` Andreas Dilger
2017-12-30 11:02 ` Thomas Gleixner
2018-06-12 19:03 ` Yang Li
2018-06-12 19:27 ` Thomas Gleixner
2018-06-15 16:55 ` Yang Li
2018-01-02 20:24 ` Darrick J. Wong
2017-12-28 15:27 ` [patch V5 02/11] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-12-29 13:24 ` Philippe Ombredanne
2018-01-04 16:25 ` Carmen Bianca Bakker
2018-01-04 20:50 ` Philippe Ombredanne
2017-12-28 15:27 ` [patch V5 03/11] LICENSES: Add the LGPL " Thomas Gleixner
2017-12-28 15:27 ` [patch V5 04/11] LICENSES: Add the LGPL-2.1 license Thomas Gleixner
2017-12-28 15:27 ` [patch V5 05/11] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-12-28 15:27 ` [patch V5 06/11] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-12-28 15:27 ` [patch V5 07/11] LICENSES: Add the BSD-3-clause "Clear" license Thomas Gleixner
2017-12-28 15:27 ` [patch V5 08/11] LICENSES: Add the MIT license Thomas Gleixner
2017-12-28 15:27 ` [patch V5 09/11] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-12-28 15:27 ` [patch V5 10/11] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-12-28 15:27 ` [patch V5 11/11] LICENSES: Add MPL-1.1 license Thomas Gleixner
2017-12-29 13:42 ` [patch V5 00/11] LICENSES: Add documentation and initial License files Philippe Ombredanne
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=20171229185404.GD11757@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linuxfoundation.org \
--cc=carmenbianca@fsfe.org \
--cc=charlemagnelasse@gmail.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=joe@perches.com \
--cc=jonas@fsfe.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=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).