Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Dinesh Joshi]

On Wed, May 15, 2024 at 12:09 AM Mick Semb Wever  wrote:

> Yes Dinesh.   João Reis managed to get hold of both Chris and Martin.
>>> Responses have been slow, but everyone is on board.  This is not to be
>>> considered a hostile fork, despite in all likelihood not being able to do a
>>> full IP donation.
>>>
>>
Great! I have no concerns at this point.

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Mick Semb Wever]

>
> Ok, so we're got confidence now on how to approach this, confirmation from
>> the project's maintainers supporting it, and interest from a handful of
>> people interested in maintaining and contributing to the project.
>>
>
> Did you talk to the current maintainers off list or did I miss some thread
> where the maintainers indicated their support in maintaining this project?
>



Yes Dinesh.   João Reis managed to get hold of both Chris and Martin.
Responses have been slow, but everyone is on board.  This is not to be
considered a hostile fork, despite in all likelihood not being able to do a
full IP donation.

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Dinesh Joshi]

On Tue, May 14, 2024 at 10:05 AM Mick Semb Wever  wrote:

>
> Ok, so we're got confidence now on how to approach this, confirmation from
> the project's maintainers supporting it, and interest from a handful of
> people interested in maintaining and contributing to the project.
>

Did you talk to the current maintainers off list or did I miss some thread
where the maintainers indicated their support in maintaining this project?

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Josh McKenzie]

Does anyone call out the need for a new CEP for bringing the gocql into the 
Driver's subproject ? 
> My suggestion is that this falls under CEP-8, even if it is not DataStax 
> donating this particular codebase, the process is largely the same and it is 
> the Drivers subproject receiving it.
+1 to future driver donations falling under CEP-8

On Tue, May 14, 2024, at 1:03 PM, Mick Semb Wever wrote:
> 
> Ok, so we're got confidence now on how to approach this, confirmation from 
> the project's maintainers supporting it, and interest from a handful of 
> people interested in maintaining and contributing to the project.
> 
> The proposed plan forward is…
> 
> We will go through a round of collecting CLAs along with agreements to donate 
> work to ASF from all gocql authors, over email and LinkedIn searches and 
> messages.  We will also open a github issue on the gocql project describing 
> the steps involved and mentioning all the authors.  A response on the GH 
> issue from everyone agreeing to the donation is the best single place to 
> collect the responses from everyone, but we'll accept and work with 
> whatever/however we get them.   These authors will also need to sign this 
> ICLA and submit it to the ASF.
> 
> After a four week grace period we will move ahead with the IP donation to 
> ASF, and make a list of all work (files) that we don't have CLAs for.  Such 
> work may remain with headers honouring their past MIT license and authors.  
> When the work is accepted and brought into the Cassandra Driver subproject we 
> will be looking to add committers to the subproject.  These may or may not be 
> people who have expressed interest in further contributing to the codebase, 
> but rather people we trust regardless when/if they come back to contribute.
> 
> Does anyone call out the need for a new CEP for bringing the gocql into the 
> Driver's subproject ? 
> My suggestion is that this falls under CEP-8, even if it is not DataStax 
> donating this particular codebase, the process is largely the same and it is 
> the Drivers subproject receiving it.
> 
>  
> 
> On Mon, 15 Apr 2024 at 12:31, Mick Semb Wever  wrote:
>> 
>>
>> 
 We can open an issue with LEGAL to see what they say at least?
>>> 
>>> 
>>> I will raise a LEGAL ticket.
>>> 
>>> My question here is whether we have to go through the process of 
>>> best-efforts to get approval to donate (transfer copyright), or whether we 
>>> can honour the copyright on the prior work and move forward ( by 
>>> referencing it in our NOTICE.txt, as per 
>>> https://infra.apache.org/licensing-howto.html )
>> 
>> 
>> https://issues.apache.org/jira/browse/LEGAL-674  

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Mick Semb Wever]

Ok, so we're got confidence now on how to approach this, confirmation from
the project's maintainers supporting it, and interest from a handful of
people interested in maintaining and contributing to the project.

The proposed plan forward is…

We will go through a round of collecting CLAs along with agreements to
donate work to ASF from all gocql authors, over email and LinkedIn searches
and messages.  We will also open a github issue on the gocql project
describing the steps involved and mentioning all the authors.  A response
on the GH issue from everyone agreeing to the donation is the best single
place to collect the responses from everyone, but we'll accept and work
with whatever/however we get them.   These authors will also need to sign
this ICLA and submit it to the ASF.

After a four week grace period we will move ahead with the IP donation to
ASF, and make a list of all work (files) that we don't have CLAs for.  Such
work may remain with headers honouring their past MIT license and authors.
When the work is accepted and brought into the Cassandra Driver subproject
we will be looking to add committers to the subproject.  These may or may
not be people who have expressed interest in further contributing to the
codebase, but rather people we trust regardless when/if they come back to
contribute.

Does anyone call out the need for a new CEP for bringing the gocql into the
Driver's subproject ?
My suggestion is that this falls under CEP-8, even if it is not DataStax
donating this particular codebase, the process is largely the same and it
is the Drivers subproject receiving it.



On Mon, 15 Apr 2024 at 12:31, Mick Semb Wever  wrote:

>
>
>
> We can open an issue with LEGAL to see what they say at least?
>>>
>>
>>
>> I will raise a LEGAL ticket.
>>
>> My question here is whether we have to go through the process of
>> best-efforts to get approval to donate (transfer copyright), or whether we
>> can honour the copyright on the prior work and move forward ( by
>> referencing it in our NOTICE.txt, as per
>> https://infra.apache.org/licensing-howto.html )
>>
>
>
> https://issues.apache.org/jira/browse/LEGAL-674
>

RE: Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Rolo, Carlos via dev]

Hello,

We are serious looking at picking up this driver here at Instaclustr. I will 
keep this thread updated.

On 2024/04/15 10:31:49 Mick Semb Wever wrote:
> We can open an issue with LEGAL to see what they say at least?
> >>
> >
> >
> > I will raise a LEGAL ticket.
> >
> > My question here is whether we have to go through the process of
> > best-efforts to get approval to donate (transfer copyright), or whether we
> > can honour the copyright on the prior work and move forward ( by
> > referencing it in our NOTICE.txt, as per
> > https://infra.apache.org/licensing-howto.html )
> >
>
>
> https://issues.apache.org/jira/browse/LEGAL-674
>


Carlos Rolo
Manager
Open Source Contributions

NetApp
carlos.r...@netapp.com

[cid:e306da79-20cb-4a62-a8c2-066e2bcbc580]

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Mick Semb Wever]

We can open an issue with LEGAL to see what they say at least?
>>
>
>
> I will raise a LEGAL ticket.
>
> My question here is whether we have to go through the process of
> best-efforts to get approval to donate (transfer copyright), or whether we
> can honour the copyright on the prior work and move forward ( by
> referencing it in our NOTICE.txt, as per
> https://infra.apache.org/licensing-howto.html )
>


https://issues.apache.org/jira/browse/LEGAL-674

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Mick Semb Wever]

> tl,dr:
> - The AUTHORS lists everyone who ever made a commit (
> https://github.com/gocql/gocql/blob/master/AUTHORS)
> - The license is BSD-3 and explicitly says the copyright is owned by the
> authors (https://github.com/gocql/gocql/blob/master/LICENSE#L1)
> - We had a previous discussion about 6 years ago:
> https://www.mail-archive.com/dev@cassandra.apache.org/msg13008.html
>
> We can open an issue with LEGAL to see what they say at least?
>


I will raise a LEGAL ticket.

My question here is whether we have to go through the process of
best-efforts to get approval to donate (transfer copyright), or whether we
can honour the copyright on the prior work and move forward ( by
referencing it in our NOTICE.txt, as per
https://infra.apache.org/licensing-howto.html )

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Dinesh Joshi]

If we take this on - are there any active contributors that can be raised
as committers to maintain this project?

On Wed, Apr 3, 2024 at 2:36 PM Nate McCall  wrote:

> We've talked through this before. Benjamin sussed out the main issue,
> IIRC.
> tl,dr:
> - The AUTHORS lists everyone who ever made a commit (
> https://github.com/gocql/gocql/blob/master/AUTHORS)
> - The license is BSD-3 and explicitly says the copyright is owned by the
> authors (https://github.com/gocql/gocql/blob/master/LICENSE#L1)
> - We had a previous discussion about 6 years ago:
> https://www.mail-archive.com/dev@cassandra.apache.org/msg13008.html
>
> We can open an issue with LEGAL to see what they say at least?
>
> -N
>
> On Tue, Feb 6, 2024 at 10:25 AM Mick Semb Wever  wrote:
>
>>
>> The current sole maintainer of the gocql driver has stated the project is
>> essentially in attic mode and is asking for new maintainers.
>>
>> https://groups.google.com/g/gocql/c/v0FruczBb2w
>>
>> No one has suggested the repo be donated to the ASF yet, but before
>> anyone should raise any such suggestion we should check if we have folk in
>> the project that would be willing to help out with such a donation.
>>
>

Re: Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Nate McCall]

We've talked through this before. Benjamin sussed out the main issue, IIRC.
tl,dr:
- The AUTHORS lists everyone who ever made a commit (
https://github.com/gocql/gocql/blob/master/AUTHORS)
- The license is BSD-3 and explicitly says the copyright is owned by the
authors (https://github.com/gocql/gocql/blob/master/LICENSE#L1)
- We had a previous discussion about 6 years ago:
https://www.mail-archive.com/dev@cassandra.apache.org/msg13008.html

We can open an issue with LEGAL to see what they say at least?

-N

On Tue, Feb 6, 2024 at 10:25 AM Mick Semb Wever  wrote:

>
> The current sole maintainer of the gocql driver has stated the project is
> essentially in attic mode and is asking for new maintainers.
>
> https://groups.google.com/g/gocql/c/v0FruczBb2w
>
> No one has suggested the repo be donated to the ASF yet, but before anyone
> should raise any such suggestion we should check if we have folk in the
> project that would be willing to help out with such a donation.
>

Is there appetite to maintain the gocql driver (in the drivers subproject) ?

[Mick Semb Wever]

The current sole maintainer of the gocql driver has stated the project is
essentially in attic mode and is asking for new maintainers.

https://groups.google.com/g/gocql/c/v0FruczBb2w

No one has suggested the repo be donated to the ASF yet, but before anyone
should raise any such suggestion we should check if we have folk in the
project that would be willing to help out with such a donation.