All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Lovejoy <opensource@jilayne.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
	Allison Randal <allison@lohutok.net>,
	linux-spdx@vger.kernel.org
Subject: Re: [Batch 5 - patch 24/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 124
Date: Sun, 2 Jun 2019 12:06:57 -0600	[thread overview]
Message-ID: <8DFC45CC-36B1-4AFC-9E28-F3FE85371461@jilayne.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1905241418410.2166@nanos.tec.linutronix.de>



> On May 24, 2019, at 6:33 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> On Fri, 24 May 2019, Kate Stewart wrote:
>> On Fri, May 24, 2019 at 12:50 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>> On Thu, 23 May 2019, Allison Randal wrote:
>>>> On 5/23/19 5:52 AM, Thomas Gleixner wrote:
>>>>> On Thu, 23 May 2019, Thomas Gleixner wrote:
>>>>>> - *
>>>>>> - * This program is distributed "as is" WITHOUT ANY WARRANTY of any kind,
>>>>>> - * whether express or implied; without even the implied warranty of
>>>>>> - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>>>>>> - * General Public License for more details.
>>>>> 
>>>>> A new variant of the scheme ...
>>>> 
>>>> Agreed on holding this one in the pile for further review. In this case,
>>>> I'd say it's not materially different than the GPL-style disclaimer,
>>>> even though it uses the BSD-style "as is" text.
>>> 
>>> Right. My gut feeling would have waved it through, but the pattern matching
>>> machine flagged it and while IANAL i started to become ANAL about these
>>> details...
>>> 
>> Agree,  in the messy set it belongs.
> 
> Which brings me to the question about these disclaimers in general. The FSF
> proposed short disclaimer says:
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
> It points to the GPL for details and that (the in kernel variant of v2)
> says:
> 
>                            NO WARRANTY
> 
>  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
> FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
> OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
> PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
> OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
> TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
> PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
> REPAIR OR CORRECTION.
> 
>  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
> WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
> REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
> INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
> OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
> TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
> YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
> PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
> POSSIBILITY OF SUCH DAMAGES.
> 
> So it would be interesting to investigate which of the modified disclaimers
> actually says something substantually different than the detailed version.
> 

yes, once we have collected the full set of additional/different disclaimers, I think the next step is to do this kind of analysis. I suspect a bunch will be fine from this perspective, and then we can focus on what to do with the ones that are truly different or extend the disclaimer in some substantive way.

Jilayne


  parent reply	other threads:[~2019-06-02 18:07 UTC|newest]

Thread overview: 101+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  9:14 [Batch 5 - patch 00/25] Batch 5 of random GPL notices/references Thomas Gleixner
2019-05-23  9:14 ` [Batch 5 - patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 101 Thomas Gleixner
2019-05-23 12:44   ` Richard Fontana
2019-05-23 22:18   ` Allison Randal
2019-05-24  1:10   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 02/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 102 Thomas Gleixner
2019-05-23 12:08   ` Richard Fontana
2019-05-23 22:18   ` Allison Randal
2019-05-24  1:10   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 03/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 103 Thomas Gleixner
2019-05-23 12:52   ` Richard Fontana
2019-05-23 22:19   ` Allison Randal
2019-05-24  1:11   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 04/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 104 Thomas Gleixner
2019-05-23 12:41   ` Richard Fontana
2019-05-23 22:20   ` Allison Randal
2019-05-24  1:12   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 05/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 105 Thomas Gleixner
2019-05-23 11:44   ` Richard Fontana
2019-05-23 22:21   ` Allison Randal
2019-05-24  1:12   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 06/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 106 Thomas Gleixner
2019-05-23 11:45   ` Richard Fontana
2019-05-23 22:21   ` Allison Randal
2019-05-24  1:13   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 07/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 107 Thomas Gleixner
2019-05-23  9:45   ` Thomas Gleixner
2019-05-23  9:14 ` [Batch 5 - patch 08/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 108 Thomas Gleixner
2019-05-23 11:54   ` Richard Fontana
2019-05-23 12:36     ` Thomas Gleixner
2019-05-23 13:06       ` Thomas Gleixner
2019-05-23  9:14 ` [Batch 5 - patch 09/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 109 Thomas Gleixner
2019-05-23  9:46   ` Thomas Gleixner
2019-05-23  9:14 ` [Batch 5 - patch 10/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 110 Thomas Gleixner
2019-05-23 12:43   ` Richard Fontana
2019-05-23 22:26   ` Allison Randal
2019-05-24  1:13   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 11/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 111 Thomas Gleixner
2019-05-23 12:43   ` Richard Fontana
2019-05-23 22:26   ` Allison Randal
2019-05-24  1:14   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 112 Thomas Gleixner
2019-05-23 12:43   ` Richard Fontana
2019-05-23 22:27   ` Allison Randal
2019-05-24  1:14   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 13/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 113 Thomas Gleixner
2019-05-23 12:07   ` Richard Fontana
2019-05-23 22:27   ` Allison Randal
2019-05-24  1:15   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 14/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 114 Thomas Gleixner
2019-05-23 12:38   ` Richard Fontana
2019-05-23 22:28   ` Allison Randal
2019-05-24 10:51   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 15/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 115 Thomas Gleixner
2019-05-23 12:42   ` Richard Fontana
2019-05-23  9:14 ` [Batch 5 - patch 16/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 116 Thomas Gleixner
2019-05-23 12:39   ` Richard Fontana
2019-05-23 22:30   ` Allison Randal
2019-05-23  9:14 ` [Batch 5 - patch 17/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 117 Thomas Gleixner
2019-05-23  9:51   ` Thomas Gleixner
2019-05-23 12:02   ` Richard Fontana
2019-05-23 12:24     ` Thomas Gleixner
2019-05-23  9:14 ` [Batch 5 - patch 18/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 118 Thomas Gleixner
2019-05-23 12:06   ` Richard Fontana
2019-05-23 22:32   ` Allison Randal
2019-05-24 10:55   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 19/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 119 Thomas Gleixner
2019-05-23 12:38   ` Richard Fontana
2019-05-23 22:33   ` Allison Randal
2019-05-24 10:56   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 20/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 120 Thomas Gleixner
2019-05-23 12:37   ` Richard Fontana
2019-05-23 22:33   ` Allison Randal
2019-05-24 10:57   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 21/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 121 Thomas Gleixner
2019-05-23 12:10   ` Richard Fontana
2019-05-23 22:34   ` Allison Randal
2019-05-24 10:58   ` Kate Stewart
2019-05-23  9:14 ` [Batch 5 - patch 22/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 122 Thomas Gleixner
2019-05-23 12:09   ` Richard Fontana
2019-05-23 22:35   ` Allison Randal
2019-05-24 10:59   ` Kate Stewart
2019-05-23  9:15 ` [Batch 5 - patch 23/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 123 Thomas Gleixner
2019-05-23 12:08   ` Richard Fontana
2019-05-23 22:36   ` Allison Randal
2019-05-24 11:00   ` Kate Stewart
2019-05-23  9:15 ` [Batch 5 - patch 24/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 124 Thomas Gleixner
2019-05-23  9:52   ` Thomas Gleixner
2019-05-23 22:42     ` Allison Randal
2019-05-24  5:50       ` Thomas Gleixner
2019-05-24 12:00         ` Kate Stewart
2019-05-24 12:33           ` Thomas Gleixner
2019-05-24 15:09             ` Allison Randal
2019-05-24 16:16               ` Thomas Gleixner
2019-05-24 17:15                 ` Allison Randal
2019-06-02 18:06             ` J Lovejoy [this message]
2019-05-23 12:51   ` Richard Fontana
2019-05-23  9:15 ` [Batch 5 - patch 25/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 125 Thomas Gleixner
2019-05-23 12:10   ` Richard Fontana
2019-05-23 22:41   ` Allison Randal
2019-05-24 11:00   ` Kate Stewart

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=8DFC45CC-36B1-4AFC-9E28-F3FE85371461@jilayne.com \
    --to=opensource@jilayne.com \
    --cc=allison@lohutok.net \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.