Page History

...

1. Consensus: min 3 PMC +1, no PMC -1. These votes are neither Simple majority nor Super majority. Vetos are to be accompanied with (technical) rationale.
2. More information on the release process and voting is in Release Managers Onboarding.

Subproject Governance

...

1. The primary Apache Cassandra PMC remains is responsible for governing the entire C* ecosystem.
2. We recognize the sidecar as a formal subproject and do the same for future subprojects primarily targeting and dependent upon the core Apache Cassandra project
New wiki page w/inclusion, enumeration, governance update per this doc, etc
3. broad Cassandra Ecosystem.
4. The PMC will vote on inclusion of new interested subprojects using the existing procedural change vote process documented in the confluence wiki (Super majority voting: 66% of votes must be in favor to pass. Requires 50% participation of roll call).
5. New committers for these subprojects will be nominated and raised, both at inclusion as a subproject and over time. Nominations can be brought to private@cassandra.apache.org. Typically we're looking for a mix of commitment and contribution to the community and project, be it through code, documentation, presentations, or other significant engagement with the project.
6. While the commit-bit is ecosystem wide, code modification rights and voting rights (technical contribution, binding -1, CEP’sCEP's) are granted per subproject
1. Individuals are trusted to exercise prudence and only commit or claim binding votes on approved subprojects. Repeated violations of this social contract will result in losing committer status.
2. Members of the PMC have commit and voting rights on all subprojects.
7. For each subproject, we the PMC will determine a trio of pmc PMC members that will be responsible for all pmc PMC specific functions (release votes, driving CVE response, marketing, branding, policing marks, etc) not otherwise delegated to the committers in collaboration w/on the subproject committers.