linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Armijn Hemel - Tjaldur Software Governance Solutions 
	<armijn@tjaldur.nl>, Thomas Gleixner <tglx@linutronix.de>,
	linux-spdx@vger.kernel.org
Subject: Re: [Batch 16 patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 226
Date: Mon, 3 Jun 2019 14:36:58 +0200	[thread overview]
Message-ID: <63f9b07d-248d-c813-705c-60810b95a8c4@metux.net> (raw)
In-Reply-To: <e47edf4c-a813-77a8-bf14-eb596d140bdb@tjaldur.nl>

On 03.06.19 12:46, Armijn Hemel - Tjaldur Software Governance Solutions
wrote:

<snip>

> Yes, I think they would be. That being said, copyright notices in the
> Linux kernel are horribly out of date/inaccurate and even Git does not
> do a good job of recording these (garbage in, garbage out). Git only has
> a single "Author" field and I know of commits where the commit message
> had two authors listed and the that was added had three authors listed.
> Then there are all kinds of silly tags in the Linux kernel where it is
> absolutely unclear whether or not someone is claiming copyright or not.
> See for examples this article:
> https://www.ifosslr.org/index.php/ifosslr/article/view/121

uh, I didn't expect it to be that complicated :o
I was assuming that Author: and Signed-off-by: would be sufficient.
(okay, we'd need some git-blame counterpart that honors Signed-off-by).

> Also, author doesn't necessarily mean copyright owner, company
> affiliation also does not necessarily mean copyright is with the company
> (it depends on the work contract) and it would require a lot more
> research to find the true copyright owner.
> 
> The copyright statements also have other relevant information, such as
> years. This is relevant to find out which copyright laws were in effect
> when the code was published.

hmm, maybe we should start w/ introducing some rules for that for all
new code ?

Maybe:

Rule 1: If not stated otherwise, the Signed-Off-By indicates the signer
        claims copyright for the added or replaced lines of code.
        This only affect any lines of code that were already present
        (and unchanged) before these rules taking effect.
Rule 2: New files shall have some SPDX-Copyright: header (checkpatch
        should check for that).
Rule 3: If the SPDX-Copyright header is present, all mentioned authors
        claim copyright for the whole file, except for claims from other
        rules.
Rule 4: For existing files, SPDX-Copyright header may be added on a per-
        case basis, when actual copyright claims have been validated.
Rule 5: If the author is transferring his claims to some company, this
        company shall be mentioned in the Signed-Off-By or SPDX-
        Copyright headers.

Certainly, it will take a long time, until everything is really cleared
up, but IMHO a good start, at least for all new code.

> There was a discussion about this a few days ago (please see the list
> archive). Personally I don't see the benefit.

There already have been lawsuits on GPL violations. For such, the actual
copyright holders of the disputed code have be clear.

Personally, I wouldn't spend too much efforts in here, but I'd wish to
have some clear rules for any new contributions (in order to not making
the situation worse as it already is).


--mtx


-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

  reply	other threads:[~2019-06-03 12:37 UTC|newest]

Thread overview: 133+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  5:44 [Batch 16 patch 00/25] Batch 16 of random GPL notices/references Thomas Gleixner
2019-06-03  5:44 ` [Batch 16 patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 226 Thomas Gleixner
2019-06-03 10:11   ` Enrico Weigelt, metux IT consult
2019-06-03 10:46     ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 12:36       ` Enrico Weigelt, metux IT consult [this message]
2019-06-03 13:00         ` Greg KH
2019-06-03 17:13         ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 12:40   ` Zavras, Alexios
2019-06-03 17:53   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 02/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 227 Thomas Gleixner
2019-06-03 10:12   ` Enrico Weigelt, metux IT consult
2019-06-03 17:54   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 03/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 228 Thomas Gleixner
2019-06-03 10:14   ` Enrico Weigelt, metux IT consult
2019-06-03 12:44   ` Zavras, Alexios
2019-06-03 17:54   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 04/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 229 Thomas Gleixner
2019-06-03 10:15   ` Enrico Weigelt, metux IT consult
2019-06-03 12:46   ` Zavras, Alexios
2019-06-03 17:56   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 05/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 230 Thomas Gleixner
2019-06-03 10:17   ` Enrico Weigelt, metux IT consult
2019-06-03 12:47   ` Zavras, Alexios
2019-06-03 17:57   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 06/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 231 Thomas Gleixner
2019-06-03 10:19   ` Enrico Weigelt, metux IT consult
2019-06-03 12:50   ` Zavras, Alexios
2019-06-03 18:10     ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 07/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 232 Thomas Gleixner
2019-06-03 10:04   ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 10:20   ` Enrico Weigelt, metux IT consult
2019-06-03 12:51   ` Zavras, Alexios
2019-06-03 18:11   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 08/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 233 Thomas Gleixner
2019-06-03 10:04   ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 10:33     ` Enrico Weigelt, metux IT consult
2019-06-03 11:36       ` Greg KH
2019-06-03 12:42         ` Enrico Weigelt, metux IT consult
2019-06-04  7:14           ` Thomas Gleixner
2019-06-03 12:52   ` Zavras, Alexios
2019-06-03 18:14   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 09/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 234 Thomas Gleixner
2019-06-03 10:44   ` Enrico Weigelt, metux IT consult
2019-06-03 12:55   ` Zavras, Alexios
2019-06-03 18:15   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 10/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 235 Thomas Gleixner
2019-06-03 10:51   ` Enrico Weigelt, metux IT consult
     [not found]   ` <1559560444-31041-1-git-send-email-info@metux.net>
2019-06-03 11:14     ` [PATCH] treewide: refined: " Enrico Weigelt, metux IT consult
2019-06-03 11:35       ` Greg KH
2019-06-03 12:40         ` Enrico Weigelt, metux IT consult
2019-06-04  7:17       ` Thomas Gleixner
2019-06-04  8:31         ` Enrico Weigelt, metux IT consult
2019-06-04  8:47           ` Greg KH
2019-06-04  8:53             ` Enrico Weigelt, metux IT consult
2019-06-04  9:10               ` Greg KH
2019-06-04 13:18               ` Thomas Gleixner
2019-06-03 12:57   ` [Batch 16 patch 10/25] treewide: " Zavras, Alexios
2019-06-03 18:16   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 11/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 236 Thomas Gleixner
2019-06-03 11:22   ` Enrico Weigelt, metux IT consult
2019-06-03 12:59   ` Zavras, Alexios
2019-06-03 18:18   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 237 Thomas Gleixner
2019-06-03 11:22   ` Enrico Weigelt, metux IT consult
2019-06-03 13:00   ` Zavras, Alexios
2019-06-03 18:19   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 13/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 238 Thomas Gleixner
2019-06-03 11:23   ` Enrico Weigelt, metux IT consult
2019-06-03 15:40   ` Zavras, Alexios
2019-06-03 18:20   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 14/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 239 Thomas Gleixner
2019-06-03 11:24   ` Enrico Weigelt, metux IT consult
2019-06-03 15:41   ` Zavras, Alexios
2019-06-03 17:56   ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 18:21   ` Allison Randal
2019-06-03  5:44 ` [Batch 16 patch 15/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 240 Thomas Gleixner
2019-06-03 11:30   ` Enrico Weigelt, metux IT consult
2019-06-03 11:45     ` Greg KH
2019-06-04  7:15       ` Thomas Gleixner
2019-06-04  7:19     ` Thomas Gleixner
2019-06-03  5:44 ` [Batch 16 patch 16/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 241 Thomas Gleixner
2019-06-03 11:34   ` Enrico Weigelt, metux IT consult
2019-06-03 15:44   ` Zavras, Alexios
2019-06-03 18:05     ` Greg KH
2019-06-03 18:18       ` dmg
2019-06-03 18:23         ` dmg
2019-06-03 18:28       ` Allison Randal
2019-06-04  9:14         ` Enrico Weigelt, metux IT consult
2019-06-04  9:16           ` Greg KH
2019-07-12  2:34             ` Denver Gingerich
2019-07-12  5:23               ` Greg KH
2019-06-03  5:44 ` [Batch 16 patch 17/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 242 Thomas Gleixner
2019-06-03 11:41   ` Enrico Weigelt, metux IT consult
2019-06-03 15:47   ` Zavras, Alexios
2019-06-03 18:04     ` Greg KH
2019-06-03 18:30       ` Allison Randal
2019-06-04  9:36       ` Enrico Weigelt, metux IT consult
2019-06-03  5:44 ` [Batch 16 patch 18/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 243 Thomas Gleixner
2019-06-03 11:41   ` Enrico Weigelt, metux IT consult
2019-06-03 15:48   ` Zavras, Alexios
2019-06-03 17:57   ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 18:31   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 19/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 244 Thomas Gleixner
2019-06-03 11:42   ` Enrico Weigelt, metux IT consult
2019-06-03 15:49   ` Zavras, Alexios
2019-06-03 18:32   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 20/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 245 Thomas Gleixner
2019-06-03 11:42   ` Enrico Weigelt, metux IT consult
2019-06-03 15:49   ` Zavras, Alexios
2019-06-03 18:32   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 21/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 246 Thomas Gleixner
2019-06-03 11:43   ` Enrico Weigelt, metux IT consult
2019-06-03 15:51   ` Zavras, Alexios
2019-06-03 18:33   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 22/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 247 Thomas Gleixner
2019-06-03 12:11   ` Enrico Weigelt, metux IT consult
2019-06-03 14:24     ` Dominik Brodowski
2019-06-03 15:55   ` Zavras, Alexios
2019-06-03 18:35   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 23/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 248 Thomas Gleixner
2019-06-03 12:12   ` Enrico Weigelt, metux IT consult
2019-06-03 15:56   ` Zavras, Alexios
2019-06-03 18:00   ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-06-03 18:36   ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 24/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 249 Thomas Gleixner
2019-06-03 12:12   ` Enrico Weigelt, metux IT consult
2019-06-03 15:58   ` Zavras, Alexios
2019-06-03 18:03     ` Greg KH
2019-06-03 18:38       ` Allison Randal
2019-06-03  5:45 ` [Batch 16 patch 25/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 250 Thomas Gleixner
2019-06-03 12:13   ` Enrico Weigelt, metux IT consult
2019-06-03 15:59   ` Zavras, Alexios
2019-06-03 18:39   ` Allison Randal

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=63f9b07d-248d-c813-705c-60810b95a8c4@metux.net \
    --to=lkml@metux.net \
    --cc=armijn@tjaldur.nl \
    --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 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).