[Umbrella tracking issue] SIG Docs Tech Leads onboarding: Kat & Xander

[divya-mohan0209]

Note for contributors: We are NOT ACCEPTING contributions for this issue from new/experienced contributors since this is to onboard our new tech leads, Kat & Xander. The PRs need to be submitted by them.

SIG Docs Tech Leads onboarding

On 30th April, Kat Cosgrove and Xander Grzywinski were nominated as the new tech leads for SIG Docs.

Transition date

A lazy consensus period till 8th May was also announced in the aforementioned nomination.

Required changes

Tech Lead onboarding requires some changes outlined below:

Kat Cosgrove

Repo	file	Complete?
k/community	OWNERS_ALIASES
k/community	sig-docs/README.md
k/community	sig-list.md
k/community	sigs.yaml
k/enhancements	OWNERS_ALIASES
k/org	OWNERS_ALIASES
k/website OWNERS	OWNERS_ALIASES
k/website en OWNERS	OWNERS_ALIASES
k/website en REVIEWERS	OWNERS_ALIASES
k/website	SECURITY_CONTACTS
kubernetes-sigs/reference	OWNERS

External tools you will need access to:

• Netlify => Collaborator access to be requested & documented.
• k8s-sig-docs-leads@ Google Group => Membership to be requested
• Google Analytics access => Will be automatically granted once access to k8s-sig-docs-leads@ Google Group is sorted.

Xander Grzywinski

Repo	file	Complete?
k/community	OWNERS_ALIASES
k/community	sig-docs/README.md
k/community	sig-list.md
k/community	sigs.yaml
k/enhancements	OWNERS_ALIASES
k/org	OWNERS_ALIASES
k/website OWNERS	OWNERS_ALIASES
k/website en OWNERS	OWNERS_ALIASES
k/website en REVIEWERS	OWNERS_ALIASES
k/website	SECURITY_CONTACTS
kubernetes-sigs/reference	OWNERS

External tools you will need access to:

• Netlify => Collaborator access to be requested & documented.
• k8s-sig-docs-leads@ Google Group => Membership to be requested
• Google Analytics access => Will be automatically granted once access to k8s-sig-docs-leads@ Google Group is sorted.

cc: @natalisucks @reylejano

/sig docs

[natalisucks]

/triage accepted

[natalisucks]

@divya-mohan0209 One other area that our new TLs will need to add themsleves to is the reference docs, and we'll need to make sure our onboarding is updated to reflect this: https://github.com/kubernetes-sigs/reference-docs/blob/master/OWNERS

[divya-mohan0209]

@natalisucks : Thanks for the catch, lemme add that on to the checklists above for both Kat & Xander.

[salaxander]

All my PRs have been created:

kubernetes/community#7891
kubernetes/enhancements#4626
kubernetes/org#4941
#46312
kubernetes-sigs/reference-docs#361

[katcosgrove]

All of my PRs are here:

kubernetes/community#7893
#46345
kubernetes/org#4947
kubernetes/enhancements#4630
kubernetes-sigs/reference-docs#362

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted