Craig Russell wrote on 10/29/24 10:25 PM:
I find it very difficult to deal with policy issues via GitHub PR comments.
Reminder: ComDev can't set *policy* for other projects.
Which I meant to raise by pointing to the official voting process
document... and realized how poorly it's written and that it doesn't
cover this case (other than as "procedural issues" as majority rule)
https://apache.org/foundation/voting.html
Technically outside the scope of ComDev, but the above document really
doesn't feel clear to a newcomer to me, which I think is part of the
underlying issue here.
Could we please have a separate thread on the dev list where we discuss issues
like:
What does consensus mean? (I think elsewhere it is lazy approval)
Excellent question. Do we have a glossary of terms somewhere? At this
point, we really should start writing one, and point out that lazy
approval is one way to gauge consensus, but it's not the only way.
Can PMC votes be vetoed (by a single -1 vote)?
Just to clarify: you mean "voting in a new PMC member"?
Can committer votes be vetoed (by a single -1 vote)?
No. That's both my opinion (a single negative vote is not necessarily a
blocker to a new committer), and because the Apache Voting Process
document specifies Vetoes for code modifications, not procedural issues.
If needed, I will volunteer to start such discussion...
If we need separate threads, go ahead, but we're already having a useful
discussion I think!
Craig
On Oct 29, 2024, at 09:35, Rich Bowen <notificati...@github.com> wrote:
@rbowen <https://github.com/rbowen> pushed 1 commit.
9409c82
<https://github.com/apache/comdev-site/commit/9409c82f87eadf519caec11f1d6ab0f663bb41a9>
vote outcome definition
--
- Shane
Member
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
