Skip to content

Proposal guide: follow the ASF voting rules - #424

Merged
tuhaihe merged 1 commit into
apache:mainfrom
tuhaihe:cc/proposal-vote-rules-c81d69
Nov 17, 2026
Merged

tuhaihe merged 1 commit into
apache:mainfrom
tuhaihe:cc/proposal-vote-rules-c81d69

Conversation

@tuhaihe

@tuhaihe tuhaihe commented Nov 17, 2026

Copy link
Copy Markdown
Member

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

Describe your change clearly, including what problem is being solved or what document is being added or updated.

Contributor's checklist

Here are some reminders before you submit your pull request:

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 leborchuk left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, mostly our decisions are lazy consensus, you are right

@tuhaihe
tuhaihe merged commit 132f93e into apache:main Nov 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants