Skip to content
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

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

Open
6 tasks done
divya-mohan0209 opened this issue May 10, 2024 · 5 comments
Open
6 tasks done
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/docs Categorizes an issue or PR as relevant to SIG Docs. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@divya-mohan0209
Copy link
Contributor

divya-mohan0209 commented May 10, 2024

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

@k8s-ci-robot k8s-ci-robot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 10, 2024
@divya-mohan0209 divya-mohan0209 added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 10, 2024
@natalisucks
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 10, 2024
@natalisucks
Copy link
Contributor

@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
Copy link
Contributor Author

divya-mohan0209 commented May 10, 2024

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

@salaxander
Copy link
Contributor

All my PRs have been created:

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

@katcosgrove
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/docs Categorizes an issue or PR as relevant to SIG Docs. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants