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.

New Committer Setup

This process is how to propose and setup a new committer to ChiliProject


  1. An existing committer (sponsor committer) proposes adding a new person as a committer.
  2. The rest of the existing committers review the new person's contributions
    • Sound judgement, the ability to communicate, and collaboration are more important than technical ability
    • Regular activity is more important than "drive by patching"
    • Above all, the person needs to enjoy working on the project with others and be friendly
  3. (?) After a few days of review, then the existing committers vote on the new member. If the vote is all "yes" then the new committer is given access. If there is a single "no", then the committers should discuss any concerns and see about reaching an agreement.


  1. If the new person is approved, the sponsor committer:
    1. adds the new person as a committer to the git repository
    2. adds the new person to the committer Role
  2. The sponsor committer emails (or otherwise contacts) the new person to let them know that they have been given commit rights


These templates can be used if you aren't sure how to approach the current committers about adding a new person.

Proposal for a new committer

Subject: Proposal for a new ChiliProject committer


I've been watching PERSON help out in the community for some time now and I would like to propose that they get commit rights.

* PERSON's ChiliProject account:
* Few major patches PERSON created that were approved:,
* Some examples of how PERSON interacts with the community: (forum links, etc)