newsNews: Licenses clarification

Latest News
Storage Array Problems posted by rwp, Sun 28 Feb 2021 06:59:48 PM UTC - 0 replies
DDoS Attack!! posted by rwp, Mon 02 Dec 2019 11:03:51 PM UTC - 0 replies
OpenSSH DSA keys Deprecated posted by rwp, Fri 21 Jun 2019 09:34:25 PM UTC - 0 replies
Version Control System Storage Back-End Maintenance Complete posted by rwp, Fri 05 Apr 2019 10:15:05 PM UTC - 0 replies
Version Control System Downtime posted by rwp, Fri 05 Apr 2019 05:52:24 PM UTC - 0 replies
[192 news in archive]

Policy on Licenses for Manuals

Item posted by Sylvain Beucler <Beuc> on Mon 13 Feb 2006 01:08:36 PM UTC.

An important aspect Savannah's rules is the practice of verifying all licenses for consistency--software licenses must be compatible with GNU GPL (version-2-or-later), so that Savannah projects, and all GNU projects, can easily build upon each other's code.

We have now recognized that the similar issue for documentation licenses needs to be addressed, and we have decided to address it in a similar fashion.  Specifically, our policy is now that new projects, and new manuals, should be released under a license compatible with the GNU Free Documentation License (current-version-or-later). Disjunctive dual licenses which include this as one option are compatible.

This policy applies to manuals written in Texinfo, and documentation which ought to be improved into such manuals. Informal materials, FAQs, and so on can be under a license compatible with either the GNU GPL or the GFDL (or both).

Existing manuals of existing non-GNU packages which are currently licensed under GPL-2-or-later can remain on Savannah with their current licenses, though we would like to change them if possible. However, existing manuals with other GFDL-incompatible licenses represent bigger problems, that we need to solve sooner or later, so we will be contacting the developers of these packages by and by.

In addition, it is vital for all documentation files to have clear statements of their licenses.  We have just discovered that some projects have not done this, and we will be contacting those projects to address the problem.

(initial post on 20060211 - updated 20060213 with clarifications)

Comments are welcome at

No messages in Policy on Licenses for Manuals


Back to the top

Powered by Savane 3.6