Differences between revisions 11 and 23 (spanning 12 versions)
Revision 11 as of 2018-11-12 07:59:44
Size: 3500
Comment: add link to binding
Revision 23 as of 2019-04-02 12:34:44
Size: 4059
Comment: link to couchdb + httpd guidelines
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

DRAFT DRAFT DRAFT

NOT ENDORSED BY ANYONE CURRENTLY
Line 31: Line 27:
Different decisions require different forms of approval. Voting when needed should be open for at [[http://www.apache.org/legal/release-policy.html#release-approval|least 72 hours]]. This is one suggested model, note that 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 bylawxs.

Different decisions require different forms of approval but community consensus is always the goal. Voting when needed should be open for at [[http://www.apache.org/legal/release-policy.html#release-approval|least 72 hours]].
Line 34: Line 32:
 - [[https://www.apache.org/foundation/glossary.html#MajorityApproval|Majority Approval]] – requires at least 3 +1 votes more +1 votes than -1 votes.  - [[https://www.apache.org/foundation/glossary.html#MajorityApproval|Majority Approval]] – requires at least 3 [[https://www.apache.org/foundation/voting.html#binding-votes|binding]] +1 votes more +1 votes than -1 votes.
Line 38: Line 36:
|| Action |||| Who can vote |||| Approval || Board approval required ||
|| Code change |||| Committer |||| Lazy Consensus |||| ||
|| Release |||| PMC |||| Majority Approval |||| ||
|| New committer |||| PMC |||| Consensus Approval or other documented method^4^ |||| ||
|| New PMC member |||| PMC |||| Consensus Approval |||| Yes^1^ ||
|| Existing committer removal |||| PMC |||| Consensus Approval |||| ||
|| Existing PMC removal |||| PMC |||| Consensus Approval |||| Yes^2^ ||
|| Change chair |||| PMC |||| Consensus Approval |||| Yes^3^ ||
|| Action |||| Who can vote |||| Approval |||| Where to vote |||| Board approval required ||
|| Code change |||| Committer |||| Lazy Consensus |||| public dev or commit list |||| ||
|| Release |||| PMC |||| Majority Approval |||| public dev list |||| ||
|| New committer |||| PMC |||| Consensus Approval or other documented method^4^ |||| private list |||| ||
|| New PMC member |||| PMC |||| Consensus Approval |||| private list|||| Yes^1^ ||
|| Existing committer removal |||| PMC |||| Consensus Approval |||| private list |||| ||
|| Existing PMC removal |||| PMC |||| Consensus Approval |||| private list |||| Yes^2^ ||
|| Change chair |||| PMC |||| Consensus Approval |||| private list |||| Yes^3^ ||
Line 51: Line 49:
^3^ Need to be [[http://www.apache.org/dev/pmc.html#newchair|approved by the board]] at the next board meeting. ^3^ Needs to be [[http://www.apache.org/dev/pmc.html#newchair|approved by the board]] at the next board meeting.

Default Project Guidelines

Introduction

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.

The Apache Foundation FAQ and How-It-Works explain the operation and background of the foundation. Terms used are defined in the ASF glossary.

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 PMC has many responsibilities including complying with ASF policies, reporting to the board, approving releases and adding new committers and PMC members.

The Chair

The chair ensures board reports are submitted and that the project's roster is up to date.

Decision Making

This is one suggested model, note that 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 bylawxs.

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.

Action

Who can vote

Approval

Where to vote

Board approval required

Code change

Committer

Lazy Consensus

public dev or commit list

Release

PMC

Majority Approval

public dev list

New committer

PMC

Consensus Approval or other documented method4

private list

New PMC member

PMC

Consensus Approval

private list

Yes1

Existing committer removal

PMC

Consensus Approval

private list

Existing PMC removal

PMC

Consensus Approval

private list

Yes2

Change chair

PMC

Consensus Approval

private list

Yes3

1 Notice must be given to board.

2 Except 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 project vote on new committers it's up to the PPMC to decide how to do it.

DefaultProjectGuidelines (last edited 2019-04-02 12:34:44 by BertrandDelacretaz)