I'd like to close out this thread. As Benjamin notes, we'll have a single
subproject for all of the drivers and with 3 PMC members overseeing the
subproject as outlined in the linked subproject governance procedures. However
we'll introduce the drivers to that subproject one by one out of nece
The idea was to have a single driver sub-project. Even if the code bases
are different we believe that it is important to keep the drivers together
to retain cohesive API semantics and make sure they have similar
functionality and feature support.
In this scenario we would need only 3 PMC members f
> Is the vote for the CEP to be for all drivers, but we will introduce each
> driver one by one? What determines when we are comfortable with one driver
> subproject and can move on to accepting the next ?
Curious to hear on this as well. There's 2 implications from the CEP as written:
1. The
Thank you so much Jeremy and Greg (+others) for all the hard work on this.
> At this point, we'd like to propose CEP-8 for consideration, starting the
> process to accept the DataStax Java driver as an official ASF project.
>
Is the vote for the CEP to be for all drivers, but we will introduce
Sharing the same sentiment. Thank you for all your efforts on getting this
ready to contribute!
> On May 26, 2023, at 9:59 AM, Francisco Guerrero wrote:
>
> I second Dinesh's sentiment. I'm looking forward to this contribution.
>
> On 2023/05/26 16:29:12 Dinesh Joshi wrote:
>> This is exciting
I second Dinesh's sentiment. I'm looking forward to this contribution.
On 2023/05/26 16:29:12 Dinesh Joshi wrote:
> This is exciting. Thank you for all your hard work on getting ICLAs from
> contributors. I am in favor of moving forward.
>
>
> >
> > On May 26, 2023, at 5:54 AM, Jeremy Hann
This is exciting. Thank you for all your hard work on getting ICLAs from contributors. I am in favor of moving forward.On May 26, 2023, at 5:54 AM, Jeremy Hanna wrote:To add to a somewhat crowded [DISCUSS] party, I'd like to restart the discussion around CEP-8.This is the original thread from Jul
To add to a somewhat crowded [DISCUSS] party, I'd like to restart the
discussion around CEP-8.
This is the original thread from July 2020:
https://lists.apache.org/thread/01pljcncyjyo467l5orh8nf9okrh7oxm
At the time, several good points were discussed and the CEP has been updated
with many of
Alex,
That's awesome! Thanks for the clarification.
-Jeremy
On Wed, Aug 5, 2020 at 1:18 AM Alexandre Dutra
wrote:
> Hi Alex and Jeremy,
>
> We've been thinking of the driver codebase on a repository level in the
> CEP, which is why we do not mention any specific branch. To clarify, our
> inten
Hi Alex and Jeremy,
We've been thinking of the driver codebase on a repository level in the
CEP, which is why we do not mention any specific branch. To clarify, our
intention is to donate the entire repository, including all existing
commits, branches and tags. So don't worry: the Java driver 3.x
+1 on both starting with just the Java driver first and contributing all
3.x and 4.x branches. Some of our long-running apps may continue using 3.x
for quite a while simply due to the extra effort due to their
deep-maintenance lifestyle.
-Jeremy
On Tue, Aug 4, 2020 at 4:26 AM Oleksandr Petrov
wr
I've tried to find this information in the document above, but couldn't
find an explicit mention of it, possibly because it's implied. If we take
java-driver as an example, is this CEP proposing to contribute all branches
(3.x and 4.x) or only the latest one?
Thank you,
-- Alex
On Wed, Jul 29, 20
Hi Dinesh,
While we think that maintaining the drivers together as a long-term goal
would be beneficial as it would allow the drivers to evolve together and
adopt similar design decisions, we also understand that donating 7 drivers
at once may put the whole operation at risk, as some folks here al
This is great! +1 to the phased approach mentioned in the document of
starting with the Java driver, and then including the learnings if any into
the rest of the drivers' donation.
Also excited about the documentation donation - it will be nice to not have
to depend on the mentioned proprietary too
Alexandre,
I gave the document a quick read and TL;DR seems to be that we'd like to:
1. Bring in all drivers
2. They're part of the C* project
If so, I would prefer if we add the Java driver first to the project. Based on
that experience we can move forward with other drivers. However, I am ope
This is fantastic, Alexandre, thanks for putting this together!
I put an initial set of comments/concerns on there and will loop back later
this week after other folks have a go.
Cheers,
-Nate
On Sat, Jul 25, 2020 at 7:35 AM Alexandre Dutra <
alexandre.du...@datastax.com> wrote:
> Hi,
>
> As p
Hi,
As per the CEP process guidelines, I'm starting a formal DISCUSS
thread to resume the conversation
started here[1].
On behalf of the developers who maintain the DataStax drivers, I
confirm that we are offering to
donate to the Apache Software Foundation all seven DataStax-funded
drivers, and
17 matches
Mail list logo
