This is really game-changing and an important change for the Cassandra community. I would like to think that creating a governance structure like this will help get more ecosystem projects under the umbrella of Apache Cassandra.
Thank you PMC, for spending the time to create this very needed framework. Patrick On Mon, Jan 30, 2023 at 11:02 AM Jeff Jirsa <jji...@gmail.com> wrote: > Usually requires an offer to donate from the current owner, an acceptance > of that offer (PMC vote), and then the work to ensure that contributions > are acceptable from a legal standpoint (e.g. like the incubator - > https://incubator.apache.org/guides/transitioning_asf.html - "For > contributions composed of patches from individual contributors, it is safe > to import the code once the major contributors (by volume) have completed > ICLAs or SGAs."). > > > > On Mon, Jan 30, 2023 at 10:53 AM German Eichberger via dev < > dev@cassandra.apache.org> wrote: > >> Great news indeed. I am wondering what it would take to include projects >> everyone is using like medusa, reaper, cassandra-ldap, etc. as a subproject. >> >> Thanks, >> German >> ------------------------------ >> *From:* Francisco Guerrero <fran...@apache.org> >> *Sent:* Friday, January 27, 2023 9:46 AM >> *To:* dev@cassandra.apache.org <dev@cassandra.apache.org> >> *Subject:* [EXTERNAL] Re: [ANNOUNCE] Evolving governance in the >> Cassandra Ecosystem >> >> Great news! I'm very happy to see these changes coming soon. >> >> Thanks to everyone involved in this work. >> >> On 2023/01/26 21:21:01 Josh McKenzie 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fpages%2Fviewpage.action%3FpageId%3D95652224&data=05%7C01%7CGerman.Eichberger%40microsoft.com%7Cda65de0ac4d84d94c54708db008e897d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638104384430582894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xUbCe%2FQGgZq3Ynr42YQucMkOw1IZ67cONiQSnkZI7bk%3D&reserved=0) >> and Cassandra-14395 ( >> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCASSANDRASC-24&data=05%7C01%7CGerman.Eichberger%40microsoft.com%7Cda65de0ac4d84d94c54708db008e897d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638104384430582894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RdItVOzwVs865Xd%2Ff8ancwkTDJWKPosHlKgbl1uysMw%3D&reserved=0), >> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1e0SsZxjeTabzrMv99pCz9zIkkgWjUd4KL5Yp0GFzNnY%2Fedit%23heading%3Dh.xhizycgqxoyo&data=05%7C01%7CGerman.Eichberger%40microsoft.com%7Cda65de0ac4d84d94c54708db008e897d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638104384430582894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pUXo983DEHRBDtjGD%2FHaZnqc1uRwpS7tBkFkNF9Qfns%3D&reserved=0), >> 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 >> > >> >
