Closed leonardpahlke closed 2 years ago
+1 from my side
sigs.k8s.io/application-analysis
How about a more SIG Release related name, like release-team-shadow-stats? (Ugh, naming.)
sounds good to me :+1:
@leonardpahlke :wave: There are a few more things we'll need to do as prerequisites for migrating the repo:
Once the above two items are done, please ping me here (or on slack) and I'll help you with the migration :+1:
Done +1
/assign
Repo has been created - https://github.com/kubernetes-sigs/release-team-shadow-stats
Also created:
Once both PRs merge, we can close this issue.
2nd PR should be merged shortly, going to go ahead and close his out
/close
@mrbobbytables: Closing this issue.
New repo, staging repo, or migrate existing
Is it a staging repo?
no
Requested name for new repository
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
@sig-release-admins
Who should have write access?
@sig-release-admins
Who should be listed as approvers in OWNERS?
@sig-release-admins
Who should be listed in SECURITY_CONTACTS?
@sig-release-admins
What should the repo description be?
What SIG and subproject does this fall under?
SIG Release
Please provide references to appropriate approval for this new repo
This tool has been discussed in sig-release
Additional context for request
@kubernetes/owners cc: @kubernetes/sig-release-admins