Child pages
  • Proposed Changes to Hive Project Bylaws - August 2015

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

The chair of the PMC is rotated annuallyserves for a one year term. When the chair is rotated one year term ends, or if the current chair of the PMC resigns, the PMC votes members vote 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.

All active PMC members, including the current PMC chair, are eligible to run as candidates in the PMC chair election. All active PMC members, including the candidates, are eligible to vote in the PMC chair election.

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.

...

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

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.
Note: Such actions will also be referred to the ASF board by the PMC chair.

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.
Note: Such actions will also be referred to the ASF board by the PMC chair.

Consensus

Active PMC members (excluding the member in question).

6

private@hive.apache.org

Electing PMC ChairThe chair of the PMC serves for a one year term. When the one year term ends, or if the current chair of the PMC resigns, PMC members vote to recommend a new chair.Single Transferable VotingActive PMC members including the candidatesN/Aprivate@hive.apache.org

Modifying Bylaws

Modifying this document.

2/3 majority

Active PMC members

6

user@hive.apache.org

New Branch CommitterWhen a new branch committer is proposed for the project.Lazy ConsensusActive PMC members3private@hive.apache.org
Removal of Branch CommitterWhen a branch committer is removed from the project.ConsensusActive PMC members excluding the committer in question if they are PMC members too.6private@hive.apache.org