Update of task #6533 (project administration): Status: None => Cancelled Assigned to: None => stevenr Open/Closed: Open => Closed
_______________________________________________________ Follow-up Comment #1: Hi, I'm evaluating the project you submitted for approval in Savannah. While doing so I have noticed a few problems which are described below. Firstly, your project is not part of the GNU project, so we cannot accept its current type. We want to maintain the distinction between 'GNU' and'non-GNU' projects. If your project is approved for inclusion into Savannah, we will set it's type to 'non-GNU'. If your project is accepted into the GNU project you may change its type. You can do this by asking us. Secondly, Savannah's mission is to host free software projects, and we want the public to think of them as free software projects. A project name that says "open" will tend to lead people to think of the project as "open source" instead of "free software". We would be glad if you accept to use "free" instead of "open" in your project name. Thirdly, "Linux" is just a kernel of a more complex system that we like to refer to as GNU/Linux, to emphasize the ideals of the Free Software movement. Would you mind changing references to Linux as an OS to GNU/Linux? For more information, see http://www.gnu.org/gnu/linux-and-gnu.html. Finally, in order to release your project properly and unambiguously under the GNU GPL, please place copyright notices and permission-to-copy statements at the beginning of every copyrightable file, usually any file more than 10 lines long. In addition, if you haven't already, please include a copy of the plain text version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING". For more information, see http://www.gnu.org/licenses/gpl-howto.html. If some of your files cannot carry such notices (e.g. binary files), then you can add a README file in the same directory containing the copyright and license notices. Check http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further information. The GPL FAQ explains why these procedures must be followed. To learn why a copy of the GPL must be included with every copy of the code, for example, see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude. Please register your project once more with the changes mentioned above. Make sure to apply all changes requested, so you will only need to re-register once. The re-registration URL found in our acknowledgment of your earlier registration will direct you to the proper location where you can re-register your project. When you do re-register, please provide a tarball of your project, not an ftp directory of individual files. Regards. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/task/?6533> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/