[Savannah-hackers] Re: submission of Tobor - A robot game to learn about prog - 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
> 
> Arnaud Delobelle <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Tobor - A robot game to learn about prog
> System name: tobor
> Type: non-GNU
> 
> Description:
> Some kind of robot game: you have a robot in a maze, you need to
> program it so that it moves around and complete some task (currently
> collect the green flags).  Aim is to learn concepts of programming
> and boolean logic.
> 
> You might have one or more robots, you program them and then launch
> the \'level player\', see if they can complete the task.  If they do,
> you win If they are all destroyed, you lose.  The aim is to have
> \'level servers\' on the internet for instance, \'level players\' (ie
> client programs) that people can use to download and play levels, and
> \'level editors\' with which one could create a new level and upload it
> onto a level server.
> 
> The current version contains only a level editor/player, but it works ok.
> 
> The project is at the moment 3 files:
> level.py (defines objects and how they interact), render.py(classes for 
> rendering the level), and an \'application\' of these 2, editlevel.py, which 
> is a level player/editor in python+Tk.
> 
> They can be seen at:
> http://marooned.myby.co.uk/pytobor/level.txt
> http://marooned.myby.co.uk/pytobor/render.txt
> http://marooned.myby.co.uk/pytobor/editlevel.txt


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        <<