I welcome the donation, and hope we are able to accept all of the drivers.
This is really great news IMO.
I do however wonder if the project may be accumulating too many sub-projects?
I wonder if it's time to think about splitting, and perhaps incubating a
project for the drivers?
On 22/04/2020, 18:20, "Dinesh Joshi" <djo...@apache.org> wrote:
Hi Adam,
Great to hear from you! I personally welcome the driver donation. My views
are inline below.
Thanks,
Dinesh
> On Apr 22, 2020, at 10:00 AM, Adam Holmberg <adam.holmb...@datastax.com>
wrote:
> - 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
Java and Python at least.
> - 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
No opinions here. What are the major differences here? Could you please
elaborate.
> - 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?
I generally think people who have built the code base should become
committers to avoid disruption and allow continuity.
> - What should the new artifacts be named in package indices (coordinates
> and artifact names)?
I am not completely sure but we may need to rename some packages but it
would be really great if we could avoid breakages due to naming changes.
> - How will we run CI for these contributions?
ASF Jenkins/CircleCI works? Do the drivers have specific needs beyond this?
> - Do we do in-tree? Sub-projects?
sub-projects like cassandra-diff, sidecar, etc. This way drivers continue
to evolve separately.
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
