[Savannah-hackers] Re: submission of GNU Denemo, A GTK+ Frontend to Lilypond - savannah.gnu.org

[Mathieu Roy]

Hi,

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


address@hidden said:

> A package was submitted to savannah.gnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Adam Tee <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: GNU Denemo, A GTK+ Frontend to Lilypond
> System name: gnudenemo
> Type: www.gnu.org

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.


> Description: Denemo is a GUI musical score editor written in
> C/gtk+. It is intended primarily as a frontend to GNU Lilypond, but
> is adaptable to other computer-music-related purposes as well.

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


In the meantime, I check your project page on SF.net and found out
licensing issues in the CVS.

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, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt). Copy it for instance
into a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html

The GPL FAQ can also help you understand the reason behind
thoses recommendations. For example, there is an entry explaining
why the GPL requires including a copy of the GPL with
every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude


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,


-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<