Team membership

To facilitate contributing volunteer work to the project we follow a friendly admittance policy. Anyone who wishes to contribute to the project will be welcome, not only developers, but also, among others, texters, web designers, PR and marketing guys, testers, translators. People may choose their field of work upon their qualification and experience. We understand that you have a life besides open source projects and we agree that this life is more important. We don’t expect you to spend much time on this project, but we expect you to agree on our philosophy and deliver quality work. Each person who ever contributed anything will be listed on our web-site. We will regularly scan the board to eliminate those persons, who have been inactive for a considerable time. They will receive a notification and will get a chance to reason their inactivity and to get back to work. However, if the notification had no effect, people will be dismissed at the next turn. You may also be kicked out either when you are extremely incompetent (e.g. you deleted the whole CVS “in error”), or when you’re a pain in the ass (e.g. people always complain about you) or you do any act that may be considered illegal or inappropriate (e.g. using internal mail lists for spamming or selling porn or black market CDs).

Any contribution implies that you accept that the GPL will be applied to your contribution.

For developers there are minimum requirements on the qualification according to the intended group of user:

Group 1 – Students for Students

This group has the lightest requirements. It is also intended to give people a chance to become part of the open source community and gather experiences. However, you must have some experiences in programming in Java and you should learn how to use a CVS very quickly. We want to introduce you to the open source development in a team; we will not introduce you to writing a hello world program. We know that you have not much experience and we tolerate mistakes, but we expect professional work. You must be willing to comply with the code guidelines. You should also be willing to “enrich” your code with a sample test program, explanative texts or images or maybe interactive visualizations.

Group 2 – Developers for Developers

You must have considerable experience in development and design. You should be a very good team player. You must be willing to comply with the code guidelines. You should also be willing to contribute to the analysis and design process, to help defining automated minimum test criteria for verification and validation of your code and be available for support and bug fix requests.

Group 3 – Cracks for Cracks

You must have considerable experience in development and design. You must comply with the interfaces and test criteria defined in Group 2 and ensure compatibility. We strongly encourage you to also comply with the code guidelines. You must, at least, provide a short description of the aspects that the code is optimized for, possible assumptions and constraints, a list of possible off-sides / side effects and a rough guide, when this particular optimization shall be used instead of the default implementation.

The responsible admin may promote individual developers to access a higher group or degrade them to a lower group when appropriate / necessary.