Description
New Repo, Staging Repo, or migrate existing
migrate existing (https://github.com/kubernetes-incubator/reference-docs)
Requested name for new repository
reference-docs
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
- bradamant3
- jimangel
- zacharysarah
If not a staging repo, who should have write access
- tengqm
- kbhawkey
If not a staging repo, who should be listed as approvers in OWNERS
- bradamant3
- bradtopol
- kbarnard10
- steveperry-53
- tengqm
- zacharysarah
- zparnold
- kbhawkey
If not a staging repo, who should be listed in SECURITY_CONTACTS
- bradamant3
- jimangel
- zacharysarah
- tengqm
What should the repo description be
Tools to build reference documentation for Kubernetes APIs and CLIs.
What SIG and subproject does this fall under in sigs.yaml
This is a subproject of sig-docs
Approvals
This subproject, reference-docs, is outlined as being in-scope as part of the sig-docs charter. An issue kubernetes/website#13904 was opened after the 1.14 release about this repo moving locations as well as discussed in the 9/3 sig-docs community meeting.
Additional context for request
Since this repo is used for each release and iterated on, I would like to /hold the migration until 1.16 is out the door.
Addt'l items:
- We'll need to PR fixes to these references
- We'll need to merge or hold: [WIP] Testing restyled kubectl ref docs kubernetes-sigs/reference-docs#82
- Related k/website issue for tracking: Relocate reference generation tooling from Kubernetes Incubator website#13904
Note: I took a guess at which users should be included as well as permissions. It could use a second set of 👀
/cc @zacharysarah @Bradamant3 @kbarnard10 @simplytunde @tengqm @kbhawkey