Skip to content
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

Closed
4 tasks done
quinnj opened this issue Dec 7, 2021 · 19 comments
Closed
4 tasks done

Transfer repository to apache organization #265

quinnj opened this issue Dec 7, 2021 · 19 comments

Comments

@quinnj
Copy link
Member

quinnj commented Dec 7, 2021

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!

@jrevels
Copy link
Contributor

jrevels commented Dec 7, 2021

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.

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?

@dmbates
Copy link
Contributor

dmbates commented Dec 7, 2021

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?

@quinnj
Copy link
Member Author

quinnj commented Dec 7, 2021

I think it's fine to use arrow or arrow-julia as the project box, preferring arrow. Yes, you only need to email and then if you'd check your name off hte list above that'd be great.

@jrevels, it's probably safest to do both then.

@ericphanson
Copy link
Member

I’ve submitted my ICLA, can someone check me off the list? (I don’t have permission)

@quinnj
Copy link
Member Author

quinnj commented Dec 14, 2021

@jrevels, @omus, @KristofferC; any update?

@omus
Copy link
Contributor

omus commented Dec 14, 2021

I'll submit mine tomorrow

@quinnj
Copy link
Member Author

quinnj commented Dec 14, 2021

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

@KristofferC
Copy link
Contributor

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:

  1. You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others).

which is not true for the PR #250 since I copy-pasted it from somewhere.

@kou
Copy link
Member

kou commented Dec 14, 2021

@KristofferC It makes sense.

@omus
Copy link
Contributor

omus commented Dec 15, 2021

I've submitted my ICLA and have checked myself off the list

@jrevels
Copy link
Contributor

jrevels commented Dec 15, 2021

I’m in the middle of traveling but will also try to care of this by EOW

@jrevels
Copy link
Contributor

jrevels commented Dec 21, 2021

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.

@quinnj
Copy link
Member Author

quinnj commented Dec 22, 2021

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.

@kou
Copy link
Member

kou commented Dec 23, 2021

OK.
Could you remove @KristofferC from the list in this description or add a note that "CLS isn't needed because ..."?
I'll add a link to this issue to https://incubator.apache.org/ip-clearance/arrow-julia-library2.html .

Did you do the following?

  1. Remind active committers that they are responsible for
    ensuring that a Corporate CLA is recorded if such is
    required to authorize their contributions under their
    individual CLA.

And could you also remind

53 Jacob Quinn
16 Jarrett Revels
10 Curtis Vogt
8 Eric Hanson
2 Douglas Bates
2 ExpandingMan
2 Kristoffer Carlsson

that the TODO item 2.?

I need to record the date when we did it in https://incubator.apache.org/ip-clearance/arrow-julia-library2.html .

@quinnj
Copy link
Member Author

quinnj commented Dec 23, 2021

Did you do the following?

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!

@kou
Copy link
Member

kou commented Dec 23, 2021

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.
I'll ask INFRA to transfer this repository to apache/arrow-julia after the vote is passed.

@jrevels
Copy link
Contributor

jrevels commented Dec 23, 2021

Thanks to both @quinnj and @kou for facilitating this process!

@kou
Copy link
Member

kou commented Dec 26, 2021

The vote passed: https://lists.apache.org/thread/byc3voz57qpgr63xdc7bs0q7626n2k0v
I asked INFRA to transfer this repository to apache/arrow-julia: https://issues.apache.org/jira/browse/INFRA-22663

@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.

@quinnj
Copy link
Member Author

quinnj commented Dec 30, 2021

Repo has been transferred

@quinnj quinnj closed this as completed Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants