Choosing a license is a serious decision and you should have already spent some time deciding what license to use, before registering this project (if you haven't, take a look at: GPL-Compatible, Free Software Licenses). If you have several components with different compatible licenses, the license of the overall project should be the most restrictive among them.

In order to make sure your Free Software is legally protected, you should write copyright notices and copying permission statements at the beginning of every single source code file and include a copy of the complete license, instead of simply giving a URL to it. If your software is released under the GNU GPL license, read the section How to Apply These Terms to Your Program.

For many legal reasons, you may not change the license of a project unless all authors agree to do so. And even in that case, versions already released under Free Software licenses will continue to apply to those versions. If you feel that you have a special case and legal capability to change the license of an existing package, we will work with you on a case-by-case basis.

If you are a webmaster of a part of the www.gnu.org website and this project is intended to create the CVS repository for that part, please select "website-only" from the licenses list below. Check that the directory you are working on is not already associated with any existing Savannah projects.