Re: [Savannah-hackers] submission of GNU Revision Control System (RCS) Docume - savannah.nongnu.org

[Rudy Gevaert]

Hi,

I'm evaluating the project you submitted for approval in Savannah.

On Thu, Jan 23, 2003 at 04:53:50PM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Aaron Hawley <address@hidden> described the package as follows:
> License: fdl
> Other License: 
> Package: GNU Revision Control System (RCS) Docume

Since your project does not seems to be part of the
GNU project yet, we cannot accept that project name
for it. Of course there are lots of non-GNU projects
with names such as gnuplot and gnuboy, but they are
not hosted in Savannah.

In the projects we host we want to keep the distinction
 between GNU and non-GNU projects, to avoid confusion.

If your project is accepted into the GNU project, you
 can change its name later on.


> System name: rcs-docs
> Type: non-GNU
> 
> Description:
> I am working on creating a manual for the GNU Revision Control System (RCS). 
> I have been only been working on writing the manual for a month, and have 
> only used RCS for only less than a year. I am writing the documentation in 
> DocBook, which makes it very portable to other documentation types, including 
> Texinfo. I wanted to create a project page to try to catch others who are 
> interested in contributing. That is likely naive thinking on my part.


Please register your project again including a URL
(could be temporary) where the source code can be found.
The description you give during project registration will be
read by Savannah administrators and not by the general Savannah
public (if you are still concerned with privacy, you can also
send me a copy of the code by e-mail).

We would like to look at your source code, even if it is still
not functional, to help you fix potential legal issues which
would be harder to find and to solve after the project gets
approved. For example, in order to release your project under
the GPL you should write copyright notices and copying
permission statements at the beginning of every source code
file, as advise in http://www.gnu.org/licenses/gpl-howto.html

Please register your project once more with the changes mentioned
above. The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times. Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,

Rudy