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

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

Open
siwiutki opened this issue Dec 10, 2024 · 3 comments
Open

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

siwiutki opened this issue Dec 10, 2024 · 3 comments
Labels
area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository

Comments

@siwiutki
Copy link

siwiutki commented Dec 10, 2024

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.

@siwiutki siwiutki added the area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository label Dec 10, 2024
@aojea
Copy link
Member

aojea commented Dec 11, 2024

@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
Copy link
Member

aojea commented Dec 11, 2024

/lgtm
/approve

Thanks

@Priyankasaggu11929
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-repo Creating, migrating or deleting a Kubernetes GitHub Repository
Projects
None yet
Development

No branches or pull requests

3 participants