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.
|Benevolent Dictator||Holger Just|
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 the projects 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 are made by general agreement or voting if not possible.
The position is not that of a benevolent dictator for life. The dictator has to accept the decisions of the rest of the community and act accordingly. If he isn't able to fulfill the position to general contentedness, it is possible to find a new dictator.
The important part here is:
The benevolent dictator is accepted by the community which specifically chose to be dictated by him. The governance process is structured in a way that it allows to replace the benevolent dictator if the community decides this is necessary.
Most of the time, the benevolent dictator will speak and act in the role of a normal developer. His statements and actions should be treated as such. Only when explicitly announced in conjunction with a single statement or action the special role of the benevolent dictator will be assumed.