linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Mehl <max.mehl@fsfe.org>
To: linux-spdx@vger.kernel.org
Subject: Implement SPDX-Copyright
Date: Fri, 24 May 2019 16:22:54 +0200	[thread overview]
Message-ID: <1558706708.m0wpla3nbm.2220@fsfe.org> (raw)

Dear all,

Great to see such a big effort going on so smoothly thanks to the
excellent collaboration here! I would like to make a small suggestion
for further improvement while we are already touching so many files in
Linux.

Currently, the REUSE and SPDX team are discussing the official
introduction of the *SPDX-Copyright* tag [^1] [^2], perhaps for SPDX 2.2
and REUSE 3.0. 

The benefit is that tools can easily detect the correct line which holds
the copyright/author/year information. As of now, there are files which
contain multiple occurrences of the word "Copyright", "©" or "(c)",
which then requires the usage of error-prone logics and patterns.

Let me give a concrete example. The following header from one of the
first patches sent around here:


  // SPDX-License-Identifier: GPL-2.0-or-later
  /*
   * Copyright (C) 2013 Pavel Machek <pavel@ucw.cz>
   * Copyright (C) 2013-2014 Aaro Koskinen <aaro.koskinen@iki.fi>


could become:


  // SPDX-License-Identifier: GPL-2.0-or-later
  /*
   * SPDX-Copyright: (C) 2013 Pavel Machek <pavel@ucw.cz>
   * SPDX-Copyright: (C) 2013-2014 Aaro Koskinen <aaro.koskinen@iki.fi>


The usage of (C) or any other copyright symbols would probably be up to
personal style or legal requirements. All this tag intends to achieve is
to make automatic tooling more robust.

What do you think? Would someone see issues with realising this
technically rather simple change in the same course of action?

Best,
Max


[^1]: https://github.com/fsfe/reuse-docs/pull/23

[^2]: https://github.com/spdx/spdx-spec/issues/122

-- 
Max Mehl - Programme Manager - Free Software Foundation Europe
Contact and information: https://fsfe.org/about/mehl | @mxmehl
Become a supporter of software freedom:  https://fsfe.org/join


             reply	other threads:[~2019-05-24 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 14:22 Max Mehl [this message]
2019-05-24 14:56 ` Implement SPDX-Copyright Greg KH
2019-05-24 15:13 ` Allison Randal
2019-05-24 17:19 ` Armijn Hemel - Tjaldur Software Governance Solutions
     [not found] ` <EB311DAA-9909-462C-AE94-7513374683CB@jilayne.com>
2019-05-31  0:26   ` J Lovejoy

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=1558706708.m0wpla3nbm.2220@fsfe.org \
    --to=max.mehl@fsfe.org \
    --cc=linux-spdx@vger.kernel.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).