unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Some files in Guix lack in-file license notice, does that make them GPL-3.0-only?
Date: Fri, 22 Dec 2023 17:57:47 +0100	[thread overview]
Message-ID: <a0c2429e6234e560f9db32d397d2a06ea4173708.camel@gmail.com> (raw)
In-Reply-To: <20231222172049.49531407.koszko@koszko.org>

Am Freitag, dem 22.12.2023 um 17:20 +0100 schrieb Wojtek Kosior via
Development of GNU Guix and the GNU System distribution.:
> 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.
I don't think it prevents people from assuming anything, but it may
lead people to assume that these files are not GPL'd, which may or may
not be the truth.  (There is a debate to be had to which extent you can
copyright, e.g. a dir-locals file in the first place.)

> 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?
As you point out, the proper fix would be to explicitly license them. 
This doesn't have to be the GPL, however.  For example, the FSF
recommends more permissive licenses for small amounts of text, e.g. as
typically found in READMEs.

Cheers


      reply	other threads:[~2023-12-22 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 16:20 Some files in Guix lack in-file license notice, does that make them GPL-3.0-only? Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-22 16:57 ` Liliana Marie Prikler [this message]

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=a0c2429e6234e560f9db32d397d2a06ea4173708.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=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).