Changes between Version 36 and Version 37 of dev/Primer
- Timestamp:
- Mar 20, 2017, 10:51:35 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
dev/Primer
v36 v37 5 5 == 1. Mail lists == 6 6 We've got 3 major mailing lists: [[br]] 7 * [https:// admin.orxonox.net/mailman/listinfo/orxonox-announce orxonox-announce] : announcements to all who like orxonox (low traffic)8 * [https:// admin.orxonox.net/mailman/listinfo/orxonox-dev orxonox-dev] : development stuff just for us (medium traffic)9 * [https:// admin.orxonox.net/mailman/listinfo/orxonox-commit orxonox-commit] : auto-mail if the svn repository changes (high traffic during development sessions)10 * [https:// admin.orxonox.net/mailman/listinfo/tickets tickets] : notifications if a ticket is added or changed7 * [https://lists.orxonox.net/mailman/listinfo/orxonox-announce orxonox-announce] : announcements to all who like orxonox (low traffic) 8 * [https://lists.orxonox.net/mailman/listinfo/orxonox-dev orxonox-dev] : development stuff just for us (medium traffic) 9 * [https://lists.orxonox.net/mailman/listinfo/orxonox-commit orxonox-commit] : auto-mail if the svn repository changes (high traffic during development sessions) 10 * [https://lists.orxonox.net/mailman/listinfo/tickets tickets] : notifications if a ticket is added or changed 11 11 12 12 == 2. Website == … … 20 20 21 21 22 == 4. Chat, IRC == 23 You will normally find some of us on our IRC-channel [irc://irc.orxonox.net/orxonox][[br]] 24 Here we talk about Orxonox, development issues or coffee...[[br]][[br]] 25 People who prefer a secured (SSL) connection have to use port '''6668''', otherwise '''6667''' should be used 22 == 4. Infrastructure == 23 We host serveral services on our server, including svn, mail, irc, and a buildserver. You can find a description of all services and how to use them in the [wiki:ITUserManual IT User Manual]. 26 24 27 25 28 == 5. Mail aliases == 29 We are maintaining a mail server. If possible we register the following addresses for someone called Peter Muster: 30 * peter at orxonox.ethz.ch 31 * peter.muster at orxonox.ethz.ch 32 * muster at orxonox.ethz.ch 33 and forward them to your email account or to a local mailbox on the server that you are able to check out via IMAP. 34 35 36 == 6. Webpage Stats == 37 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 at: 38 * [https://admin.orxonox.net/awstats/awstats.pl awstat on orxonox server][[br]] 39 You have to log in with your subversion account. 40 41 42 == 7. Repository == 26 == 5. Repository == 43 27 Orxonox is programmed by many programmers at the same time. To synchronize the work and to make it available for all, we've got a central subversion server (subversion is a versioning system; the newer form of cvs). Most Linuxes already have svn (subversion) in their software repository (gentoo: portage tree, debian: apt-system), for Windows you need to install tortoise svn, which you can get here: http://tortoisesvn.tigris.org/ [[br]] 44 28 If you want to read more about this topic, go to: … … 56 40 57 41 58 == 8. Compiling and Running ==42 == 6. Compiling and Running == 59 43 To get Orxonox running on your system, first read [wiki:Running how to get Orxonox running]. 60 44 61 45 62 == 9. Finding your Way as a Developer ==46 == 7. Finding your Way as a Developer == 63 47 As a developer of Orxonox you will want to communicate over our [wiki:Primer#a1.Maillists mailing lists], [wiki:WikiStart the wiki], [http://forum.orxonox.net the forum] and [wiki:Primer#a4.ChatIRC IRC]. If you want to work on the project, check out the [wiki:Contribute page]. You will find the current tasks, for the next orxonox release under: 64 48 * [http://www.orxonox.net/roadmap Roadmap] … … 71 55 72 56 73 == 10. Understanding Orxonox ==57 == 8. Understanding Orxonox == 74 58 It definitely takes some time to understand the Orxonox source code. The best way to get your questions answered is to post them on the development-mailing list. Even better is to just go to the developers and ask specific questions. Once you know where to find which functions, you will want to read some more about special topics in the source files themselves: we use doxygen to comment the code, so you will find comments for every class/function. There are also [wiki:ModulesDescription module descriptions] which we are currently working on.