Join: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
Line 17:
You must choose the tasks you want to do :), I am not an assigner.
Once you have completed a task, please send it to the [[Patch Tracker|http://sourceforge.net/tracker/?atid=301111&group_id=1111&func=browse]] at Sourceforge.<br>
When you reach three(3) completed tasks I will add you into the developer list of the project. I know this is not very nice, but in the past Arianne's developer list has reached 30 members, of whom only 3 were really working on Arianne! I want the developer list to show the real active dedicated workers.
OK, I shall stop the idle chat :)
First here are a few things that must be done, before you start work. They should take you a few days:
1) Read the following webpages
* http://arianne.sourceforge.net/index.php?arianne_url=servers/server_marauroa
* http://arianne.sourceforge.net/index.php?arianne_url=content/about
Please post us your problems/queries to mailing list.<br>
Also, please point out anything that you think may be wrong in the docs.
2) Read the Marauroa documentation <br>
Checkout the CVS by doing: <br>
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/arianne checkout marauroa
In this module is a folder called Docs, please take some time to read them.
3) Browse Marauroa code <br>
Read the code and try to understand it.<br>
The most important parts are GameServerManager and RPServerManager, and of course the RPRuleProcessor and RPZone.
There are several headers that need to be documented and as you didn't write them it would be really helpful if you could point out methods that are complex to understand. Documenting some methods using Javadocs would be a great help.
4) Compile and Run Marauroa <br>
Documenting how to compile and run it would be great. It is already explained in the readme, but it needs to be improved.
=== Client side: ariannexp ===
3) Browse ariannexp code <br>
Read the code and try to understand it.
There are several headers that need to be documented and as you didn't write them it would be really helpful if you could point out methods that are complex to understand. Documenting some methods using Doxygen would be a great help.<br>
There are several folder in the ariannexp module:
* libClient
Line 58:
* TestLibGladiator
The gladiators folders are for our Gladiators game. <br>
libClient is the base for developing clients. <br>
libFramework is the basic library to wrap the arianne system into any other language. In particular libFramework is python oriented.
To understand how the code works take a look at AIGladiator. <br>
We are now focusing on developing all the games using the wrapped library in Python, check out test.py in libFramework
Point out what you don't understand, but in mailing list please.
4) Compile and Run AIGladiator <br>
Documenting how to compile and run it would be a great help. It is already explained in the readme, but it needs to be improved. The linux support is not 100% up to date, so you may have to edit the autoconf files.
===Client side: gladiators and mapacman===
3) Read clients code <br>
3.1) Browse mapacman code <br>
Read the code and try to understand it.
3.2) Browse gladiators code <br>
Read the code and try to understand it, but don't worry too much about it because it is written in blitz and it should soon be replaced ( who knows, maybe by you... ;) by version written in python.
Point out what you don't understand, but in mailing list please.
4) Compile and Run mapacman <br>
Documenting how to compile and run it would be a great help, it is already explained in the readme, but it needs to be improved. The linux support is not 100% up to date, so perhaps you need to update the autoconf files.
The documentation is not 100% synced with the code, but you will get a good idea of Marauroa and its workings.<br>
If you need help on any of these tasks remember that I am always reachable by the mailing list.<br>
I know that these kinds of tasks are not really motivating, but keep in mind: start small, start simple, start fast. Once you complete these things you will have a pretty good idea of how Marauroa runs.
| |||