- 
                Notifications
    You must be signed in to change notification settings 
- Fork 791
Closed
Labels
area/github-repoCreating, migrating or deleting a Kubernetes GitHub RepositoryCreating, migrating or deleting a Kubernetes GitHub Repository
Description
New Repo, Staging Repo, or migrate existing
Migrate existing packethost/cluster-api-provider-packet
Requested name for new repository
cluster-api-provider-packet
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
If not a staging repo, who should have write access
@gianarb @deitch @jacobsmith928 @mrmrcoleman probably we need a team for it: cluster-api-packet-maintainers
If not a staging repo, who should be listed as approvers in OWNERS
This is the issue that tracks this work: kubernetes-retired/cluster-api-provider-packet#114
If not a staging repo, who should be listed in SECURITY_CONTACTS
This is the issue that tracks this work: kubernetes-retired/cluster-api-provider-packet#121
What should the repo description be
"Packet Cloud Provider for Cluster API"
What SIG and subproject does this fall under in sigs.yaml
sig-cluster-lifecycle
Approvals
- Wed 10 June during cluster-api Office Hour, we raised our desire to move the repo under kubernetes-sigs. The video will be linked as soon as available.
Additional context for request
16th June I will bring this topic to sig-cluster-lifecycle be-weekly meeting because for now I just had a chat in ClusterAPI meeting. Will update this PR with more information
Metadata
Metadata
Labels
area/github-repoCreating, migrating or deleting a Kubernetes GitHub RepositoryCreating, migrating or deleting a Kubernetes GitHub Repository