??changed: - * Make sure your project runs primarily on a completely free OS; - * Use a license compatible with the GNU GPL, and use the "or any later version" formulation for the GPL; - * Write a half-page technical description of your project: its goal, its programming language and its depencies (with !URLs); - * 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. - * Check your copyrights : http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html - * Check your headers : http://www.gnu.org/licenses/gpl-howto.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 level of quality for projects hosted at Savannah. * Make sure your project runs primarily on a completely free OS. * Use a license compatible with the GNU GPL, and use the "or any later version" formulation for the GPL. * Write a half-page technical description of your project: its goal, its programming language and its dependencies (with !URLs). * Give a pointer to your source code. * Apply valid copyright and license notices using our templates to each source file in your project; include a copy of the license you chose. See http://www.gnu.org/licenses/gpl-howto.html. * Refer to the "GNU/Linux operating system" instead of "Linux", which is the kernel. Advertise the free software movements, which we support, and not open source, which we don't. Do not use "Open" in your project name.
The review we do can be lengthy and difficult 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 ensures a level of quality for projects hosted at Savannah, and even more important, raises awareness of these legal and philosophical issues related to free software. ??changed: - * Project dependencies: to make the approval process quicker, give us !URLs to your depencies, and if possible direct links to their licenses - * 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 Affero GPL (since it is very likely to be 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 if it 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. * Project dependencies: to make the approval process quicker, give us !URLs to your depencies, ideally with direct links to their licenses. * 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. ??changed: - * Write appropriate copyright and license notices, at the beginning of all of your 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, that you should use to speed up the approval. More answers at http://www.gnu.org/licenses/gpl-faq.html. For the GFDL, check http://www.gnu.org/licenses/fdl-howto.html - * Include a verbatim copy of the license as plain text, do not point users to an external source to get the license; - * Moreover, do not combine code with incompatible licenses (e.g. GNU GPL'd code with CPL'd code). The GPL Compliance Lab, [EMAIL PROTECTED], may provide advice for complex cases. For Perl code, avoid the modules released under the Artistic license only; for PHP, avoid modules released under the PHP license. Or talk their authors into releasing them under licenses compatible with the GNU GPL :) * Write appropriate copyright and license notices, at the beginning of all of your 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. * Include a verbatim copy of the license in your project as plain text, do not point users to an external source to get the license. * Do not combine code with incompatible licenses (e.g., GNU GPL'd code with CPL'd code). The GPL Compliance Lab, [EMAIL PROTECTED], may provide advice for complex cases. For Perl code, avoid the modules released under the Artistic license only; for PHP, avoid modules released under the PHP license. If you want to use such modules, please ask their authors to use licenses compatible with the GNU GPL. ??changed: - * Tell people that they are using the GNU/Linux variant of the GNU operating system, and that Linux is its kernel, not the whole OS. Check http://www.gnu.org/gnu/linux-and-gnu.html and http://www.gnu.org/gnu/gnu-linux-faq.html - * We support the free software movement, and not the open source one, 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. - -If you followed these advices and prepared your project accordingly, you're likely to gain time during your project registration, and are likely to get approved after the first review. - * Tell people that they are using the GNU/Linux variant of the GNU operating system, and that Linux is its kernel, not the whole OS. See http://www.gnu.org/gnu/linux-and-gnu.html and http://www.gnu.org/gnu/gnu-linux-faq.html. * 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. If you follow all this advice and carefully prepare your project accordingly, your project is more likely to be reviewed quickly, and more likely to approved after the first review. Thank you for supporting savannah. -- forwarded from https://savannah.gnu.org/maintenance/[EMAIL PROTECTED]://savannah.gnu.org/maintenance _______________________________________________ Savannah-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/savannah-cvs
