A meritocratic governance model for TastyIgniter development
Using a clear, documented consensus-based governance process is a vital component for community driven development.
Using a clear, documented consensus-based governance process is a vital component for community driven development. Incorporating the organisational structures illustrated below will help ensure the TastyIgniter Project stays dynamic and vibrant throughout the project cycle.
The main objectives of the meritocratic Governance Model are twofold: To put decision powers in the hands of the community, the people who contribute to the project's success, and to make it easy to recognise way in which to get involved, to contribute and make a valuable impact.
There are five different levels at which project members can get involved, by taking on the role of User, Contributor, Approver, Maintainer.
Users are the members who have a need for the project. They are the most important members of the community as without them, the project would not exist.
Contributors provide significant input into the project, which can be done in a wide range of ways, such as programming, bug fixes, graphics, or conference organisation.
Approvers are contributors who have proven their commitment to a project, and are responsible for safeguarding the project’s success. Approvers check all code and ensure it fits with the project.
Maintainers are leaders in their area, and as owners of a component of the project code, must be aware of its state at all times and ensure the overall fit of their component.
The structure can also take a more simplified form, with three components: Team Members, Team Leader, and Project Founder.
Team Members are community members who provide significant input into the project. They have shown an understanding of its objectives and strategy and the ability to work as a team player and make valuable contributions over a period of time. They share the same responsibilities as Users and Contributors described previously.
Team Leaders are Members who have shown commitment to the project, and become recognised leaders in their particular area. They have responsibility for the quality and spirit fit of their component.
The Project Founder takes overall responsibility for leading the project, and picks the version name from a list suggested by the community.
Decision making process
Decision making typically involves the following three or four steps:
- Proposal - any community member can make a proposal to be considered by the community.
- Discussion - proposals are discussed in order to ensure approval for the contribution. Considering the shared vision of the group, a consensus decision may be reached at this stage.
- Vote - If a consensus has not been reached through discussion, a vote is taken.
- Decision - A decision is made, ideally by consensus, or by the majority vote.
This governance model allows anyone can contribute to the project, regardless of their personal skill set, as there are many ways to contribute. Join the community, then join a group on the Group Membership page from your User Control Panel.