Steering member transition: @parispittman --> @cpanato

[justaugustus]

Steering member transition: @parispittman --> @cpanato

With @parispittman stepping down from the committee, we need to transition her seat to a new member.

Based on the results of this year's election, Cici Huang (Google) (@cici37) would be the next in line for Steering, however, due to maximal representation (Ben and Bob are also Googlers), the next seat would go to Carlos Panato (Chainguard) (@cpanato).

NOTE(@justaugustus): These items were initially copied from https://github.com/kubernetes/steering/issues/256. I'll be reviewing and cleaning up this list as we action on the items.

Initial steps

• [x] All new members must complete the Inclusive Leadership Training within 30 days from the date of their appointment.
  • [x] @cpanato certificate ID number: LF-mn8udh5gy6
• [x] Update the following files in the respective repos:
  • x: OWNERS_ALIASES and README.md: https://github.com/kubernetes/steering/pull/261
  • • sigs.yaml (SC members and liaisons) and auto-generated content
    • slack usergroup - communication/slack-config/usergroups.yaml, communication/slack-config/users.yaml
  • x: OWNERS_ALIASES and the steering-committee: https://github.com/kubernetes/org/pull/3847
  • x: OWNERS_ALIASES: https://github.com/kubernetes/website/pull/38004
  • x: OWNERS_ALIASES: https://github.com/kubernetes/funding/pull/36
  • • update groups/groups.yaml:
    • steering@kubernetes.io
    • steering-emeritus@kubernetes.io
    • steering-private@kubernetes.io
    • OWNERS_ALIASES
• [x] Add new members to the steering-private slack channel
• [x] Add new members to the CNCF Service Desk and remove emeritus members
• [ ] Add new members to the cncf-kubernetes-maintainers mailing list and remove emeritus members
• [x] Add new members to the Public CNCF Maintainer List and remove emeritus members: https://github.com/cncf/foundation/pull/460
• [x] Transfer Community Group liaison assignments from emeritus members to new members: https://github.com/kubernetes/community/pull/6974
• [x] If a Google Workspace top-level account is owned by an emeritus member, transfer it to an existing member (currently owned by @justaugustus, @parispittman, and @mrbobbytables)
  • [x] @parispittman to handoff to @palnabarun
• [ ] 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] 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/blob/5a0edcffc51e819a8349fee34f32b6568d2e4323/README.md#zoom-admins
• [x] Add new members to 1password, remove emeritus members
• [ ] 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 @parispittman @cpanato

[justaugustus]

From @mrbobbytables in https://kubernetes.slack.com/archives/CPNFRNLTS/p1669042948278349?thread_ts=1669042812.147799&cid=CPNFRNLTS:

we can probably remove the zoom step as those creds are in there

👍🏽

[mrbobbytables]

If an emeritus member is one of the https://github.com/kubernetesio Twitter account contributors, transfer access to an existing member

Will need to poke CNCF about this, I just checked and only team admins can make the change.

[BenTheElder]

Anything left here @cpanato @justaugustus ?

[cpanato]

i dont think so. but if there is anything we can do adhoc /close

[k8s-ci-robot]

@cpanato: Closing this issue.

In response to [this](https://github.com/kubernetes/steering/issues/260#issuecomment-1498896034): >i dont think so. but if there is anything we can do adhoc >/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.