REQUEST: Migrate siwiutki/nat64 to kubernetes-sigs/nat64

[siwiutki]

New repo, staging repo, or migrate existing

migrate existing

Is it a staging repo?

no

Requested name for new repository

nat64

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

aojea, danwinship, thockin

Who should have write access?

aojea, danwinship, thockin

Who should be listed as approvers in OWNERS?

aojea, danwinship, thockin

Who should be listed in SECURITY_CONTACTS?

aojea, danwinship, thockin

What should the repo description be?

NAT64 agent for Kubernetes deployments

What SIG and subproject does this fall under?

sig-network

Please provide references to appropriate approval for this new repo

https://groups.google.com/g/kubernetes-sig-network/c/-vOSMUlzYfE

Additional context for request

This was already discussed and approved on SIG network call and demo was presented on the call.

[aojea]

@siwiutki please update the description

Who should have admin access?
aojea, danwinship, thockin

Who should have write access?
aojea, danwinship, thockin

Who should be listed as approvers in OWNERS?
aojea, danwinship, thockin

Who should be listed in SECURITY_CONTACTS?
aojea, danwinship, thockin

What should the repo description be?
NAT64 agent for Kubernetes deployments 

[aojea]

/lgtm
/approve

Thanks

[Priyankasaggu11929]

@siwiutki @aojea, per the rules for donated repositories, could you please update the content of the https://github.com/siwiutki/nat64 repo to confirm/include/address:

• All contributors must have signed the CNCF Individual CLA or CNCF Corporate CLA
• If (a) contributor(s) have not signed the CLA and could not be reached, a NOTICE file should be added referencing section 7 of the CLA with a list of the developers who could not be reached
• Licenses of dependencies are acceptable; please review the allowed-third-party-license-policy.md and exceptions. If your dependencies are not covered, then please open a License Exception Request issue in cncf/foundation repository.
• Boilerplate text across all files should attribute copyright as follows: "Copyright " if no CLA was in place prior to donation
• Additions of the standard Kubernetes header to code created by the contributors can occur post-transfer, but should ideally occur shortly thereafter.
• Should contain template files as per the kubernetes-template-project.

Once above is confirmed, I'll start the repo migration process. Thanks!

[aojea]

@Priyankasaggu11929 I run through the repo and I think we are ready and we can cross all open items, I can see the licenses are allowed and the boilerplate in place.

In the beginenning the sig-net leads will take ownership of the repo, but I expect @siwiutki to get membership soon and take over as an official contributor of kubernetes

[Priyankasaggu11929]

I run through the repo and I think we are ready and we can cross all open items, I can see the licenses are allowed and the boilerplate in place.

In the beginenning the sig-net leads will take ownership of the repo, but I expect @siwiutki to get membership soon and take over as an official contributor of kubernetes

Thank you @aojea @siwiutki.
@siwiutki – could you please confirm if you have signed the CNCF CLA as well?

Also @siwiutki, I'm sending you an invite to add you to an intermediary Kubernetes github org.
Please transfer the https://github.com/siwiutki/nat64 repo to the intermediary GitHub org. I'll transfer it further to requested kubernetes-sigs org from there.

[siwiutki]

@Priyankasaggu11929 Even though I joined the intermediary Kubernetes github org that you invited me to, it seems like I don't have permissions to transfer siwiutki/nat64 to that org. Am I missing something? I'm following this process from GitHub docs to migrate the repository.

[Priyankasaggu11929]

Hi @siwiutki, just updated the permissions for you. I think repo transfer should work now.

If not, please let me know, I'll try to help further. Thanks! :)

[Priyankasaggu11929]

Hello @siwiutki @aojea, I'm blocked on the transfer of repo, due to the org level settings on kubernetes-sigs.
We will need (kubernetes-sigs) org membership for @siwiutki.

@siwiutki, could you please use this template to create a new org membership request. Thanks!

[siwiutki]

@Priyankasaggu11929 I created #5340, PTAL

[siwiutki]

@Priyankasaggu11929 I'm now part of kubernetes-sigs organization, feel free to continue the migration process.

@Priyankasaggu11929 I run through the repo and I think we are ready and we can cross all open items, I can see the licenses are allowed and the boilerplate in place.

In the beginenning the sig-net leads will take ownership of the repo, but I expect @siwiutki to get membership soon and take over as an official contributor of kubernetes

Following @aojea comment, I think I can now be officially added as an owner as well, now that I'm a member of kubernetes-sigs. Let me know if any action is required on my side (modify this request, do some PR to kubernetes-purgatory/nat64, etc.) for that.

[Priyankasaggu11929]

Repo is now transferred to kubernetes-sigs org — https://github.com/kubernetes-sigs/nat64

I've created PR to add gh teams (admin & maintainers) for the new repo — #5358

Questions:

• @aojea, the new nat64 repo will be a new subproject, or part of an existing subproject of SIG Network?
• (I missed it before) is the new repo intended to stay a fork of aojea/nat64 or it should be a standalone repo now?
  If latter, we will need to detach it from the fork. I can help, once it is confirmed (we will need to delete the forked repo, and push the cloned content to a new repo with same name).

Following @aojea comment, I think I can now be officially added as an owner as well, now that I'm a member of kubernetes-sigs.

@siwiutki, yes, it would be a direct PR to kubernetes-sigs/nat64 now.

[aojea]

It will be a subproject of pod-networking
https://github.com/kubernetes/community/tree/master/sig-network#pod-networking

Standalone repo, we can detach it from the fork

[Priyankasaggu11929]

It will be a subproject of pod-networking https://github.com/kubernetes/community/tree/master/sig-network#pod-networking

Thanks @aojea. I've created documentation PR — kubernetes/community#8290, PTAL.

Standalone repo, we can detach it from the fork

@aojea, @siwiutki – I'll wait for your confirmation that
(i) there's a local clone available (with all content and git metadata), (steps in doc), and
(ii) I can delete the current (forked) kubernetes-sigs/nat64 repo and re-create an empty repo with the same name, to detach from fork.

Once new repo is in place, then we can push the locally cloned content back to the new repo.

I'll proceed after the confirmation. Thanks!

[aojea]

@Priyankasaggu11929 please proceed

[Priyankasaggu11929]

@Priyankasaggu11929 please proceed

Ack. Deleting the current forked repo.

[Priyankasaggu11929]

@aojea, new empty repo created – https://github.com/kubernetes-sigs/nat64

[Priyankasaggu11929]

@aojea, @siwiutki, this request is now complete, from my end. Let me know if anything else is needed. Thanks!

[aojea]

Thank you very much for your help, I checked it is working so I think we can close

/close

[k8s-ci-robot]

@aojea: Closing this issue.

In response to this:

Thank you very much for your help, I checked it is working so I think we can close

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.