Ginger88895
/
warzone2100
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
warzone2100/tools
History
Giel van Schijndel ccbd9c56c7 wzmasterserver.py: change the `__author__` value to "The Warzone 2100 Project" 
This used to be a list of authors.  Ego-boosting can always be performed by the AUTHORS file, no need to boost it all over the place ;-)

Suggested by Fastdeath's patch, see #1985

git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@11369 4a71c877-e1ca-e34f-864e-861f7616d084
 		2010-08-03 09:38:30 +02:00
..
3ds2pie 3ds2pie tool update. Belongs to #1553. 2010-03-20 16:17:48 +01:00
blender Update plugin status 2010-03-21 19:47:12 +01:00
conversion Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
display Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
editworld Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
gitsvngateway Bail out when pushing to the git repository fails. 2009-11-23 18:47:00 +01:00
guidecode Delete cms.php - it appears to be superfluous. 2010-02-09 20:27:50 +01:00
html2trac
…
lobby
…
map Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
masterserver wzmasterserver.py: change the `__author__` value to "The Warzone 2100 Project" 2010-08-03 09:38:30 +02:00
pietoaster Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
pygments-lexers
…
qwzm Fix (and add missing) headers to files. 2010-07-28 18:58:33 +02:00
rpl2avi rpl2avi converter by Angus Lees 2009-11-22 16:34:23 +01:00
tech-tree-chart-generator
…
tile_texpage2mipmap_tileset
…
trac/plugins Commit Trac mini plugins (which we use): 2010-02-09 20:27:49 +01:00
README
…

README 

************************************DRAFT***************************************

This directory (will) contain all sorts of Warzone 2100 related tools.

 * Each of these tools will have to be Warzone specific.
 * Every independend tool should have one directory of its own
 * No tool should depend on others for compilation or linking.
 * Each of these tools *must* have a "COPYING" file with it in its directory.
  - This file should contain the full licensing conditions applied to the entire tool.
  - If parts of this tool are licensed differently this *must* be made note of in this file.
  - Preferrably all tools should be licensed GPL (or maybe LGPL if it's easily reusable for other projects?).
  - In case the GPL is used it is best copied from /trunk/COPYING using the `svn copy` command.