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