Closed pmorie closed 3 years ago
Considering this "approved" since @pmorie is a chair for SIG Multicluster
/assign
Repo has been created - https://github.com/kubernetes-sigs/work-api
@qiujian16 is not a member of @kubernetes-sigs or @kubernetes GitHub orgs so they would need to request for membership.
Also created:
Once both PRs merge, we can close this issue. :+1:
Teams have been granted access and all related PRs have merged. Closing.
/milestone v1.21
New Repo, Staging Repo, or migrate existing
New Repo
Requested name for new repository
work-api
Which Organization should it reside
e.g. kubernetes-sigs
If not a staging repo, who should have admin access
pmorie, jeremyot, jqiu (qiujian16)
If not a staging repo, who should have write access
pmorie, jeremyot, jqiu (qiujian16)
If not a staging repo, who should be listed as approvers in OWNERS
pmorie, jeremyot, jqiu (qiujian16)
If not a staging repo, who should be listed in SECURITY_CONTACTS
pmorie, jeremyot, jqiu (qiujian16)
What should the repo description be
Kubernetes Work API
What SIG and subproject does this fall under in sigs.yaml
This is a new subproject of sig-multicluster called work-api
Approvals
Please prove you have followed the appropriate approval process for this new repo by including links to the relevant approvals (meeting minutes, e-mail thread, etc.)
Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md
tl;dr (but really you should read the linked doc, this may be stale)
Additional context for request
This will hold design documents and implementation of the Work API