I appreciate you calling that out - not a nit :). I wrote up a bunch of those 
wiki pages and helped drive those discussions and somehow have a devil of a 
time keeping it all straight. Probably due to how infrequently I need to access 
that information (in my brain or the wiki).

I *think* you're right, but I'm struggling to find where that's clarified on 
the wiki. (edit: found it):
https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/158863606/Cassandra+Project+Governance
 implies it:
>  1. While the commit-bit is ecosystem wide, code modification rights and 
> voting rights (technical contribution, binding -1, CEP's) are granted per 
> subproject 

Though it has this very clearly under the heading about committers:
>  1. Committer <https://projects.apache.org/committee.html?cassandra> votes 
> are considered “binding 
> <https://www.apache.org/foundation/voting.html#binding-votes>”

The CEP wiki article doesn't really clarify what's considered binding or not: 
https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/95652201/Cassandra+Enhancement+Proposals+CEP
> The criteria for acceptance is consensus (3 binding +1 votes and no binding 
> vetoes). The vote should remain open for 72 hours.

Ah hah! Ok - it's directly clarified here:
https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/372214307/Project+Governance+and+Operations:
> The most significant way we differ from the general ASF guidelines is that we 
> grant committers binding -1 veto rights on technical votes (see: Cassandra 
> Project Governance 
> <https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/158863606/Cassandra+Project+Governance>
>  for details; applies to both code commits and CEP's).


Anyone have any reservations w/me updating the other pages to elaborate on what 
votes are considered binding for CEP's adjacent to where we talk about the vote 
for CEP's (or linking to that other page where we denote what's considered 
binding)? Having the various qualifications about committer votes being binding 
separate from the discussion about those votes apparently leads me to confusion 
the one or two times a year I need to re-look up that information. =/

~Josh


On Wed, Jul 22, 2026, at 11:50 AM, Ekaterina Dimitrova wrote:
> Nit: Weren’t committers’ votes on CEPs binding too?
> 
> On Wed, 22 Jul 2026 at 10:02, Josh McKenzie <[email protected]> wrote:
>> __
>> Results are in:
>> 
>> +1 binding: 11
>> +1 non-binding: 6
>> -1 binding or non-binding: 0
>> 
>> With 11 binding +1, 6 non-binding +1, and no -1 votes, the vote passes.
>> 
>> Thanks everyone!
>> 
>> ----- Original message -----
>> From: Doug Rohrer <[email protected]>
>> To: [email protected]
>> Subject: Re: [VOTE] CEP-63: Merge cassandra-analytics and cassandra-sidecar 
>> into cassandra-ecosystem and refactor
>> Date: Tuesday, July 21, 2026 1:09 PM
>> 
>> +1 - thanks for taking this on!
>> 
>> Doug
>> 
>>> On Jul 20, 2026, at 12:27 PM, Isaac Reath <[email protected]> wrote:
>>> 
>>> +1 (nb)
>>> 
>>> On Mon, Jul 20, 2026 at 8:02 AM Shailaja Koppu <[email protected]> wrote:
>>>> +1
>>>> 
>>>> 
>>>>> On Jul 20, 2026, at 10:18 AM, Aleksey Yeshchenko <[email protected]> 
>>>>> wrote:
>>>>> 
>>>>> +1
>>>>> 
>>>>>> On 20 Jul 2026, at 02:17, Nate McCall <[email protected]> wrote:
>>>>>> 
>>>>>> +1 
>>>>>> 
>>>>>> On Sat, Jul 18, 2026 at 2:26 AM Josh McKenzie <[email protected]> 
>>>>>> wrote:
>>>>>>> __
>>>>>>> Hello everyone,
>>>>>>> 
>>>>>>> I would like to start voting on CEP-63: Merge cassandra-analytics and 
>>>>>>> cassandra-sidecar into cassandra-ecosystem and refactor
>>>>>>> 
>>>>>>> Proposal:
>>>>>>> https://cwiki.apache.org/confluence/spaces/CASSANDRA/pages/435028087/CEP-63+Merge+cassandra-analytics+and+cassandra-sidecar+into+cassandra-ecosystem+and+refactor+DRAFT
>>>>>>> 
>>>>>>> Discussion thread:
>>>>>>> https://lists.apache.org/thread/pqo400b24wz1p75vtt296238dcyy67qx
>>>>>>> 
>>>>>>> The vote will be open at least through next Wednesday July 22nd (3 
>>>>>>> business days), more if needed. A vote passes if there are at least 3 
>>>>>>> binding +1s and no binding vetoes.
>>>>>>> 
>>>>>>> Thanks everyone for the collaboration to get here.
>>>>>>> ~Josh
>> 

Reply via email to