Steering onboarding - @justaugustus + @tpepper

[Stephen Augustus]

Steering Onboarding

This document covers steps needed to onboard new Steering Committee
members and off-board emeritus members.

Initial steps

• All new members must complete the Inclusive Leadership Training
  within 30 days from the date of their appointment.
  • @justaugustus certificate ID number: LF-zhwaqh4h1z
  • @tpepper certificate ID number: LF-zr308bplvo
• Update the following files in the respective repos:
  • kubernetes/steering: OWNERS_ALIASES and README.md: #220
  • kubernetes/community:
    • sigs.yaml (SC members and liaisons) and auto-generated content: kubernetes/community#6212
    • slack usergroup - communication/slack-config/usergroups.yaml, communication/slack-config/users.yaml: kubernetes/community#6212
  • kubernetes/org: OWNERS_ALIASES and the steering-committee: kubernetes/org#3086
  • kubernetes/website: OWNERS_ALIASES: kubernetes/website#30411
  • kubernetes/funding: OWNERS_ALIASES: kubernetes/funding#25
  • kubernetes/k8s.io:
    • update [e-mail] and [e-mail] in groups/groups.yaml: kubernetes/k8s.io#3051
    • OWNERS_ALIASES: kubernetes/k8s.io#3059
• Add new members to the steering-private slack channel
• Add new members to the CNCF Service Desk and remove emeritus members
  • @nikhita needs to remain listed in her role as a SIG ContribEx lead
• Add new members to the cncf-kubernetes-maintainers mailing list and remove emeritus members
  • @nikhita needs to remain listed in her role as a SIG ContribEx lead
• Add new members to the Public CNCF Maintainer List and remove emeritus members: cncf/foundation#229
  • @nikhita needs to remain listed in her role as a SIG ContribEx lead
• Transfer Community Group liaison assignments from emeritus members to new members: kubernetes/community#6231
• (N/A) If a Google Workspace top-level account is owned by an emeritus member,
  transfer it to an existing member
  • Currently owned by @dims, @parispittman, and @mrbobbytables
• (N/A) If an emeritus member is one of the @kubernetesio Twitter account contributors,
  transfer access to an existing member
  • Currently owned by @parispittman and @mrbobbytables: https://github.com/kubernetes/community/blob/35d8e8cc6a5165352e92ec17d5bf9e892e653bc7/communication/marketing-team/social-guidelines.md
• (N/A) If Zoom license credentials were owned by a majority of emeritus
  members, share them with existing members. The Zoom host key is
  accessible to all members and is a pinned message in the steering-private
  slack channel
  • Currently owned by @parispittman, @cblecker, and @mrbobbytables: https://github.com/kubernetes/steering/tree/7abf985b52a75957efdca70f01671c79eca4e9d4#zoom-admins
• Set up a private meeting to go over backlog

After handoff meeting

• Remove emeritus members from the steering-private slack channel

---

I'll take point on the PRs:
/assign @justaugustus @tpepper

[Stephen Augustus]

The last remaining item (which is in-flight is):

Add new members to the cncf-kubernetes-maintainers mailing list and remove emeritus members

I'm pretty sure this is already done, but I'll use #222 to validate.

[Stephen Augustus]

/close

[Kubernetes Prow Robot]

@justaugustus: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.