From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Proposal for Outreachy (May-August 2020)
Date: Sun, 12 Jan 2020 00:39:55 +0100 [thread overview]
Message-ID: <87tv51sgtw.fsf@gnu.org> (raw)
In-Reply-To: <20200109205409.7d69453e@kompiuter> (Jan's message of "Thu, 9 Jan 2020 20:54:09 +0100")
Hi,
Jan <tona_kosmicznego_smiecia@interia.pl> skribis:
> Don't know if this is a good place, but gnome-color-manager in this
> commit:
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=29ae18db0578bbdbc0119703f7412fe91927e80e
> has GPL2 license in the "license" field and the COPYING file also tells
> the license is GPL2, but if you check a random source file, for example
> https://gitlab.gnome.org/GNOME/gnome-color-manager/blob/master/src/gcm-brightness.c
> Then files are licensed under GPL2 or any later.
>> * This program is free software; you can redistribute it and/or modify
>> * it under the terms of the GNU General Public License as published by
>> * the Free Software Foundation; either version 2 of the License, or
>> * (at your option) any later version.
>
> I guess the license is GPLV2 then, but I'm not sure, can someone
> confirm this?
The “or any later version” wording is present in source file headers, so
it’s definitely ‘gpl2+’, not ‘gpl2’.
I fixed this one and a couple of others in
7bd000d104f79f2b1c51c48c9d01f247189f9935.
Thanks for the heads-up!
Ludo’.
next prev parent reply other threads:[~2020-01-11 23:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 11:31 Proposal for Outreachy (May-August 2020) Raghav Gururajan
2020-01-07 11:32 ` Raghav Gururajan
2020-01-07 18:06 ` Jan
2020-01-08 10:40 ` Efraim Flashner
2020-01-08 15:15 ` Jan
2020-01-08 7:06 ` Raghav Gururajan
2020-01-08 15:05 ` Jan
2020-01-08 7:42 ` Raghav Gururajan
2020-01-08 14:59 ` Jesse Gibbons
2020-01-08 15:02 ` Raghav Gururajan
2020-01-09 19:54 ` Jan
2020-01-11 23:39 ` Ludovic Courtès [this message]
2020-01-12 1:15 ` Jan
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=87tv51sgtw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).