Default Project Guidelines
This document defines the guidelines under which a project operates if it hasn't defined its own guidelines.
It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc.
Apache has a code of conduct that it expects its members to follow.
Roles and Responsibilities
Apache projects define a set of roles with associated rights and responsibilities.
Project Management Committee
The chair ensures board reports are submitted and that the project's roster is up to date.
This is one suggested model, note that (P)PMCs have some leeway in the way decisions are made, where vetoes apply etc., see https://httpd.apache.org/dev/guidelines.html and http://couchdb.apache.org/bylaws.html#decisions for good examples of that. For CouchDB note that nowadays the term "community guidelines" is preferred over bylaws.
Different decisions require different forms of approval but community consensus is always the goal. Voting when needed, should be open for at least 72 hours.
- Lazy Consensus – Consensus no objections (‘silence gives assent’).
Who can vote
Where to vote
Board approval required
public dev or commit list
public dev list
Consensus Approval or other documented method4
New PMC member
Existing committer removal
Existing PMC removal
1 Notice must be given to the board, or if a podling the IPMC.
2 Except for the PMC member in question. Only the board can remove PMC members.
3 Needs to be approved by the board at the next board meeting.
4 While most projects vote on new committers, it's up to the PPMC to decide how to do it.