ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

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.

« Previous - Version 18/29 (diff) - Next » - Current version
Holger Just, 2012-09-08 09:46 pm



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.

Project Lead

  • Benevolent Dictator: Eric Davis
  • 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.

Development Team

  • Team lead: TODO
  • Members: TODO
  • 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.

Issue Triage Team

  • Team lead: TODO
  • Members: TODO
  • Description: This team attacks incoming issues, tests possible bugs, and makes sure issues are filed and followed through correctly.

Documentation Team

  • Team lead: TODO
  • Members: Muntek Singh
  • 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

User Support Team

  • Team lead: TODO
  • Members: TODO
  • Description: The Forums and IRC fall within the many ways this team supports users.

Infrastructure Team

Security Team

  • Team lead: Eric Davis
  • Members:
  • Description: This team is responsible for all security concerns including vulenerability reports, disclosures, and CVE reporting.

Market Research Team

(Eric Davis: I'm not sure if this is the best name for the team. It's almost like the Community Relations team I ran in Redmine)

  • Team lead: Niels Lindenthal
  • Members: Birthe Russmeyer, Wieland Lindenthal
  • Description: The industry for project management tools is a highly competitive market with various strong players such as Microsoft, Atlassian, projectplace, basecamp and last but not least Redmine. This team is responsible for the organization of market research, user surveys and expert panels in order to find answers to the following questions:
    • What are ChiliProject's current competitors? What are ChiliProject's future competitors?
    • What are the project's strengths, weaknesses, threads and opportunities?
    • What are the reasons organizations and projects choose tools other than ChiliProject?
    • What are ChiliProject's USPs? How to communicate these reasons to the different stakeholders (project teams, management, admins etc.)?
    • Which of ChiliProject's features do organizations currently use? What are the missing features?