THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
THIS IS A PROPOSED UPDATE TO THE HIVE BYLAWS. TEXT THAT IS PROPOSED TO BE REMOVED IS STRUCK THROUGH. TEXT THAT IS PROPOSED TO BE ADDED IS IN ITALICS BOLD 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.
...
A committer who makes a sustained contribution to the project may be invited to become a member of the PMC. The form of contribution is not limited to code. It can also include code review, helping out users on the mailing lists, documentation, etc.
Branch Committers
Significant, pervasive features are often developed in a speculative branch of the repository. While the initiative is active the PMC may grant commit rights on the branch to its consistent contributors. Branch committers are responsible for shepherding their feature into an active release and do not cast binding votes or vetoes in the project. Release candidates may not be made from speculative branches nor may they be based on child branches of speculative branches. Unless stated otherwise branch committers are required to follow the the same rules as regular committers.
Submodule Committers
Submodule committers are committers who are responsible for maintenance of a particular submodule of Hive. Committers on submodules have access to and responsibility for a specified subset of Hive's source code repository. Committers on submodules may cast binding votes on any technical discussion regarding that submodule.
...
All rules that apply to committers regarding transitioning to emeritus status, revocation of commit rights, and having a signed Individual Contributor License Agreement apply to submodule committers as well.
Release Manager
A Release Manager (RM) is a committer who volunteers to produce a Release Candidate according to HowToRelease. The RM shall publish a Release Plan on the dev@hive list stating the branch from which they intend to make a Release Candidate, at least one week before they do so. The RM is responsible for building consensus around the content of the Release Candidate, in order to achieve a successful Product Release vote.
Project Management Committee
...
The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache Software Foundation (VicePresident, 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.
When the current chair of the PMC resigns, the PMC votes to recommend a new chair using lazy consensus, but the decision must be ratified by the Apache board.
The chair of the PMC is rotated annually. When the chair is rotated or if the current chair of the PMC resigns, the PMC votes to recommend a new chair using Single Transferable Vote (STV) voting. See http://wiki.apache.org/general/BoardVoting for specifics. The decision must be ratified by the Apache board.
Decision Making
Within the Hive project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'lazy consensus' approval. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval.
...
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. |
...
Vetoes
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 | 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 | 37 | ||
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@hive7 | |
| New Speculative Branch | When a new speculative branch is proposed for the project. | Lazy consensus | Active PMC members | 7 | dev@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 | 67 | ||
New Committer | When a new committer is proposed for the project. | Lazy consensus | Active PMC members | 7 | ||
| New Branch Committer | When a branch committer is proposed for the project. | Lazy consensus | Active PMC members | 37 | private@hive.apache.org | |
New PMC Member | When a committer is proposed for the PMC. | Lazy consensus | Active PMC members | 37 | ||
Committer Removal | When removal of commit privileges is sought. | Consensus | Active PMC members (excluding the committer in question if a member of the PMC). | 67 | ||
PMC Member Removal | When removal of a PMC member is sought. | Consensus | Active PMC members (excluding the member in question).6 | 7 | ||
| Branch Committer Removal | When removal of commit privileges is sought. Branch committer privileges will be automatically revoked when a branch is merged to mainline or the branch becomes inactive. | Lazy consensus | Active PMC members | 7 | private@hive.apache.org | |
Modifying Bylaws | Modifying this document. | 2/3 majority | Active PMC members | 67 |