= Orxonox Primer =
[[TracNav(TracNav/TOC)]]
Hello all!

This is a little tutorial for all new to Orxonox, a little refresh for all others:

== 1. Maillists ==
We've got 3 major mailing lists: [[br]]
  * orxonox-dev@mail.datacore.ch      [https://mail.datacore.ch/mailman/listinfo/orxonox-dev subscribe] :    development stuff just for us
  * orxonox-announce@mail.datacore.ch [https://mail.datacore.ch/mailman/listinfo/orxonox-announce subscribe] : announcements to all who like orxonox [[br]]
  * orxonox-commit@mail.datacore.ch    [https://mail.datacore.ch/mailman/listinfo/orxonox-commit subscribe] : auto-mail if the svn repos changes [[br]]


== 2. Webpage ==
We've got two web pages: [[br]]
[http://www.orxonox.net The Main Page]: This page is for all that want some quick infos [[br]]
[https://www.orxonox.net/cgi-bin/trac.cgi/wiki This Wiki]: Wiki for developers, to work more interactive [[br]]

The wiki has got some nice features like the ticket system, where you can set up development requests. The roadmap shows what the current development goals are. Anyone with a account/pass (all developers) is able to make changes to the wiki or the ticket system; just use the account from the subversion.


== 3. Forum ==
There is also a forum: https://www.orxonox.net/forum/ - we use it to exchange thoughts, drawings, materials, whatever. You will have to create your name there from then on, you will be able to post there.


== 4. Chat, IRC ==
You will find us normally on our irc-channel on: '''irc://irc.datacore.ch ''', channel: '''#orxonox'''. there we talk about Orxonox, development issues or something else...


== 5. Mailaliases ==
We are maintaining a mail server. If possible we register the following addresses for someone called Peter Muster: 
* peter at orxonox.ethz.ch
* peter.muster at orxonox.ethz.ch
* muster at orxonox.ethz.ch
and forward them to your email account or to a local mailbox on the server, that you will be able to check out via imap.


== 6. Webpage Stats: ==
We have installed a graph, that monitors the current web traffic on our server. We keep track about visits/hits on our website. you find it in: 
* [https://www.orxonox.net/awstat/awstats.pl?config=www.orxonox.net awstat on orxonox server]
You have to log in with your account (subversion/wiki).


== 7. Repository ==
Orxonox is being programmed by many programmers at the same time (at the moment we are 7 programmers). To synchronize the work and to make it available for all, we've got a central subversion server (subversion is a newer form of cvs). Most Linuxes have got svn (subversion) in their software repository (gentoo: portage tree, debian: apt-system), Windows needs  special software, that you can get from: http://tortoisesvn.tigris.org/ [[br]]
If you want to read more about this topic, you will find more infos at: 
* [http://svnbook.red-bean.com/en/1.1/index.html the official subversion guide, written very funnily]
* [http://www.onlamp.com/pub/a/onlamp/2002/10/31/subversion.html a shorter version]
You can download the code repos in linux by typing: 
{{{
valisk $ svn co https://svn.orxonox.net/orxonox orxonox
}}}
and the data repository (ships, textures, pictures, sounds, etc):
{{{
valisk $ svn co https://svn.orxonox.net/data/ data
}}}


== 8. Compiling and Running ==
To get Orxonox running on your system, first read the following articles: [wiki:Running Get it Running].


== 9. Finding your Way as a Developer ==
As a developer of orxonox (coder/modler) you will want to communicate over our mailinglists, the wiki and the irc. You will find the current tasks, for the next orxonox release under:
 * [https://www.orxonox.net/cgi-bin/trac.cgi/roadmap Roadmap]
and all tasks, that we have defined yet:
 * [https://www.orxonox.net/cgi-bin/trac.cgi/report/1 Tasks]
You will see the current changes on the orxonox source and the wiki on
the timline of our wiki:
* [https://www.orxonox.net/cgi-bin/trac.cgi/timeline timeline]
The commit messages will also be sent to your email adress, if you have registered to the orxonox-commit mailinglist


== 10. Understanding Orxonox ==
It definitly take some time to understand the Orxonox code. The best way to get your questions answered is to post them on the development-mailinglist. Even better is to just go to the developers and ask them to give you an overview... Once you know where to find which functions, you will want to read some more about special topics in the sourcefiles itself: we use doxygen to comment the code, so you will find a comment to every class/function. There is a second source of information, that we are currently working
on: [wiki:ModulesDescription module description]