Apologies for coming in late on this one.

+1 in general, but… -1 on the gh transfer (see below), and a few questions
seeking clarification.

Dave, is your comment about lazy-consensus applicable to both the project's
PMC or the IPMC (Incubator PMC's role on this thread) ?  My understanding
is that the PMC must still formally vote (requires 3 binding and no vetos)
and the IPMC just needs visibility (lazy).  To be specific, the PMC vote
requirements is on us, and my opinion is that importing a new codebase and
repository always deserves a proper vote by us (even in situations like
this where we are generally confident of the outcome based on previous
discussions).

Furthermore, this text in https://incubator.apache.org/ip-clearance/
indicates the form's checklist must be complete first.
"Once a PMC directly checks-in a filled-out short form, the Incubator PMC
will need to approve the paper work after which point the receiving PMC is
free to import the code."

These are somewhat confirmed by steps (6) and (7) on this page:
https://incubator.apache.org/ip-clearance/ip-clearance-template.html


This IP Clearance form is not yet completed.  Please fill out the data
column in the form to indicate all steps have been done.

They are:
 - Check and make sure that the files that have been donated have been
updated to reflect the new ASF copyright.
 - Check and make sure that for all items included with the distribution
that is not under the Apache license, we have the right to combine with
Apache-licensed code and redistribute.
 - Check and make sure that all items depended upon by the project is
covered by one or more of the following approved licenses: Apache, BSD,
Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same
terms.


My understanding is the latter two points have been done, and the license
headers and the LICENSE and NOTICE stuff will land with
https://github.com/rustyrazorblade/cassandra-easy-stress/pull/41

And IIRC that PR needs to be merged before asking infra to transfer the
repo. (only reason for my -1 on the transfer)



On Fri, 2 May 2025 at 21:39, Jon Haddad <j...@rustyrazorblade.com> wrote:

> Since we only need lazy consensus here - it sounds like i can go ahead and
> rename the repo to cassandra-easy-stress and transfer it over to Apache.
>
> On Thu, May 1, 2025 at 1:37 PM Aaron <aaronplo...@gmail.com> wrote:
>
>> +1
>>
>> On Thu, May 1, 2025 at 4:27 PM Dave Herrington <he...@rhinosource.com>
>> wrote:
>>
>>> +1 (nb)
>>>
>>> -Dave
>>>
>>> On Wed, Apr 30, 2025 at 8:16 AM Jordan West <jw...@apache.org> wrote:
>>>
>>>> (general@incubator cc'd)
>>>>
>>>> Please vote on the acceptance of the easy-cass-stress (to be renamed
>>>> cassandra-stress) and its IP Clearance:
>>>>
>>>>
>>>> https://incubator.apache.org/ip-clearance/cassandra-easy-cass-stress.html
>>>>
>>>> All consent from original authors of the donation, and tracking of
>>>> collected CLAs, is found in
>>>>
>>>> https://github.com/rustyrazorblade/easy-cass-stress/pull/41/files and
>>>> <https://www.notion.so/easy-cass-stress-submission-141ac849cc9d80a4972cc8623aa54667?pvs=21>
>>>> https://delicate-tail-8c0.notion.site/easy-cass-stress-submission-141ac849cc9d80a4972cc8623aa54667
>>>>
>>>> These do not all require acknowledgement before the vote.
>>>>
>>>> The code is prepared for donation at
>>>> https://github.com/rustyrazorblade/easy-cass-stress
>>>>
>>>> Once this vote passes we will request ASF Infra to move the
>>>> rustyrazorblade/easy-cass-stress as-is to apache/cassandra-stress. The main
>>>> branch and gh-pages branches, all tags, and all history, will be kept.  The
>>>> main branch will continue to be named main.
>>>>
>>>> PMC members, please check carefully the IP Clearance requirements
>>>> before voting.
>>>>
>>>> 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.
>>>>
>>>> Thanks,
>>>>
>>>> Jordan
>>>>
>>>
>>>
>>> --
>>> -Dave
>>>
>>> David A. Herrington II
>>> President and Chief Engineer
>>> RhinoSource, Inc.
>>>
>>> *Data Lake Architecture, Cloud Computing and Advanced Analytics.*
>>>
>>> www.rhinosource.com
>>>
>>

Reply via email to