[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #14945] Submission of Extendable Read-O

From: Xiang Gao
Subject: [Savannah-register-public] [task #14945] Submission of Extendable Read-Only File System
Date: Fri, 15 Jun 2018 22:14:13 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Follow-up Comment #35, task #14945 (project administration):

Hi Karl,
> a license "compatible with the GNU GPL" (the phrase on both pages) means any
version of GNU GPL, present and future (that's implied in the GPL text
itself). That is why or-any-later-version is required. That is why the only
listed licenses are indeed compatible with GPLv3+. 
> In general, the idea of Savannah is to host software that can be used as
part of the GNU Project, because the FSF sponsors/owns Savannah. And that
means being compatible with GPLv3+. 
It is true that we could explicitly state that GPLv3+ compatibility is
required; I'll look into that. But it is already implicit in the words there,
and, regardless of how good we are at writing explanations, it has always been
the policy. 

OK, if that is implied in the GPL text itself, I have no idea how the Linux
kernel marked the kernel as GPLv2-only, its text is shown at

compared to

I don't have enough knowledge to get the point.

BTW I also searched a lwn text,

Actually I can only select the distribute license of the part of our code, of
course not all the Linux kernel, and in my point of view, GPL-v2 is also good
for us, but I can also accept GPL-v2+ licenses. 

Anyway, if "Savannah requires GPLv3+ compatibility" is so important, 
GPLv2 is not so freedom as a _free software_, I have to find an alternative

Gao Xiang


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]