[Savannah-cvs] [How To Get Your Project Approved Quickly] (edit) or-any-later-version is in notices, not the license; source files are not derivatives

[karl]

??changed:
-    * Use a license compatible with the GNU GPL, and use the "or any later 
version" formulation for the GPL.
    * Use a license compatible with the GNU GPL, and use the "or any later 
version" formulation in your license notices.

??changed:
-    * GNU GPL-compatible license: your license should be listed as compatible 
at http://www.gnu.org/licenses/license-list.html. You can also use the GNU 
Affero GPL, since it is effectively compatible with !GPLv3. For documentation, 
we are currently clarifying exactly what licenses we accept. Of course, we 
accept our GNU Free Documentation License (and compatibles), even though is not 
compatible with the GNU GPL.  Do not use a GNU license without the "or any 
later version" wording, as that creates future compatibility problems.
    * GNU GPL-compatible license: your license should be listed as compatible 
at http://www.gnu.org/licenses/license-list.html. You can also use the GNU 
Affero GPL, since it is effectively compatible with !GPLv3. For documentation, 
we are currently clarifying exactly what licenses we accept. Of course, we 
accept our GNU Free Documentation License (and compatibles), even though is not 
compatible with the GNU GPL.  Do not use a GNU license without the "or any 
later version" wording in your notices, as that creates future compatibility 
problems.

??changed:
-          * Write appropriate copyright and license notices, at the beginning 
of all of your source files. http://www.gnu.org/licenses/gpl-howto.html and 
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html are good 
starting points to understand these issues and provide standard templates; 
please use them to speed up approval. More answers at 
http://www.gnu.org/licenses/gpl-faq.html. For the GFDL, check 
http://www.gnu.org/licenses/fdl-howto.html.
          * Write appropriate copyright and license notices, at the beginning 
of all of your source (non-derivative) files. 
http://www.gnu.org/licenses/gpl-howto.html and 
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html are good 
starting points to understand these issues and provide standard templates; 
please use them to speed up approval. More answers at 
http://www.gnu.org/licenses/gpl-faq.html. For the GFDL, check 
http://www.gnu.org/licenses/fdl-howto.html.

??changed:
-    * We support the free software movement, as opposed to "open source", 
because we are careful about ethics, that is, our primary focus is the freedom 
offered to users of free software. Further information at 
http://www.gnu.org/philosophy/free-software-for-freedom.html. As a consequence, 
we do not accept project with the word "open" in their name; we suggest you 
replace it with free instead, or use another project name of your choice.
    * We support the free software movement, as opposed to "open source", 
because we are careful about ethics, that is, our primary focus is the freedom 
offered to users of free software. Further information at 
http://www.gnu.org/philosophy/free-software-for-freedom.html. As a consequence, 
we do not accept projects with the word "open" in their name; we suggest you 
replace it with free instead, or use another project name of your choice.

--
forwarded from 
https://savannah.gnu.org/maintenance/address@hidden://savannah.gnu.org/maintenance