Wiki

We do not recommend that you setup new ChiliProject instances and
we urge all existing users to migrate their data to a maintained
system, e.g. Redmine. We will
provide a migration script later. In the meantime, you can use the
instructions by
Christian Daehn.

This page lists the stable core teams which handle some important aspects of the day-to-day community life of ChiliProject. These teams exist to structure our daily work and streamline communication. If you want to contribute in any of the listed areas, you could either contact the team lead or any of the members, or just start your work there. The community and the team members are very likely to get in contact with you as you start working. Always remember, we are no closed circle, but encourage everyone to contribute. There are many areas outside of Ruby coding where we need help.

To get a glimpse of who the community is, you can also take a look at our Who page, where some of the community members tell a bit about themselves.

Description: The project leader serves the function of a benevolent dictator. His responsibility is to make sure that the project keeps a clear and generally accepted direction and represents ChiliProject to the outside world. His ultimate power is to resolve deadlocks in decision processes in the community by casting an ultimate vote on the subject. However, this is only the very last resort of decision finding, by default, decisions should be made by general agreement or voting of such agreement is not possible.

Description: This team is in charge of the overall development and direction of ChiliProject. This team has check-in access to the main repository and incorporates the advice and directions from the other teams as well as makes "executive" decisions on what goes into ChiliProject.

Description: This team is in charge of collecting, refining, and organizing the documentation surrounding ChiliProject. This includes the help text within ChiliProject, as well as the guides and docs on chiliproject.org.