Join: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
imported>StephenIerodiaconou mNo edit summary |
||
| Line 4: | Line 4: | ||
First of all, you should only read this if you are interested in joining as a core developer of Arianne. If you want to do a one time contribution or periodic contributions you can use the [[Patch Tracker|http://sourceforge.net/tracker/?atid=301111&group_id=1111&func=browse]] at Sourceforge. |
First of all, you should only read this if you are interested in joining as a core developer of Arianne. If you want to do a one time contribution or periodic contributions you can use the [[Patch Tracker|http://sourceforge.net/tracker/?atid=301111&group_id=1111&func=browse]] at Sourceforge. |
||
As a core arianne developer |
As a core arianne developer <i>must</i> know arianne! He/she must understand the system which is not an easy, simple task. Fortunately, it should be the only non-simple task that you need to do in Arianne. :) |
||
== Developers == |
== Developers == |
||
| Line 22: | Line 22: | ||
OK, I shall stop the idle chat :) |
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: <br> |
First here are a few things that must be done, before you start work. They should take you a few days: <br> |
||
1) Read the following webpages |
<b>1) Read the following webpages</b> |
||
* http://arianne.sourceforge.net/index.php?arianne_url=servers/server_marauroa |
* http://arianne.sourceforge.net/index.php?arianne_url=servers/server_marauroa |
||
* http://arianne.sourceforge.net/index.php?arianne_url=content/about |
* http://arianne.sourceforge.net/index.php?arianne_url=content/about |
||
| Line 29: | Line 29: | ||
Also, please point out anything that you think may be wrong in the docs. |
Also, please point out anything that you think may be wrong in the docs. |
||
2) Read the Marauroa documentation <br> |
<b>2) Read the Marauroa documentation </b> <br> |
||
Checkout the CVS by doing: <br> |
Checkout the CVS by doing: <br> |
||
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/arianne checkout marauroa |
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/arianne checkout marauroa |
||
| Line 36: | Line 36: | ||
=== Server side: Marauroa === |
=== Server side: Marauroa === |
||
3) Browse Marauroa code <br> |
<b>3) Browse Marauroa code </b> <br> |
||
Read the code and try to understand it.<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. |
The most important parts are GameServerManager and RPServerManager, and of course the RPRuleProcessor and RPZone. |
||
| Line 42: | Line 42: | ||
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. |
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> |
<b>4) Compile and Run Marauroa </b> <br> |
||
Documenting how to compile and run it would be great. It is already explained in the readme, but it needs to be improved. |
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 === |
=== Client side: ariannexp === |
||
3) Browse ariannexp code <br> |
<b>3) Browse ariannexp code </b> <br> |
||
Read the code and try to understand it. |
Read the code and try to understand it. |
||
| Line 67: | Line 67: | ||
Point out what you don't understand, but in mailing list please. |
Point out what you don't understand, but in mailing list please. |
||
4) Compile and Run AIGladiator <br> |
<b>4) Compile and Run AIGladiator</b> <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. |
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=== |
===Client side: gladiators and mapacman=== |
||
3) Read clients code <br> |
<b>3) Read clients code </b> <br> |
||
3.1) Browse mapacman code <br> |
<b>3.1) Browse mapacman code</b> <br> |
||
Read the code and try to understand it. |
Read the code and try to understand it. |
||
3.2) Browse gladiators code <br> |
<b>3.2) Browse gladiators code </b> <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. |
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. |
Point out what you don't understand, but in mailing list please. |
||
4) Compile and Run mapacman <br> |
<b>4) Compile and Run mapacman</b> <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. |
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. |
||
| Line 88: | Line 88: | ||
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. |
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. |
||
5) Adding better graphics, better sound effects, and better animation support would be great. All of which is badly needed. |
<b>5) Adding better graphics, better sound effects, and better animation support would be great.</b> <br> All of which is badly needed. |
||