THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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. These This refers to contributions are usually big enough to take many FLIPs to contribute, and will 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 |
...