From: Dirk Hohndel <dirk@hohndel.org>
To: Sean Paul <seanpaul@chromium.org>
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Add SPDX idenitifier and clarify license
Date: Wed, 2 May 2018 23:25:35 +0200 [thread overview]
Message-ID: <20180502212522.GD1309@rrmbpvm.gr8dns.org> (raw)
In-Reply-To: <20180502203330.GX73214@art_vandelay>
On Wed, May 02, 2018 at 04:33:30PM -0400, Sean Paul wrote:
> > > diff --git a/drivers/gpu/drm/ttm/ttm_agp_backend.c b/drivers/gpu/drm/ttm/ttm_agp_backend.c
> > > index 7c2485fe88d8..ea4d59eb8966 100644
> > > --- a/drivers/gpu/drm/ttm/ttm_agp_backend.c
> > > +++ b/drivers/gpu/drm/ttm/ttm_agp_backend.c
> > > @@ -1,3 +1,4 @@
> > > +/* SPDX-License-Identifier: GPL-2.0 OR MIT */
> > > /**************************************************************************
> > > *
> > > * Copyright (c) 2006-2009 VMware, Inc., Palo Alto, CA., USA
> >
> > Probably a stupid question, but can't you remove the boilerplate license now?
> >
>
> Answering my own question, there are differences between the license in the files
> and the SPDX license [1]. They are:
> - the license in the files adds "(including the next paragraph)" in the second
> paragraph
> - the files have "AND/OR ITS SUPPLIERS" in the third paragraph
> - a couple of list items are transposed and changed, but should be fine
> according to [2]
>
> So IANAL, but it seems like you should either add the SPDX and remove the
> boilerplate, or keep the boilerplate and skip the SPDX.
I am not a lawyer, either, so I asked a couple before starting this little
project...
GPL and similar license boilerplate can be replaced (and I removed it from
some files in other commits that I'm working on to clean up the files
which originated from VMware), but the MIT license is a template license
and because of that the Copyright notice is actually part of the license
and in order for people to be able to reproduce that, you aren't supposed
to remove the boilerplate.
There are a number of variations of the MIT license, a bit of googling
seems to indicate that the text that already existed in those files is the
MIT/X-Consortium flavor of the license - that's where the "including the
next paragraph" can be found, see here
https://www.x.org/releases/X11R7.7/doc/xorg-docs/License.html
SPDX appears to consider those licenses equivalent (they have a different,
older flavor of the X11 license as "X11".
Similarly, the "and/or its suppliers" language seems to have been added by some
project around X (but I wasn't able to pin down where exactly it came from), but
once again the lawyers don't appear to see an issue.
So in summary
- we need to keep the boilerplate for MIT (but not GPL)
- the text modifications should be OK (and the scanners appear to
recognize the existing text as MIT)
Not sure this answers your question.
/D
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-02 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 13:46 [PATCH] Add SPDX idenitifier and clarify license Thomas Hellstrom
2018-05-02 14:00 ` Christian König
2018-05-02 14:41 ` Thomas Hellstrom
2018-05-02 14:56 ` Dirk Hohndel
2018-05-14 16:00 ` Alex Deucher
2018-05-14 16:06 ` Christian König
2018-05-02 20:12 ` Sean Paul
2018-05-02 20:33 ` Sean Paul
2018-05-02 21:25 ` Dirk Hohndel [this message]
2018-05-03 12:46 ` Sean Paul
2018-05-03 15:41 ` Dirk Hohndel
2018-05-08 21:52 ` Alex Deucher
2018-05-08 23:11 ` Dirk Hohndel
2018-05-09 5:25 ` Thomas Hellstrom
2018-05-04 14:36 ` Christian König
2018-05-03 13:03 ` Fabio Estevam
2018-05-03 13:12 ` Christian König
2018-05-03 15:48 ` Dirk Hohndel
2018-05-03 15:53 ` Fabio Estevam
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=20180502212522.GD1309@rrmbpvm.gr8dns.org \
--to=dirk@hohndel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
--cc=thellstrom@vmware.com \
/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