Difference between revisions of "Policy"
(→Maintenance) |
(→Views: Beef it up a bit, written somewhat poorly and could use even more...) |
||
| Line 24: | Line 24: | ||
== Views == | == Views == | ||
| − | + | First and foremost, our community is strongly against [[cheating]]. | |
| + | |||
| + | Secondly. we are against the "big brother" mentality. Our reach and authority only applies when using our provided services. The Odamex team is not interested in policing every server and accusing every suspect, nor are we interested in micromanaging every little bit of use of our products. It is thanks to the individuals that volunteer their time that we are able to offer what we do to you, the player. | ||
| + | |||
| + | We are FOR open discussion and understanding of issues either in the applications or in our services, and we are always willing to discuss them rationally if a problem happens to arise. We provide such services as the bug tracker, the irc bug bot, and the realtime changelog so that all may see what is really happening and how change really does occur. | ||
Revision as of 20:52, 7 April 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. 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 odamex web site, maintained by Manc
- Primary master server (status), maintained by Manc
- Secondary master server (status), maintained by Voxel
- The odamex IRC channel
- SVN repository, maintained by Manc
- The documentation, maintained by deathz0r and AlexMax
- Public game servers, maintained by their respective administrators
Testing
Please find and report bugs. If you are involved 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
First and foremost, our community is strongly against cheating.
Secondly. we are against the "big brother" mentality. Our reach and authority only applies when using our provided services. The Odamex team is not interested in policing every server and accusing every suspect, nor are we interested in micromanaging every little bit of use of our products. It is thanks to the individuals that volunteer their time that we are able to offer what we do to you, the player.
We are FOR open discussion and understanding of issues either in the applications or in our services, and we are always willing to discuss them rationally if a problem happens to arise. We provide such services as the bug tracker, the irc bug bot, and the realtime changelog so that all may see what is really happening and how change really does occur.