The developers who maintain the DataStax drivers would like to start a conversation about donating these drivers to the Apache Cassandra project. Since we're actively working on the C* 4.0 support and integration in the drivers right now, we don't plan on executing on this until after C* 4.0 releases in order to avoid delaying the release. In the meantime we wanted to open the discussion so that we can all determine what we think best suits the project going forward.
There are a number of details we would like to discuss as a project community. Naming a few to get the discussion going: - Is there interest from the project community to take ownership of the (currently) DataStax drivers? - Which drivers should be taken into project stewardship? -- The project currently bundles Java and Python; there are five others: C#, Node.js, C++, PHP and Ruby - Which major branch of the Java driver should be chosen for development? -- Server currently uses Java driver 3.x but the latest is 4.x - Who will be the committers that maintain these drivers? Should we nominate new committers (contributors on the current drivers code-bases) so they can keep maintaining them with minimal disruption to the project as a whole? - What should the new artifacts be named in package indices (coordinates and artifact names)? - How will we run CI for these contributions? - Do we do in-tree? Sub-projects? There will surely be even more to figure out as we go. We look forward to discussing this with everyone. Kind regards, The DS Drivers Team
