savannah-hackers
[Top][All Lists]
Advanced

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

Re: [Savannah-hackers] submission of Agora - savannah.nongnu.org


From: Rudy Gevaert
Subject: Re: [Savannah-hackers] submission of Agora - savannah.nongnu.org
Date: Wed, 22 Jan 2003 18:20:58 -0500
User-agent: Mutt/1.3.28i

Hi,

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

On Wed, Jan 22, 2003 at 04:43:03PM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Yann Hodique <address@hidden> described the package as follows:
> License: gpl

You have removed the last section, titled "How to Apply
These Terms to Your New Programs", from the GPL license.
Please use a complete verbatim copy of the GPL license, as found
in http://www.gnu.org/licenses/gpl.txt

The GPL license can only be copied in verbatim form. The last section
is also very important and makes part of the license.


> Other License: 
> Package: Agora
> System name: agora
> Type: non-GNU
> 
> Description:
> The aim of Agora is to create a portable, polymorph, interactivity place.
> The chosen architecture is plugins-oriented.
> 
> The main property we\'ll keep in mind is that any part of the program should 
> be added/removed/replaced without disturbing the rest of the system.
> Planned applications for the server include for now a chat server (which was 
> the actual first idea) and a little Diplomacy-like online game.
> 
> We will use standard C++ to write the core application, as well as the 
> experimental plugins, with respect of POSIX specifications
> 
> Current source code is available at 
> http://guillaume.denry.free.fr/agora/agora.tar.gz
> 
> Other Software Required:
> 

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,

Rudy




reply via email to

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