Steering onboarding - @justaugustus + @tpepper

[justaugustus]

Steering Onboarding

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

Initial steps

• [x] All new members must complete the Inclusive Leadership Training within 30 days from the date of their appointment.
  • [x] @justaugustus certificate ID number: LF-zhwaqh4h1z
  • [x] @tpepper certificate ID number: LF-zr308bplvo
• [x] Update the following files in the respective repos:
  • x: OWNERS_ALIASES and README.md: https://github.com/kubernetes/steering/pull/220
  • x:
  • [x] sigs.yaml (SC members and liaisons) and auto-generated content: https://github.com/kubernetes/community/pull/6212
  • [x] slack usergroup - communication/slack-config/usergroups.yaml, communication/slack-config/users.yaml: https://github.com/kubernetes/community/pull/6212
  • x: OWNERS_ALIASES and the steering-committee: https://github.com/kubernetes/org/pull/3086
  • x: OWNERS_ALIASES: https://github.com/kubernetes/website/pull/30411
  • x: OWNERS_ALIASES: https://github.com/kubernetes/funding/pull/25
  • x:
  • [x] update steering@kubernetes.io and steering-private@kubernetes.io in groups/groups.yaml: https://github.com/kubernetes/k8s.io/pull/3051
  • [x] OWNERS_ALIASES: https://github.com/kubernetes/k8s.io/pull/3059
• [x] Add new members to the steering-private slack channel
• [x] 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
• [x] 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
• [x] Add new members to the Public CNCF Maintainer List and remove emeritus members: https://github.com/cncf/foundation/pull/229
  • @nikhita needs to remain listed in her role as a SIG ContribEx lead
• [x] Transfer Community Group liaison assignments from emeritus members to new members: https://github.com/kubernetes/community/pull/6231
• [x] (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
• [x] (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
• [x] (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
• [x] Set up a private meeting to go over backlog

After handoff meeting

• [x] Remove emeritus members from the steering-private slack channel

---

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

[justaugustus]

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 https://github.com/kubernetes/steering/issues/222 to validate.

[justaugustus]

/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to [this](https://github.com/kubernetes/steering/issues/219#issuecomment-990662116): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.