For each role listed below you may find more details in Structure and Roles section.
Anyone can become a member.
Users who continue to engage with the project and the community can become contributors.
Community members who wish to take an active part in the community can become a contributor. All contributions are submitted as patches that are validated by committers or project maintainers.
Contributors engage with the project through forum, blog, projects, and mailing lists. There is no expectation of commitment, no specific skill requirements and no selection process.
Contributors can be nominated as committers as soon as they prove their attachment and willingness to help in reaching goals.
Committers are community members dedicated to the continuous development. Committer-ship allows contributors to easily carry on with project related activities by giving them direct access to project resources. That is, they can make changes directly to project outputs, without having to submit changes via patches.
Anyone can become a committer if they show willingness and ability to participate in the project as a team player.
Nominees may decline their appointment as a committer. This role allows people to contribute more easily.
Committership is a privilege, not a right. This is earned and can be removed in extreme circumstances. However, under normal circumstances committership exists for as long as the committer wishes to continue engaging with the project.
A committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become project maintainer, and thus part of the Technical Committee.
The technical committee consists of all project maintainers. Its main role is to set a vision and strategy for the community, as a whole, especially from the technical and business point of view, to decide upon matters that cannot reach a consensus among the members of the community. Its members are expected to review code contributions, participate in strategic planning, approve changes to the governance model and manage the copyrights within the project outputs.
Members of the technical committee do not have significant authority over other members of the community, although they are to vote on new committers. They have access to the project’s private mailing list and its archives. This list is used for sensitive issues, such as votes for new committers and legal matters that cannot be discussed in public. It is never used for project management or planning.
The technical committee leader is voted for by its memnbers. Once someone has been appointed leader, he/ she remains in that role until choosing to retire, is removed by a majority vote. He/ she has no additional authority over other members of the technical committee: the role is one of coordinator and facilitator, but also to ensure that all governance processes are adhered to.
This is a group of decision makers with the role of a moderator: the instrumental inspirational authority, expected to draw both the development vision and the guidelines of the community.