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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 >> >> >> >>
