Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Mick]

Votes passes with twelve +1s (ten from the PMC), and no vetoes.



> On 11 Nov 2025, at 22:51, Mick  wrote:
> 
> Please vote on the acceptance of the Cassandra CPP Driver and its IP 
> Clearance:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html 
> 
> All consent from original authors of the donation, and tracking of
> collected CLAs, is found in:
> - https://github.com/datastax/cpp-driver/pull/573 
> - 
> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a 
> 
> These are now represented in the NOTICE file.
> 
> The code is prepared for donation at https://github.com/datastax/cpp-driver
> (Only the `master` ref head will be brought over, and all tags.)
> 
> Once this vote passes we will request ASF Infra to move the 
> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master branch 
> will kept all its history, will be kept.  
> 
> Cassandra PMC members, please check carefully the IP Clearance requirements 
> before voting.
> general@incubator is cc'd, only a lazy consensus is required from the IPMC.
> 
> The vote will be open for 72 hours (or longer). Votes by PMC members are 
> considered binding. A vote passes if there are at least three binding +1s and 
> no -1's.
> 
> regards,
> Mick

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Francisco Guerrero]

+1

On 2025/11/11 21:51:15 Mick wrote:
> Please vote on the acceptance of the Cassandra CPP Driver and its IP 
> Clearance:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html 
> 
> All consent from original authors of the donation, and tracking of
> collected CLAs, is found in:
> - https://github.com/datastax/cpp-driver/pull/573 
> - 
> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a 
> 
> These are now represented in the NOTICE file.
> 
> The code is prepared for donation at https://github.com/datastax/cpp-driver
> (Only the `master` ref head will be brought over, and all tags.)
> 
> Once this vote passes we will request ASF Infra to move the 
> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master branch 
> will kept all its history, will be kept.  
> 
> Cassandra PMC members, please check carefully the IP Clearance requirements 
> before voting.
> general@incubator is cc'd, only a lazy consensus is required from the IPMC.
> 
> The vote will be open for 72 hours (or longer). Votes by PMC members are 
> considered binding. A vote passes if there are at least three binding +1s and 
> no -1's.
> 
> regards,
> Mick

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[David Capwell]

+1

> On Nov 17, 2025, at 10:05 AM, Ekaterina Dimitrova  
> wrote:
> 
> Repeating Bret - IP clearance seems right, SHA matches a legit commit, 
> dependencies all seem to have acceptable licenses (accounting for the 
> libssh/libssh2 confusion) and code changes appear correct.
> 
> +1
> 
> Best regards,
> Ekaterina
> 
> На пт, 14.11.2025 г. в 4:54 Benjamin Lerer  > написа:
>> +1
>> 
>> Le jeu. 13 nov. 2025 à 16:24, Josh McKenzie > > a écrit :
>>> +1
>>> 
>>> On Thu, Nov 13, 2025, at 12:05 AM, Bret McGuire wrote:
Similar to eval of the Python driver.
 
IP clearance seems right, SHA matches a legit commit, dependencies all 
 seem to have acceptable licenses (accounting for the libssh/libssh2 
 confusion) and code changes appear correct.
 
+1
 
 
 On Tue, Nov 11, 2025 at 3:53 PM Mick >>> > wrote:
 Please vote on the acceptance of the Cassandra CPP Driver and its IP 
 Clearance:
 https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
 
 All consent from original authors of the donation, and tracking of
 collected CLAs, is found in:
 - https://github.com/datastax/cpp-driver/pull/573
 - 
 https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a
 
 These are now represented in the NOTICE file.
 
 The code is prepared for donation at https://github.com/datastax/cpp-driver
 (Only the `master` ref head will be brought over, and all tags.)
 
 Once this vote passes we will request ASF Infra to move the 
 datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master 
 branch will kept all its history, will be kept. 
 
 Cassandra PMC members, please check carefully the IP Clearance 
 requirements before voting.
 general@incubator is cc'd, only a lazy consensus is required from the IPMC.
 
 The vote will be open for 72 hours (or longer). Votes by PMC members are 
 considered binding. A vote passes if there are at least three binding +1s 
 and no -1's.
 
 regards,
 Mick

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Ekaterina Dimitrova]

Repeating Bret - IP clearance seems right, SHA matches a legit commit,
dependencies all seem to have acceptable licenses (accounting for the
libssh/libssh2 confusion) and code changes appear correct.

+1

Best regards,
Ekaterina

На пт, 14.11.2025 г. в 4:54 Benjamin Lerer  написа:

> +1
>
> Le jeu. 13 nov. 2025 à 16:24, Josh McKenzie  a
> écrit :
>
>> +1
>>
>> On Thu, Nov 13, 2025, at 12:05 AM, Bret McGuire wrote:
>>
>>Similar to eval of the Python driver.
>>
>>IP clearance seems right, SHA matches a legit commit, dependencies all
>> seem to have acceptable licenses (accounting for the libssh/libssh2
>> confusion) and code changes appear correct.
>>
>>+1
>>
>>
>> On Tue, Nov 11, 2025 at 3:53 PM Mick  wrote:
>>
>> Please vote on the acceptance of the Cassandra CPP Driver and its IP
>> Clearance:
>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>>
>> All consent from original authors of the donation, and tracking of
>> collected CLAs, is found in:
>> - https://github.com/datastax/cpp-driver/pull/573
>> -
>> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a
>>
>> These are now represented in the NOTICE file.
>>
>> The code is prepared for donation at
>> https://github.com/datastax/cpp-driver
>> (Only the `master` ref head will be brought over, and all tags.)
>>
>> Once this vote passes we will request ASF Infra to move the
>> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master
>> branch will kept all its history, will be kept.
>>
>> Cassandra PMC members, please check carefully the IP Clearance
>> requirements before voting.
>> general@incubator is cc'd, only a lazy consensus is required from the
>> IPMC.
>>
>> The vote will be open for 72 hours (or longer). Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding +1s
>> and no -1's.
>>
>> regards,
>> Mick
>>
>>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Benjamin Lerer]

+1

Le jeu. 13 nov. 2025 à 16:24, Josh McKenzie  a écrit :

> +1
>
> On Thu, Nov 13, 2025, at 12:05 AM, Bret McGuire wrote:
>
>Similar to eval of the Python driver.
>
>IP clearance seems right, SHA matches a legit commit, dependencies all
> seem to have acceptable licenses (accounting for the libssh/libssh2
> confusion) and code changes appear correct.
>
>+1
>
>
> On Tue, Nov 11, 2025 at 3:53 PM Mick  wrote:
>
> Please vote on the acceptance of the Cassandra CPP Driver and its IP
> Clearance:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>
> All consent from original authors of the donation, and tracking of
> collected CLAs, is found in:
> - https://github.com/datastax/cpp-driver/pull/573
> -
> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a
>
> These are now represented in the NOTICE file.
>
> The code is prepared for donation at
> https://github.com/datastax/cpp-driver
> (Only the `master` ref head will be brought over, and all tags.)
>
> Once this vote passes we will request ASF Infra to move the
> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master
> branch will kept all its history, will be kept.
>
> Cassandra PMC members, please check carefully the IP Clearance
> requirements before voting.
> general@incubator is cc'd, only a lazy consensus is required from the
> IPMC.
>
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
> regards,
> Mick
>
>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Josh McKenzie]

+1

On Thu, Nov 13, 2025, at 12:05 AM, Bret McGuire wrote:
>Similar to eval of the Python driver.
> 
>IP clearance seems right, SHA matches a legit commit, dependencies all 
> seem to have acceptable licenses (accounting for the libssh/libssh2 
> confusion) and code changes appear correct.
> 
>+1
> 
> 
> On Tue, Nov 11, 2025 at 3:53 PM Mick  wrote:
>> Please vote on the acceptance of the Cassandra CPP Driver and its IP 
>> Clearance:
>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html 
>> 
>> All consent from original authors of the donation, and tracking of
>> collected CLAs, is found in:
>> - https://github.com/datastax/cpp-driver/pull/573 
>> - 
>> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a
>>  
>> 
>> These are now represented in the NOTICE file.
>> 
>> The code is prepared for donation at https://github.com/datastax/cpp-driver
>> (Only the `master` ref head will be brought over, and all tags.)
>> 
>> Once this vote passes we will request ASF Infra to move the 
>> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master 
>> branch will kept all its history, will be kept.  
>> 
>> Cassandra PMC members, please check carefully the IP Clearance requirements 
>> before voting.
>> general@incubator is cc'd, only a lazy consensus is required from the IPMC.
>> 
>> The vote will be open for 72 hours (or longer). Votes by PMC members are 
>> considered binding. A vote passes if there are at least three binding +1s 
>> and no -1's.
>> 
>> regards,
>> Mick

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Bret McGuire]

   Similar to eval of the Python driver.

   IP clearance seems right, SHA matches a legit commit, dependencies all
seem to have acceptable licenses (accounting for the libssh/libssh2
confusion) and code changes appear correct.

   +1


On Tue, Nov 11, 2025 at 3:53 PM Mick  wrote:

> Please vote on the acceptance of the Cassandra CPP Driver and its IP
> Clearance:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>
> All consent from original authors of the donation, and tracking of
> collected CLAs, is found in:
> - https://github.com/datastax/cpp-driver/pull/573
> -
> https://ibm.ent.box.com/file/1970403868396?s=6un5oggyli0bln4cxypl8rn2f2dtzy6a
>
> These are now represented in the NOTICE file.
>
> The code is prepared for donation at
> https://github.com/datastax/cpp-driver
> (Only the `master` ref head will be brought over, and all tags.)
>
> Once this vote passes we will request ASF Infra to move the
> datastax/cpp-driver as-is to apache/cassandra-cpp-driver  . The master
> branch will kept all its history, will be kept.
>
> Cassandra PMC members, please check carefully the IP Clearance
> requirements before voting.
> general@incubator is cc'd, only a lazy consensus is required from the
> IPMC.
>
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
> regards,
> Mick

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Bret McGuire]

   Good catch jd!  I can confirm that the libssh reference in the
dependency list was indeed a mistake on my part and that libssh2 is the
correct library.  I've updated the list on the PR to contain the correct
information and added a comment explicitly indicating the change in order
to preserve history.

   - Bret -

On Wed, Nov 12, 2025 at 2:50 PM Jeremiah Jordan  wrote:

> Checked IP Clearance
> I see libssh which is LGPL mentioned in the linked PR comments. I could
> not find the use of libssh in the code only libssh2 which uses a BSD 3
> clause license.
>
> Code looks good.
> Besides libssh mentioned above the Dependency list looks good.
>
> +1 from me assuming the above libssh reference was a mistake and it really
> is only using libssh2 that is BSD licensed.
>
> -Jeremiah
>
>
> On Nov 12, 2025 at 8:12:01 AM, Christopher Bradford 
> wrote:
>
>> +1
>>
>> Thank you for tracking all of the approvals down, that's no small task.
>>
>> Christopher Bradford
>>
>>
>>
>> On Wed, Nov 12, 2025 at 6:43 AM Mick  wrote:
>>
>>> For commits that are after the SGA date we need approval from their
>>> authors that their contributions can be transferred.  This can be
>>> implicit/lazy for Cassandra committers. We will need a "+1 to  also
>>> being donated" from Daniel (if you can chase that up Bret please).  That
>>> can be either on this thread or on the (now closed) donation PR.
>>>
>>> Another legit question that's come up is we don't have consent from all
>>> past contributors.  Here we are taking a similar approach to past donations
>>> where we track this in the NOTICE file: we make mention of the donation SHA
>>> and contributors from before that we were unable to reach.
>>>
>>>
>>>
>>>
>>> > On 12 Nov 2025, at 05:02, Bret McGuire  wrote:
>>> >
>>> >Both the C/C++ and Python driver have "extra" commits added after
>>> the IP clearance form was created.  In C/C++ case the commit in question
>>> was driven by the branch pruning completed as part of the donation process,
>>> while for the Python driver this came about due to branch pruning combined
>>> with the release of 3.29.3.  If I'm not mistaken all of these commits come
>>> from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The
>>> only exception that I've found is one commit (
>>> https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
>>> on the Python driver from Daniel Bershatsky, and I've confirmed that we do
>>> have a signed DataStax CLA from him.  I would welcome anybody who wants to
>>> double-check those results! :)
>>> >
>>> >Given this information it seems like we're covered from a
>>> copyright/licensing question for all contributions since the SHAs specified
>>> in the IP clearance form.  That said, I am certainly NOT a lawyer so I will
>>> wait for Mick (or somebody else who knows more about this than I do) to
>>> enumerate what steps (if any) we need to take here.
>>> >
>>> >- Bret -
>>> >
>>> > On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas 
>>> wrote:
>>> > +1
>>> >
>>> > Note that there was one documentation cleanup PR that merged to the
>>> C++ driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4
>>> by Bret that would not be included according to the SHA listed at the IP
>>> clearance link:
>>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>>> >
>>> >> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>>> >>
>>> >>
>>> >>> Cassandra PMC members, please check carefully the IP Clearance
>>> requirements before voting.
>>> >>> general@incubator is cc'd, only a lazy consensus is required from
>>> the IPMC.
>>> >>>
>>> >>> The vote will be open for 72 hours (or longer). Votes by PMC members
>>> are considered binding. A vote passes if there are at least three binding
>>> +1s and no -1's.
>>> >>
>>> >>
>>> >>
>>> >> +1
>>> >
>>> >
>>> >
>>>
>>>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Jeremiah Jordan]

 Checked IP Clearance
I see libssh which is LGPL mentioned in the linked PR comments. I could not
find the use of libssh in the code only libssh2 which uses a BSD 3 clause
license.

Code looks good.
Besides libssh mentioned above the Dependency list looks good.

+1 from me assuming the above libssh reference was a mistake and it really
is only using libssh2 that is BSD licensed.

-Jeremiah


On Nov 12, 2025 at 8:12:01 AM, Christopher Bradford 
wrote:

> +1
>
> Thank you for tracking all of the approvals down, that's no small task.
>
> Christopher Bradford
>
>
>
> On Wed, Nov 12, 2025 at 6:43 AM Mick  wrote:
>
>> For commits that are after the SGA date we need approval from their
>> authors that their contributions can be transferred.  This can be
>> implicit/lazy for Cassandra committers. We will need a "+1 to  also
>> being donated" from Daniel (if you can chase that up Bret please).  That
>> can be either on this thread or on the (now closed) donation PR.
>>
>> Another legit question that's come up is we don't have consent from all
>> past contributors.  Here we are taking a similar approach to past donations
>> where we track this in the NOTICE file: we make mention of the donation SHA
>> and contributors from before that we were unable to reach.
>>
>>
>>
>>
>> > On 12 Nov 2025, at 05:02, Bret McGuire  wrote:
>> >
>> >Both the C/C++ and Python driver have "extra" commits added after
>> the IP clearance form was created.  In C/C++ case the commit in question
>> was driven by the branch pruning completed as part of the donation process,
>> while for the Python driver this came about due to branch pruning combined
>> with the release of 3.29.3.  If I'm not mistaken all of these commits come
>> from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The
>> only exception that I've found is one commit (
>> https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
>> on the Python driver from Daniel Bershatsky, and I've confirmed that we do
>> have a signed DataStax CLA from him.  I would welcome anybody who wants to
>> double-check those results! :)
>> >
>> >Given this information it seems like we're covered from a
>> copyright/licensing question for all contributions since the SHAs specified
>> in the IP clearance form.  That said, I am certainly NOT a lawyer so I will
>> wait for Mick (or somebody else who knows more about this than I do) to
>> enumerate what steps (if any) we need to take here.
>> >
>> >- Bret -
>> >
>> > On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas 
>> wrote:
>> > +1
>> >
>> > Note that there was one documentation cleanup PR that merged to the C++
>> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
>> Bret that would not be included according to the SHA listed at the IP
>> clearance link:
>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>> >
>> >> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>> >>
>> >>
>> >>> Cassandra PMC members, please check carefully the IP Clearance
>> requirements before voting.
>> >>> general@incubator is cc'd, only a lazy consensus is required from
>> the IPMC.
>> >>>
>> >>> The vote will be open for 72 hours (or longer). Votes by PMC members
>> are considered binding. A vote passes if there are at least three binding
>> +1s and no -1's.
>> >>
>> >>
>> >>
>> >> +1
>> >
>> >
>> >
>>
>>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Christopher Bradford]

+1

Thank you for tracking all of the approvals down, that's no small task.

Christopher Bradford



On Wed, Nov 12, 2025 at 6:43 AM Mick  wrote:

> For commits that are after the SGA date we need approval from their
> authors that their contributions can be transferred.  This can be
> implicit/lazy for Cassandra committers. We will need a "+1 to  also
> being donated" from Daniel (if you can chase that up Bret please).  That
> can be either on this thread or on the (now closed) donation PR.
>
> Another legit question that's come up is we don't have consent from all
> past contributors.  Here we are taking a similar approach to past donations
> where we track this in the NOTICE file: we make mention of the donation SHA
> and contributors from before that we were unable to reach.
>
>
>
>
> > On 12 Nov 2025, at 05:02, Bret McGuire  wrote:
> >
> >Both the C/C++ and Python driver have "extra" commits added after the
> IP clearance form was created.  In C/C++ case the commit in question was
> driven by the branch pruning completed as part of the donation process,
> while for the Python driver this came about due to branch pruning combined
> with the release of 3.29.3.  If I'm not mistaken all of these commits come
> from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The
> only exception that I've found is one commit (
> https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
> on the Python driver from Daniel Bershatsky, and I've confirmed that we do
> have a signed DataStax CLA from him.  I would welcome anybody who wants to
> double-check those results! :)
> >
> >Given this information it seems like we're covered from a
> copyright/licensing question for all contributions since the SHAs specified
> in the IP clearance form.  That said, I am certainly NOT a lawyer so I will
> wait for Mick (or somebody else who knows more about this than I do) to
> enumerate what steps (if any) we need to take here.
> >
> >- Bret -
> >
> > On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas 
> wrote:
> > +1
> >
> > Note that there was one documentation cleanup PR that merged to the C++
> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
> Bret that would not be included according to the SHA listed at the IP
> clearance link:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
> >
> >> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
> >>
> >>
> >>> Cassandra PMC members, please check carefully the IP Clearance
> requirements before voting.
> >>> general@incubator is cc'd, only a lazy consensus is required from the
> IPMC.
> >>>
> >>> The vote will be open for 72 hours (or longer). Votes by PMC members
> are considered binding. A vote passes if there are at least three binding
> +1s and no -1's.
> >>
> >>
> >>
> >> +1
> >
> >
> >
>
>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Mick]

For commits that are after the SGA date we need approval from their authors 
that their contributions can be transferred.  This can be implicit/lazy for 
Cassandra committers. We will need a "+1 to  also being donated" from 
Daniel (if you can chase that up Bret please).  That can be either on this 
thread or on the (now closed) donation PR.

Another legit question that's come up is we don't have consent from all past 
contributors.  Here we are taking a similar approach to past donations where we 
track this in the NOTICE file: we make mention of the donation SHA and 
contributors from before that we were unable to reach. 




> On 12 Nov 2025, at 05:02, Bret McGuire  wrote:
> 
>Both the C/C++ and Python driver have "extra" commits added after the IP 
> clearance form was created.  In C/C++ case the commit in question was driven 
> by the branch pruning completed as part of the donation process, while for 
> the Python driver this came about due to branch pruning combined with the 
> release of 3.29.3.  If I'm not mistaken all of these commits come from myself 
> (a PMC member) or Brad Schoening (a Cassandra committer).  The only exception 
> that I've found is one commit 
> (https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
>  on the Python driver from Daniel Bershatsky, and I've confirmed that we do 
> have a signed DataStax CLA from him.  I would welcome anybody who wants to 
> double-check those results! :)
> 
>Given this information it seems like we're covered from a 
> copyright/licensing question for all contributions since the SHAs specified 
> in the IP clearance form.  That said, I am certainly NOT a lawyer so I will 
> wait for Mick (or somebody else who knows more about this than I do) to 
> enumerate what steps (if any) we need to take here.
> 
>- Bret -
> 
> On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas  wrote:
> +1
> 
> Note that there was one documentation cleanup PR that merged to the C++ 
> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by 
> Bret that would not be included according to the SHA listed at the IP 
> clearance link: 
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
> 
>> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>> 
>> 
>>> Cassandra PMC members, please check carefully the IP Clearance requirements 
>>> before voting.
>>> general@incubator is cc'd, only a lazy consensus is required from the IPMC.
>>> 
>>> The vote will be open for 72 hours (or longer). Votes by PMC members are 
>>> considered binding. A vote passes if there are at least three binding +1s 
>>> and no -1's.
>> 
>> 
>> 
>> +1
> 
> 
> 

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Bret McGuire]

   Agree on all counts Scott!  I thought it useful to go into the level of
detail in my reply in part to make sure I hadn't made a bone-headed mistake
when double-checking my earlier conclusions but also (and probably more
importantly) to provide the context for somebody who knows more about this
stuff than I do to say whether we're good.  This area is very definitely
_not_ my area of expertise so my hope is that if I lay out the details
somebody smarter than me can say whether the reasoning holds or not! ;)

   I suspect you're very much right and that we can remedy this with a
contribution after the donation is wrapped up.

   Thanks for the thorough review!

   - Bret -


On Tue, Nov 11, 2025 at 10:23 PM C. Scott Andreas 
wrote:

> Yep to be clear, I don’t mean for that to interfere with this vote or the
> donation - just spot checked the commit listed on the form.
>
> It seems that these commits could easily be contributed to the respective
> drivers post-donation if needed.
>
> I am still +1 and very grateful for these contributions to the project. 👍
>
> - Scott
>
> On Nov 11, 2025, at 8:03 PM, Bret McGuire  wrote:
>
> 
>Both the C/C++ and Python driver have "extra" commits added after the
> IP clearance form was created.  In C/C++ case the commit in question was
> driven by the branch pruning completed as part of the donation process,
> while for the Python driver this came about due to branch pruning combined
> with the release of 3.29.3.  If I'm not mistaken all of these commits come
> from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The
> only exception that I've found is one commit (
> https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
> on the Python driver from Daniel Bershatsky, and I've confirmed that we do
> have a signed DataStax CLA from him.  I would welcome anybody who wants to
> double-check those results! :)
>
>Given this information it seems like we're covered from a
> copyright/licensing question for all contributions since the SHAs specified
> in the IP clearance form.  That said, I am certainly NOT a lawyer so I will
> wait for Mick (or somebody else who knows more about this than I do) to
> enumerate what steps (if any) we need to take here.
>
>- Bret -
>
> On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas 
> wrote:
>
>> +1
>>
>> Note that there was one documentation cleanup PR that merged to the C++
>> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
>> Bret that would not be included according to the SHA listed at the IP
>> clearance link:
>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>>
>> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>>
>>
>> Cassandra PMC members, please check carefully the IP Clearance
>> requirements before voting.
>> general@incubator is cc'd, only a lazy consensus is required from the
>> IPMC.
>>
>> The vote will be open for 72 hours (or longer). Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding +1s
>> and no -1's.
>>
>>
>>
>> +1
>>
>>
>>
>>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[C. Scott Andreas]

Yep to be clear, I don’t mean for that to interfere with this vote or the donation - just spot checked the commit listed on the form.It seems that these commits could easily be contributed to the respective drivers post-donation if needed.I am still +1 and very grateful for these contributions to the project. 👍- ScottOn Nov 11, 2025, at 8:03 PM, Bret McGuire  wrote:   Both the C/C++ and Python driver have "extra" commits added after the IP clearance form was created.  In C/C++ case the commit in question was driven by the branch pruning completed as part of the donation process, while for the Python driver this came about due to branch pruning combined with the release of 3.29.3.  If I'm not mistaken all of these commits come from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The only exception that I've found is one commit (https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa) on the Python driver from Daniel Bershatsky, and I've confirmed that we do have a signed DataStax CLA from him.  I would welcome anybody who wants to double-check those results! :)   Given this information it seems like we're covered from a copyright/licensing question for all contributions since the SHAs specified in the IP clearance form.  That said, I am certainly NOT a lawyer so I will wait for Mick (or somebody else who knows more about this than I do) to enumerate what steps (if any) we need to take here.   - Bret -On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas  wrote:+1Note that there was one documentation cleanup PR that merged to the C++ driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by Bret that would not be included according to the SHA listed at the IP clearance link: https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.htmlOn Nov 11, 2025, at 2:48 PM, Mick  wrote:Cassandra PMC members, please check carefully the IP Clearance requirements before voting.general@incubator is cc'd, only a lazy consensus is required from the IPMC.The vote will be open for 72 hours (or longer). Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and no -1's.+1

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Bret McGuire]

   Both the C/C++ and Python driver have "extra" commits added after the IP
clearance form was created.  In C/C++ case the commit in question was
driven by the branch pruning completed as part of the donation process,
while for the Python driver this came about due to branch pruning combined
with the release of 3.29.3.  If I'm not mistaken all of these commits come
from myself (a PMC member) or Brad Schoening (a Cassandra committer).  The
only exception that I've found is one commit (
https://github.com/datastax/python-driver/commit/b144a84a1f97002c4545b335efaac719519cd9fa)
on the Python driver from Daniel Bershatsky, and I've confirmed that we do
have a signed DataStax CLA from him.  I would welcome anybody who wants to
double-check those results! :)

   Given this information it seems like we're covered from a
copyright/licensing question for all contributions since the SHAs specified
in the IP clearance form.  That said, I am certainly NOT a lawyer so I will
wait for Mick (or somebody else who knows more about this than I do) to
enumerate what steps (if any) we need to take here.

   - Bret -

On Tue, Nov 11, 2025 at 5:01 PM C. Scott Andreas 
wrote:

> +1
>
> Note that there was one documentation cleanup PR that merged to the C++
> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
> Bret that would not be included according to the SHA listed at the IP
> clearance link:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>
> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>
>
> Cassandra PMC members, please check carefully the IP Clearance
> requirements before voting.
> general@incubator is cc'd, only a lazy consensus is required from the
> IPMC.
>
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
>
>
> +1
>
>
>
>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Nate McCall]

+1

On Tue, 11 Nov 2025 at 3:11 PM, Patrick McFadin  wrote:

> Pending the administrative detail Scott highlighted being cleared up, +1
> from me.
>
> Patrick
>
> On Tue, Nov 11, 2025 at 3:02 PM C. Scott Andreas 
> wrote:
>
>> +1
>>
>> Note that there was one documentation cleanup PR that merged to the C++
>> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
>> Bret that would not be included according to the SHA listed at the IP
>> clearance link:
>> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>>
>> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>>
>>
>> Cassandra PMC members, please check carefully the IP Clearance
>> requirements before voting.
>> general@incubator is cc'd, only a lazy consensus is required from the
>> IPMC.
>>
>> The vote will be open for 72 hours (or longer). Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding +1s
>> and no -1's.
>>
>>
>>
>> +1
>>
>>
>>
>>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Patrick McFadin]

Pending the administrative detail Scott highlighted being cleared up, +1
from me.

Patrick

On Tue, Nov 11, 2025 at 3:02 PM C. Scott Andreas 
wrote:

> +1
>
> Note that there was one documentation cleanup PR that merged to the C++
> driver since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by
> Bret that would not be included according to the SHA listed at the IP
> clearance link:
> https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html
>
> On Nov 11, 2025, at 2:48 PM, Mick  wrote:
>
>
> Cassandra PMC members, please check carefully the IP Clearance
> requirements before voting.
> general@incubator is cc'd, only a lazy consensus is required from the
> IPMC.
>
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
>
>
> +1
>
>
>
>

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[C. Scott Andreas]

+1 Note that there was one documentation cleanup PR that merged to the C++ driver 
since the SHA proposed for donation (d9ae6b9) in commit f81cba4 by Bret that would 
not be included according to the SHA listed at the IP clearance link: 
https://incubator.apache.org/ip-clearance/cassandra-cpp-driver.html On Nov 11, 2025, 
at 2:48 PM, Mick  wrote: Cassandra PMC members, please check 
carefully the IP Clearance requirements before voting. general@incubator is cc'd, 
only a lazy consensus is required from the IPMC. The vote will be open for 72 hours 
(or longer). Votes by PMC members are considered binding. A vote passes if there are 
at least three binding +1s and no -1's. +1

Re: [VOTE][IP CLEARANCE] Cassandra CPP Driver

[Mick]

> Cassandra PMC members, please check carefully the IP Clearance requirements 
> before voting.
> general@incubator is cc'd, only a lazy consensus is required from the IPMC.
> 
> The vote will be open for 72 hours (or longer). Votes by PMC members are 
> considered binding. A vote passes if there are at least three binding +1s and 
> no -1's.


+1