savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of The Marvin Project - savannah.nongn


From: Rudy Gevaert
Subject: Re: [Savannah-hackers] submission of The Marvin Project - savannah.nongnu.org
Date: Wed, 16 Apr 2003 05:37:01 -0400
User-agent: Mutt/1.3.28i

Hi,

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

On Wed, Apr 16, 2003 at 05:22:30AM -0400, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Olivier Ricordeau <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: The Marvin Project
> System name: marvin
> Type: non-GNU
> 
> Description:
> Marvin is a front-end for GPG which uses human voice as a key. It\'s composed 
> of two libraries (1 for signal processing, 1 for neural networks). Involved 
> languages: C and OCaml.
> Libraries are LGPL (and might become GPL ASA I have time to find out the 
> subtility between GPL and LGPL), and Marvin is GPL.
> For more info, visit http://marvinproject.org/
> 
> URL for sources (very alpha version, released only in order to get our 
> savannah account available):
> http://themarvinproject.free.fr/archives/marvin-alpha.tgz

To release your project under the GPL, you should put
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).
Put it in a file named COPYING.

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

The GPL FAQ explain the reason behind these 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,


-- 
Rudy Gevaert                address@hidden              
Web page                    http:/www.webworm.org
GNU/Linux for schools       http://www.nongnu.org/glms
Savannah hacker             http://savannah.gnu.org
                                        




reply via email to

[Prev in Thread] Current Thread [Next in Thread]