Strong supporter for bringing ccm into the project as well. ccm is necessary test infrastructure for multiple subprojects, and Cassandra committers should be able to make the changes to ccm that are necessary for their patches.
There's also the security angle: we should work to consolidate our dependencies where appropriate, and reduce the risk of supply chain antics. > On May 15, 2024, at 4:25 PM, Bret McGuire <bret.mcgu...@gmail.com> wrote: > > Speaking only for myself I _love_ this idea. The various drivers use ccm > extensively in their integration test suites so having this tool in-house and > actively looked after would be very beneficial for our work. > > - Bret - > > On Wed, May 15, 2024 at 9:23 AM Josh McKenzie <jmcken...@apache.org > <mailto:jmcken...@apache.org>> wrote: >> Right now ccm isn't formally a subproject of Cassandra or under governance >> of the ASF. Given it's an integral components of our CI as well as for local >> testing for many devs, and we now have more experience w/our muscle on IP >> clearance and ingesting / absorbing subprojects where we can't track down >> every single contributor to get an ICLA, seems like it might be worth >> revisiting the topic of donation of ccm to Apache. >> >> For what it's worth, Sylvain originally and then DataStax after transfer >> have both been incredible and receptive stewards of the projects and repos, >> so this isn't about any response to any behavior on their part. >> Structurally, however, it'd be better for the health of the project(s) >> long-term to have ccm promoted in. As far as I know there was strong >> receptivity to that donation in the past but the IP clearance was the >> primary hurdle. >> >> Anyone have any thoughts for or against? >> >> https://github.com/riptano/ccm >>
