??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 in your license notices. - * 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 movement, which we support, and not open source, which we don't. Do not use "Open" in your project name. - * Do not use "GNU" in your project name unless it has been officially dubbed a GNU package. See http://www.gnu.org/help/evaluation.html for information about that process; it does not happen through 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 in your license notices. * 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 movement, which we support, and not open source, which we don't. Do not use "Open" in your project name. * Do not use "GNU" in your project name unless it has been officially dubbed a GNU package. See http://www.gnu.org/help/evaluation.html for information about that process; it does not happen through savannah.
??changed: - * Project dependencies: to make the approval process quicker, give us !URLs to your dependencies, 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 in your notices, as that creates future compatibility problems. - * Consistent licensing: - * 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. - * Source files include Makefiles, scripts, and !ChangeLogs from your project. - * 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. - * No proprietary dependencies: your project - * must work on a completely free operating system. Find free replacements for your non-free dependencies. Develop and test your Java applications with GNU GCJ and Classpath, and your .Net ones with !DotGNU (or other free alternatives). http://www.gnu.org/philosophy/java-trap.html explains why. - * Runs primarily on a free operating system. Proprietary platforms such as Microsoft Windows should be considered as secondary targets, and cannot provide additional features over the ports to free !OSes. - * No storage or back-up-only project: we exist to help people develop software and technical documentation. Other hosting services offer storage space. We expect to be used primarily and not as a back-up, although we do not require all parts of the project to be hosted at Savannah. - * 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 projects with the word "open" in their name; we suggest you replace it with free instead, or use another project name of your choice. * Project dependencies: to make the approval process quicker, give us !URLs to your dependencies, 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 in your notices, as that creates future compatibility problems. * Consistent licensing: * 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. * Source files include Makefiles, scripts, and !ChangeLogs from your project. * 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. * No proprietary dependencies: your project * must work on a completely free operating system. Find free replacements for your non-free dependencies. Develop and test your Java applications with GNU GCJ and Classpath, and your .Net ones with !DotGNU (or other free alternatives). http://www.gnu.org/philosophy/java-trap.html explains why. * Runs primarily on a free operating system. Proprietary platforms such as Microsoft Windows should be considered as secondary targets, and cannot provide additional features over the ports to free !OSes. * No storage or back-up-only project: we exist to help people develop software and technical documentation. Other hosting services offer storage space. We expect to be used primarily and not as a back-up, although we do not require all parts of the project to be hosted at Savannah. * 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 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/howtogetyourprojectapprovedquickly#msg20081230074813+0...@https://savannah.gnu.org/maintenance _______________________________________________ Savannah-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/savannah-cvs
