[Savannah-hackers] Re: submission of Battle for Wesnoth - 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
> 
> David White <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Battle for Wesnoth
> System name: wesnoth
> Type: non-GNU
> 
> Description:
> A turn-based strategy game with a fantasy theme, written in C++ and using the 
> Simple Directmedia Layer (SDL) library.
> 
> The game includes an attractive graphical interface, and sound and music 
> support. Network support is planned in the future.
> 
> The latest stable version of the source code is available at 
> http://wesnoth.whitevine.net/files/wesnoth-0.4.tar.gz

The license does not contain the last section, titled
"How to Apply These Terms to Your New Programs".  

Please use a complete verbatim copy of the license, which may be found
at http://www.gnu.org/licenses/gpl.txt,
http://www.gnu.org/licenses/lgpl.txt or
http://www.gnu.org/licenses/fdl.txt 

The license must be copied verbatim and in its entirety.  


 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