Re: Relicensing Nautilus to GPLv3+
- From: Alexandre Franke <afranke gnome org>
- To: Carlos Soriano <csoriano protonmail com>
- Cc: "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: Re: Relicensing Nautilus to GPLv3+
- Date: Tue, 18 Jul 2017 07:56:28 +0200
On Mon, Jul 17, 2017 at 10:23 PM, Carlos Soriano via
desktop-devel-list <desktop-devel-list gnome org> wrote:
This is done now in
https://git.gnome.org/browse/nautilus/commit/?id=365ec7f7ac1cec51dc0248dd05b17cb78252a788
I don’t think that’s sufficient though. Putting a LICENSE file in the
project directory just addresses the “You should have received a copy”
provision, but doesn’t effectively place the code under that license.
You could even have several license files if parts of your project are
under different licenses.
That license file you put in your repository also states that you
should attach a notice to the program. It can take several form but
the recommended one is in the header of your source. In fact, there is
already such a notice and it claims that the software is GPLv2+
(https://git.gnome.org/browse/nautilus/tree/src/nautilus-main.c?id=365ec7f7ac1cec51dc0248dd05b17cb78252a788).
This brings us to another point: do you intend to use GPLv3 or GPLv3+?
The notice should be explicit about it (again, as suggested by the
license you copied to your project).
Cheers,
--
Alexandre Franke
GNOME Hacker & Foundation Director
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]