Difference between revisions of "Policy"
(→Maintenance) |
(→Development) |
||
Line 6: | Line 6: | ||
== Development == | == Development == | ||
− | Current maintainers can be found in the [[MAINTAINERS]] file distributed with the source code. These are people who volunteer time to work on odamex and keep things running. If you wish to improve odamex without commitment, you can send us [[patches]]. We will generally expect many patches from you over a period of time before you get listed as a maintainer and are given [[svn]] access. | + | Current maintainers can be found in the [[MAINTAINERS]] file, distributed with the source code. These are people who volunteer time to work on odamex and keep things running. If you wish to improve odamex without commitment, you can send us [[patches]]. We will generally expect many patches from you over a period of time before you get listed as a maintainer and are given [[svn]] access. |
== Maintenance == | == Maintenance == |
Revision as of 19:11, 30 March 2006
We believe in rough consensus and running code.
Governance
Development
Current maintainers can be found in the MAINTAINERS file, distributed with the source code. These are people who volunteer time to work on odamex and keep things running. If you wish to improve odamex without commitment, you can send us patches. We will generally expect many patches from you over a period of time before you get listed as a maintainer and are given svn access.
Maintenance
Alongside the game development, the community administrates the following systems
- The documentation, maintained by deathz0r
- The odamex web site, maintained by Manc
- SVN repository, maintained by Manc
- Primary Master server (status), maintained by Manc
- Secondary Master server (status), maintained by Voxel
- The odamex IRC channel
- Public game servers, maintained by their respective administrators
Testing
Please find and report bugs. If you are envolved in testing, you should generally build odamex in debug mode and run it from within a debugger. Should you experience a crash, you should file a bug that includes the complete call stack (backtrace).
Views
Our community is strongly against cheating.