savannah-cvs
[Top][All Lists]
Advanced

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

[Savannah-cvs] [ProjectApproval] (edit) links to more info, English twea


From: karlberry
Subject: [Savannah-cvs] [ProjectApproval] (edit) links to more info, English tweaks
Date: Thu, 07 Apr 2011 01:01:13 +0000

??changed:
-The official requirements list are located at 
https://savannah.gnu.org/register/requirements.php . This page explains the 
points in more details.
The official requirements list is at 
https://savannah.gnu.org/register/requirements.php. This page explains the 
points in more details.

??changed:
-Read them to get your project approved quickly :)
-
-* Make sure your project runs primarily on a completely free OS;
-
-* Use a license compatible with the GNU GPL;
-
-* Write a half-page technical description of your project: its goal, its 
programming language and its depencies (with URIsToTheDependencies);
-
-* Don't forget to give a pointer to the source code;
-
-* Apply valid copyright and license notices using our templates; include a 
copy of the license you chose
-
-* Refer to the GNU/Linux operating system instead of the Linux, which is the 
kernel. Advertise the free software movements, which we support, and not the 
open source one, which we don't. Do not use "Open" in your project name.
-
-The review we do can be long and tedious for both the submitter and the 
reviewer. Be sure to follow these steps; if your project doesn't comply with 
our requirements, we will ask you to make changes to your project or register 
again. This ensure a level of quality for projects hosted at Savannah.
Read them and follow them to get your project approved quickly :).

* Make sure your project runs primarily on a completely free OS.

* Use a license compatible with the GNU GPL.

* Write a half-page technical description of your project: its goal, its 
programming language and its depencies (with URIsToTheDependencies).

* Don't forget to give a pointer to the source code.

* Apply valid copyright and license notices using our templates, and include a 
copy of the license you chose.

* Refer to the GNU/Linux operating system and reserve the name "Linux" for 
referring specifically to the kernel that Linus wrote. More info: 
http://www.gnu.org/gnu/gnu-linux-faq.html.

* Talk about the free software movement, which we support, and not open source, 
which we don't. Do not use "Open" in your project name.   More info: 
http://www.gnu.org/philosophy/open-source-misses-the-point.html.

The review we do can be long and tedious for both the submitter and the 
reviewer. Be sure to follow these steps; if your project doesn't comply with 
our requirements, we will ask you to make changes to your project or register 
again. This ensure a consistent level of quality and policy for projects hosted 
at Savannah.

??changed:
-* WhyLegalChecksBeforeRelease: solid legal basis are one of free software's 
strengths
* WhyLegalChecksBeforeRelease: solid legal basis are one of free software's 
strengths.

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



reply via email to

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