From: Wojtek Kosior via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Some files in Guix lack in-file license notice, does that make them GPL-3.0-only?
Date: Fri, 22 Dec 2023 17:20:49 +0100 [thread overview]
Message-ID: <20231222172049.49531407.koszko@koszko.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
Hi
at least the following files from Guix source tree
dir-locals.el
configure.ac
config-daemon.ac
bootstrap
README
have neither copyright nor license information in them. I believe it
prevents people from assuming that GPL v3 **or later** applies to those
files.
You know, the COPYING file in the source tree has just the text of
GPLv3. The permission to use a later GPL version only ever appears in
the source files themselves. But in case of the files listed above,
such extra permission is absent. As a result, all a receiver of the
source code can assume is that the terms from the COPYING file apply
here.
What should be done to fix this? Would it be welcome if I or someone
else reached out to the authors of those files to get a permission to
also use them under hypothetical later GPL versions?
Libre software projects are in general prone to this kind of licensing
ambiguities and FSFE's REUSE[1] specification seems like a good fix for
that. Would a patch that makes Guix repo REUSE-compliant be welcome?
Wojtek
[1] https://reuse.software/
-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2023-12-22 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 16:20 Wojtek Kosior via Development of GNU Guix and the GNU System distribution. [this message]
2023-12-22 16:57 ` Some files in Guix lack in-file license notice, does that make them GPL-3.0-only? Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231222172049.49531407.koszko@koszko.org \
--to=guix-devel@gnu.org \
--cc=koszko@koszko.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).