Apache Hive Project Bylaws
THIS IS A PROPOSED UPDATE TO THE HIVE BYLAWS REGARDING CODE CHANGES THAT IS ADOPTED BY HIVE. TEXT THAT IS PROPOSED TO BE REMOVED IS STRUCK THROUGH. CODE THAT IS PROPOSED TO BE ADDED IS IN ITALICS.
Table of Contents |
---|
This document defines the bylaws under which the Apache Hive project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc.
...
Membership of the PMC can be revoked by ana unanimous vote of all the active PMC members other than the member in question.
The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (VicePresidentVice President, Apache Hive) and has primary responsibility to the board for the management of the projects within the scope of the Hive PMC. The chair reports to the board quarterly on developments within the Hive project.
...
Approval Type | Definition |
---|---|
Consensus | For this to pass, all voters with binding votes must vote and there can be no binding vetoes (-1). Consensus votes are rarely required due to the impracticality of getting all eligible voters to cast a vote. |
Lazy Consensus | Lazy consensus requires 3 binding +1 votes and no binding vetoes. |
Lazy Majority | A lazy majority vote requires 3 binding +1 votes and more binding +1 votes that -1 votes. |
Lazy Approval | An action with lazy approval is implicitly allowed unless a -1 vote is received, at which time, depending on the type of action, either lazy majority or lazy consensus approval must be obtained. |
2/3 Majority | Some actions require a 2/3 majority of active committers or PMC members to pass. Such actions typically affect the foundation of the project (e.g. adopting a new codebase to replace an existing product). The higher threshold is designed to ensure such changes are strongly supported. To pass this vote requires at least 2/3 of binding vote holders to vote +1. |
VetosVetoes
A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the reasons for the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid.
...
Actions | Description | Approval | Binding Votes | Minimum Length | Mailing List |
---|---|---|---|---|---|
Code Change | A change made to a codebase of the project and committed by a committer. This includes source code, documentation, website content, etc. | one +1 from a committer who has not authored the patch followed by a Lazy approval (not counting the vote of the contributor), moving to lazy majority if a -1 is received. Minor issues (e.g. typos, code style issues, JavaDoc changes. At committer's discretion) can be committed after soliciting feedback/review on the mailing list and not receiving feedback within 2 days. | Active committers | 1 | JIRA (dev@hive.apache.org) |
Release Plan | Defines the timetable and actions for a release. The plan also nominates a Release Manager. | Lazy majority | Active committers | 3 | user@hive.apache.org |
Product Release | When a release of one of the project's products is ready, a vote is required to accept the release as an official release of the project. | Lazy Majority | Active PMC members | 3 | user@hive.apache.org |
Adoption of New Codebase | When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue. This also covers the creation of new sub-projects and submodules within the project. | 2/3 majority | Active PMC members | 6 | dev@hive.apache.org |
New Committer | When a new committer is proposed for the project. | Lazy consensus | Active PMC members | 3 | private@hive.apache.org |
New PMC Member | When a committer is proposed for the PMC. | Lazy consensus | Active PMC members | 3 | private@hive.apache.org |
Committer Removal | When removal of commit privileges is sought. | Consensus | Active PMC members (excluding the committer in question if a member of the PMC). | 6 | private@hive.apache.org |
PMC Member Removal | When removal of a PMC member is sought. | Consensus | Active PMC members (excluding the member in question). | 6 | private@hive.apache.org |
Modifying Bylaws | Modifying this document. | 2/3 majority | Active PMC members | 6 | user@hive.apache.org |
New Branch Committer | When a new branch committer is proposed for the project. | Lazy Consensus | Active PMC members | 3 | private@hive.apache.org |
Removal of Branch Committer | When a branch committer is removed from the project. | Consensus | Active PMC members excluding the committer in question if they are PMC members too. | 6 | private@hive.apache.org |