I'm told my email came through with a white background and gray font. Apologies for that; contortions between editors and trying to get my email client to format consistently after copy/paste led to some kind of pathologically bad case.
Also: you should be using a dark background on your browser to save your eyes. Part of why I didn't realize. :) (It's on the internet so it must be true: https://www.wired.co.uk/article/dark-mode-chrome-android-ios-science) ~Josh On Thu, Jan 26, 2023, at 6:57 PM, C. Scott Andreas wrote: > Josh and all PMC members, thank you for your work on this! > > Supportive of the changes and grateful to have scaffolding in place to > accommodate current/incoming subprojects. > > – Scott > >> On Jan 26, 2023, at 1:21 PM, Josh McKenzie <jmcken...@apache.org> wrote: >> >> >> The Cassandra PMC is pleased to announce that we're evolving our governance >> procedures to better foster subprojects under the Cassandra Ecosystem's >> umbrella. Astute observers among you may have noticed that the Cassandra >> Sidecar is already a subproject of Apache Cassandra as of CEP-1 >> (https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652224) >> and Cassandra-14395 (https://issues.apache.org/jira/browse/CASSANDRASC-24), >> however up until now we haven't had any structure to accommodate raising >> committers on specific subprojects or clarity on the addition or governance >> of future subprojects. >> >> Further, with the CEP for the driver donation in motion >> (https://docs.google.com/document/d/1e0SsZxjeTabzrMv99pCz9zIkkgWjUd4KL5Yp0GFzNnY/edit#heading=h.xhizycgqxoyo), >> the need for a structured and sustainable way to expand the Cassandra >> Ecosystem is pressing. >> >> We'll document these changes in the confluence wiki as well as the sidecar >> as our first formal subproject after any discussion on this email thread. >> The new governance process is as follows: >> ------------------------------------- >> >> Subproject Governance >> 1. The Apache Cassandra PMC is responsible for governing the broad Cassandra >> Ecosystem. >> 2. 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). >> 3. New committers for these subprojects will be nominated and raised, both >> at inclusion as a subproject and over time. Nominations can be brought to >> priv...@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. >> 4. While the commit-bit is ecosystem wide, code modification rights and >> voting rights (technical contribution, binding -1, CEP's) are granted per >> subproject >> 4a. 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. >> 4b. Members of the PMC have commit and voting rights on all subprojects. >> 5. For each subproject, the PMC will 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) on the subproject. >> ------------------------------------- >> >> Curious to see what thoughts we have as a community! >> >> Thanks! >> >> ~Josh >> > >
