savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of Allegro Sprite Editor - savannah.n


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of Allegro Sprite Editor - savannah.nongnu.org
Date: 22 Jun 2003 19:46:20 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> David A. Capello <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Allegro Sprite Editor
> System name: ase
> Type: non-GNU
> 
> Description:
> ASE is a program to draw images. It includes a couple of LGPL libraries (RAP 
> and RLIB), and will be released with Lua (www.lua.org) code embedded, but ASE 
> code is distributed under GPL terms. The binaries will be available for 
> GNU/Linux, Windows, and DOS.

Wouldn't it be more appropriate to set up a project for each library?
They can be useful to people not especially interested in ASE, no?

> The project is registered in SourceForge, but I have planned pass it
> to Savannah. You can get more information about it and the source
> code from: http://ase.sourceforge.net/

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,


-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english




reply via email to

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