-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer repository to apache organization #265
Comments
I don't believe we were thoroughly tracking this, but I think the safest assumption would be to assume that out of our contributions, at least some were made on behalf of Beacon/in the course of Beacon work. In that case, does it make the most sense to basically just do both? i.e. @jrevels / @omus / @ericphanson all provide individual CLAs, and I also execute a corporate CLA for Beacon? |
Do we simply use "arrow" in the notify project box? The agreement states that we email the signed PDF only to secretary@apache.org Is there any further action that is needed for coordination of the submission? |
I think it's fine to use @jrevels, it's probably safest to do both then. |
I’ve submitted my ICLA, can someone check me off the list? (I don’t have permission) |
@jrevels, @omus, @KristofferC; any update? |
I'll submit mine tomorrow |
Note that @ericphanson helpfully pointed out that an electronic signature is possible/suffices: https://julialang.slack.com/archives/C02FQ3638CB/p1638988968012400?thread_ts=1638856381.010100&cid=C02FQ3638CB |
I have only one commit that touches the actual source code so according to the discussion about single commit authors in https://lists.apache.org/thread/cr28lsyq1rsxsb810olsj74h7z08zvbg I feel that there should be no requirement to sign anything from my part. There are also things like:
which is not true for the PR #250 since I copy-pasted it from somewhere. |
@KristofferC It makes sense. |
I've submitted my ICLA and have checked myself off the list |
I’m in the middle of traveling but will also try to care of this by EOW |
Finally got around to this, sorry for the delay - I've submitted both an ICLA for myself and a CCLA for Beacon via the provided instructions. Let me know if anything else is necessary to move forward. |
Ok @kou , I think that should be everyone then, assuming we're in agreement to ignore @KristofferC's "administrative" commit. I'm ready to facilitate whatever we need to do next to complete the transfer. |
OK. Did you do the following?
I need to record the date when we did it in https://incubator.apache.org/ip-clearance/arrow-julia-library2.html . |
Yes, my comment above on Dec 7th was a recommendation to Jarrett that a corporate CLA be signed/provided. I reminded the individual contributors on Dec 6. I've removed Kristoffer from the list above. Thanks! |
Thanks. I've filled missing items in https://incubator.apache.org/ip-clearance/arrow-julia-library2.html and started vote: https://lists.apache.org/thread/f9xck9j8qdrhvw363vjl6qkk2g8t4l6b If we don't receive -1 vote at least 72 hours, the vote can be passed. |
The vote passed: https://lists.apache.org/thread/byc3voz57qpgr63xdc7bs0q7626n2k0v @quinnj INFRA may need admin permission to this repository. Please watch https://issues.apache.org/jira/browse/INFRA-22663 and respond to requests from INFRA. |
Repo has been transferred |
As has been discussed in a few places (slack, arrow-dev mailing list, etc.), we'd like to transfer this repo to the apache organization in our efforts to officially participate in the broader arrow community and project. For the mechanics of the transfer, @kou has very helpfully laid out the plan and TODO items here and we can track the current state of the transfer here.
There is a request to NOT merge any more commits until the transfer is complete; cc active committers: @omus, @jrevels.
To complete the transfer, we just need signed CLAs for the following individuals:
This list is as computed by @kou for more-than-1-commit since the original donation of the repo to the arrow project. The required CLA can be found here. @jrevels , @omus , @ericphanson, as also noted, if your collective contributions should be viewed under a "corporate" contribution, there's a separate corporate CLA. Happy to chat more if that doesn't make sense or whatever.
Let's do this!
The text was updated successfully, but these errors were encountered: