-
Notifications
You must be signed in to change notification settings - Fork 693
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: Create repository kubernetes-sigs/cni-dra-driver #5228
Comments
/lgtm |
1 similar comment
/lgtm |
/assign New repo is created – https://github.com/kubernetes-sigs/cni-dra-driver PR to add GitHub teams for the new repo – #5248
@LionelJouin, new repo will be (i) a new subproject of SIG Network, OR (ii) part of an existing subproject of sig-network? |
@MikeZappa87 is an existing member of kubernetes org, not kubernetes-sigs. I'll create a new PR to fix it. Thanks again! PR – #5249 |
I will put it under https://github.com/kubernetes/community/tree/master/sig-network#pod-networking |
PR to document new repo in k/community – https://github.com/kubernetes/community/pull/8141/files Once PR is merged, the repo creation is complete. Thanks! |
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
cni-dra-driver
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
@LionelJouin ; @aojea ; @MikeZappa87
Who should have write access?
@LionelJouin ; @aojea ; @MikeZappa87
Who should be listed as approvers in OWNERS?
@LionelJouin ; @aojea ; @MikeZappa87
Who should be listed in SECURITY_CONTACTS?
@LionelJouin ; @aojea ; @MikeZappa87
What should the repo description be?
CNI DRA Driver
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/8Jfm_Qa-Bl0
https://groups.google.com/a/kubernetes.io/g/wg-device-management/c/E_vIab0M2cA
https://github.com/containernetworking/meeting-notes/blob/main/MEETING-NOTES.md (2024-10-14 ; 2024-10-21)
Additional context for request
No response
The text was updated successfully, but these errors were encountered: