Repository navigation
Proposal guide: follow the ASF voting rules - #424
Merged
Merged
Conversation
The Vote section of the proposal guide pointed to the ASF rules for votes on code modification, where a -1 is a veto, and then said the project uses majority approval. Those are two different rules. State instead that Apache Cloudberry follows the ASF voting process, and that the ASF rules apply where this page differs. Describe what the project does in practice: most proposals are accepted by lazy consensus, and a vote is called only when discussion cannot resolve a disagreement. Summarize how the ASF rules apply: a vote on a proposal is a procedural vote decided by simple majority, while code changes, including the pull requests that implement a proposal, follow the rules for code modification, where a committer's -1 is a veto that is valid only with a technical justification. Rename the "Vote" stage to "Decision" in the lifecycle diagram and the section heading. Keep the 72-hour minimum, the fractional vote examples (which match the ASF page) and the consensus-seeking paragraph. Drop the "majority approval" sentence.
leborchuk
approved these changes
Nov 17, 2026
leborchuk
left a comment
There was a problem hiding this comment.
LGTM, mostly our decisions are lazy consensus, you are right
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Vote section of the proposal guide pointed to the ASF rules for votes on code modification, where a -1 is a veto, and then said the project uses majority approval. Those are two different rules.
State instead that Apache Cloudberry follows the ASF voting process, and that the ASF rules apply where this page differs. Describe what the project does in practice: most proposals are accepted by lazy consensus, and a vote is called only when discussion cannot resolve a disagreement. Summarize how the ASF rules apply: a vote on a proposal is a procedural vote decided by simple majority, while code changes, including the pull requests that implement a proposal, follow the rules for code modification, where a committer's -1 is a veto that is valid only with a technical justification.
Rename the "Vote" stage to "Decision" in the lifecycle diagram and the section heading. Keep the 72-hour minimum, the fractional vote examples (which match the ASF page) and the consensus-seeking paragraph. Drop the "majority approval" sentence.
closes: #ISSUE_Number
Change logs
Contributor's checklist
Here are some reminders before you submit your pull request: