From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: put appropriate license notices in source files
Date: Fri, 4 Jun 2021 15:25:52 -0500 [thread overview]
Message-ID: <20210604202552.52xlrdzdwpebnrdi@redhat.com> (raw)
In-Reply-To: <13090550.mNDUoA7e8v@omega>
On Fri, Jun 04, 2021 at 10:03:04PM +0200, Bruno Haible wrote:
> * There are many tools for copyright and license checking [2] and we make
> their job easier by avoiding unclear situations regarding what is
> "nontrivial".
> So, I added copyright and license notices to these files.
>
> [1] https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
> [2] https://wiki.debian.org/CopyrightReviewTools
Speaking of tools, should we include SPDX tags alongside the full text
of all our licenses, as that is yet another thing that aids
license-checking tools?
https://spdx.github.io/spdx-spec/appendix-V-using-SPDX-short-identifiers-in-source-files/
However, for clarity, I think it is wrong to rely on SPDX tag only in
place of the full license text; adding the one-liner SPDX should be
just that, an additional line.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-06-04 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 20:03 put appropriate license notices in source files Bruno Haible
2021-06-04 20:25 ` Eric Blake [this message]
2021-06-04 20:36 ` Paul Eggert
2021-06-04 21:02 ` Bruno Haible
2021-06-07 10:13 ` Simon Josefsson via Gnulib discussion list
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210604202552.52xlrdzdwpebnrdi@redhat.com \
--to=eblake@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).