Revision as of 10:41, 25 February 2005 view source 80.58.13.170 (talk) No edit summary ← Older edit		Revision as of 10:43, 25 February 2005 view source 80.58.13.170 (talk) No edit summary Newer edit →
Line 1: ~~= Welcome =~~ Hi and thanks for your interest in joining Arianne. Line 8 ⟶ 7: 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 == First I request that you join the [[arianne-devel mailing list\|http://lists.sourceforge.net/mailman/listinfo/arianne-devel]], so as to ease communication between us. Line 24 ⟶ 23: 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> === 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 Line 31 ⟶ 30: Also, please point out anything that you think may be wrong in the docs. === Read the Marauroa documentation === Checkout the CVS by doing: <br> cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/arianne checkout marauroa Line 37 ⟶ 36: In this module is a folder called Docs, please take some time to read them. === Server side: Marauroa === ==== Browse Marauroa code ==== Read the code and try to understand it.<br> The most important parts are GameServerManager and RPServerManager, and of course the RPRuleProcessor and RPZone. Line 44 ⟶ 43: 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. ==== Compile and Run Marauroa ==== 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 === ==== Browse ariannexp code ==== Read the code and try to understand it. Line 69 ⟶ 68: Point out what you don't understand, but in mailing list please. ==== Compile and Run AIGladiator ==== 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, mapacman and stendhal=== ==== Read clients code ==== ==== Browse mapacman code ==== Read the code and try to understand it. ==== Browse gladiators code ==== 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. ==== Compile and Run mapacman and stendhal ==== 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 90 ⟶ 89: 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. ==== Improving them ==== Adding better graphics, better sound effects, and better animation support would be great.<br> All of which is badly needed.

Join: Difference between revisions