-
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/wg-serving #5072
Comments
/cc @smarterclayton |
LGTM. Thanks! |
I assume we can create owners file for different directories, right? |
Tha will be a prow config for the repo. |
lgtm. |
/assign @mrbobbytables |
Repo is live at: https://github.com/kubernetes-sigs/wg-serving |
repo has been created 👍 |
/close |
@ArangoGutierrez: Closing this issue. In response to this:
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. |
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
wg-serving
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
ArangoGutierrez, Jeffwan, SergeyKanzhelev, terrytangyuan
Who should have write access?
ArangoGutierrez, Jeffwan, SergeyKanzhelev, terrytangyuan
Who should be listed as approvers in OWNERS?
ArangoGutierrez, Jeffwan, SergeyKanzhelev, terrytangyuan
Who should be listed in SECURITY_CONTACTS?
ArangoGutierrez, Jeffwan, SergeyKanzhelev, terrytangyuan
What should the repo description be?
Templates and designs for WG Serving.
What SIG and subproject does this fall under?
SIG Architecture, SIG Apps, SIG Node, SIG Scheduling, SIG Network
Please provide references to appropriate approval for this new repo
This is for experimental work, and collect community designs from the new working group, which is sponsored by SIG Arch, Node, Network, Autoscaling, and Scheduling.
Additional context for request
No response
The text was updated successfully, but these errors were encountered: