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

[Mathieu Roy]

Hi,

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



address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> heeale <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: SlagPanic> 
> System name: slagpanic Type: non-GNU
> 
> Description:
> SlagPanic is an arcade-like game written in the Python programming language, 
> using the Pygame library. 
> 
> This game has been inspired by an old game, "GalsPanic".

Can you explain me the origin of the name?

> This program has been written on Gnu/Linux, but it should work on
> all the platfroms supported by Python and Pygame.
> 
> There is also a little C++ module, that require to be compiled to work. 
> However it is possible to use the Python version of this module.
> 
> The latest (non-working) version of SlagPanic compiled for Linux

"Linux" is just a kernel of a more complex system
that we like to refer to as GNU/Linux, to emphasize
the ideals of the Free Software movement.


Would you mind changing references to Linux as an OS
to GNU/Linux?

For more information, see
http://www.gnu.org/gnu/linux-and-gnu.html



> : http://members.xoom.it/heeale2/slagpanic16.tar.gz


 In order to release your project properly and unambiguously 
under the GPL, please place copyright notices and permission-to-copy
statements at the beginning of every file of source code.

In addition, if you haven't already, please copy a copy of the plain
text version of the GPL, available from
(http://www.gnu.org/licenses/gpl.txt), into a file named "COPYING".

Additional instructions are available from
http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.  To learn
why a copy of the GPL must be included with every copy of the code,
for example, go to
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude

Please register your project once more with the changes
mentioned above.  

We cannot track projects that have been answered but not approved, so
we must ask you to register the project whenever you change the
registration. Make sure to apply all changes so you need to reregister
only once.

The re-registration URL found in our acknowledgement of your earlier
registration will direct you to the proper location.

Regards,



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