THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Note that this implies that com
| Table of Contents |
|---|
Apache Flink Project Bylaws
This document defines the bylaws under which the Apache Flink project operates. It defines the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc.
...
Flink operates under a set of principles known collectively as the 'Apache Way'. If you are new to Apache development, please refer to the Incubator Project for more information on how Apache projects operate.
Roles and Responsibilities
Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project. The roles are defined in the following sections.
Committers
The project's Committers are responsible for the project's technical management. Committers have access to and responsibility for all of Flink's source code repository.
...
All Apache committers are required to have a signed Individual Contributor License Agreement (ICLA) on file with the Apache Software Foundation. There is a Committer FAQ which provides more details on the requirements for Committers.
Project Management Committee
The PMC is responsible to the board and the ASF for the management and oversight of Apache Flink's codebase. The responsibilities of the PMC include
...
When the current chair of the PMC resigns, the PMC votes to recommend a new chair using consensus, but the decision must be ratified by the Apache board.
Release Manager
A release manager takes responsibility for the mechanics of a release. Release managers take care of shepherding a Flink release from an initial community consensus to make it to final distribution.
...
A release starts when the project community agrees to make a release.
Decision Making
Within the Flink project, different types of decisions require different forms of approval. For example, the previous section describes several decisions which require 'consensus' approval. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval.
Voting
Decisions regarding the project are made by votes on the primary project development mailing list (dev@flink.apache.org). Where necessary, PMC voting may take place on the private Flink PMC mailing list. Votes are clearly indicated by subject line starting with [VOTE]. Votes may contain multiple items for approval and these should be clearly separated. Voting is carried out by replying to the vote mail. Voting may take three flavors
...
Only active (i.e. non-emeritus) committers and PMC members have binding votes.
Approvals
These are the types of approvals that can be sought. Different actions require different types of approvals.
Approval Type | Definition |
|---|---|
Consensus | 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 than -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 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). 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. In order to address the case of insufficient active binding voters to reach 2/3 majority, one can follow the process below to exclude a binding vote from the counting of this particular voting thread.
|
...
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.
If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in a timely manner.
Actions
Actions | Description | Approval | Binding Votes | Minimum Length (days) | 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 followed by a Lazy approval (not counting the vote of the contributor), moving to lazy majority if a -1 is received. | Active committers | 0 | JIRA or Github Pull Request (with notification sent to dev@flink.apache.org) |
| FLIP (Major Change) | A major change to the codebase that meets the FLIP criteria. | Consensus | Active committers | 3 | dev@flink.apache.org |
Release Plan | Defines the timetable and actions for a release. The plan also nominates a Release Manager. | Lazy majority | Active committers | 3 | |
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 | |
Adoption of New Codebase | Adoption of large existing external codebase. This refers to contributions big enough that potentially change the shape and direction of the project with massive restructuring and future maintenance commitment. | 2/3 majority | Active PMC members | 6 | |
New Committer | When a new committer is proposed for the project. | Consensus | Active PMC members | 3 | |
New PMC Member | When a committer is proposed for the PMC. | Consensus | Active PMC members | 3 | |
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 | |
PMC Member Removal | When removal of a PMC member is sought. | Consensus | Active PMC members (excluding the member in question). | 6 | |
Modifying Bylaws | Modifying this document. | 2/3 majority | Active PMC members | 6 |
...