...
- 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.
- More information on the release process and voting is in Release Managers Onboarding.
Subproject Governance:
- The primary Apache Cassandra PMC remains responsible for governing the entire C* ecosystem.
- 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
- While the commit-bit is ecosystem wide, code modification rights and voting rights (technical contribution, binding -1, CEP’s) are granted per subproject
- 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.
- Members of the PMC have commit and voting rights on all subprojects
- For each subproject, we determine a trio of pmc members that will be responsible for all pmc specific functions (release votes, driving CVE response, marketing, branding, policing marks, etc) not otherwise delegated to the committers in collaboration w/the subproject committers.