Release Team Lead access for @cici37 @jlbutler @salaxander @gracenng @leonardpahlke

[cici37]

GitHub Username(s)

• @cici37
• @jlbutler
• @salaxander
• @gracenng
• @leonardpahlke

Release Cycle

Kubernetes 1.25

Prerequisites

• [x] Ensure new Release Team Lead:
  • [x] Has joined the following mailing lists:
    • kubernetes-sig-release
    • kubernetes-dev
  • [x] Has joined the following Slack channels:
    • #sig-release
    • #release-management
  • [x] Is a Kubernetes GitHub org member
  • [x] Has completed the CNCF Inclusive Speaker Orientation

Onboarding

• [x] Release Team Lead has agreed to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications. This must be done as an issue comment by the incoming Release Team Lead.
• [x] Update GitHub teams (kubernetes/org)
  • milestone-maintainers
  • release-team
  • release-team-leads
  • sig-release
• [x] Update kubernetes/sig-release OWNERS
  • Release Team Lead and Shadows
    • Add an approvers entry in releases/release-x.y/OWNERS
  • Release Team Lead only
    • In OWNERS_ALIASES, add an entry in the following sections:
      • release-team
      • release-team-lead-role
• [x] Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
  • k8s-infra-release-viewers@
  • release-managers@
  • release-team@
• [x] Grant calendar access
• [x] Grant Zoom credentials (host key)
• [x] Add incoming leads to release-team-leads Slack Group (kubernetes/community)
  • Add slack ID(s) to users.yaml, if they are not yet in the file
  • Add username(s) to usergroups.yaml

Offboarding

• [ ] Remove from GitHub teams (kubernetes/org)
  • milestone-maintainers
  • release-team
  • release-team-leads
• [ ] Remove from Google Groups/GCP IAM membership (kubernetes/k8s.io)
  • k8s-infra-release-viewers@
  • release-managers@
• [ ] Manually remove from the following Google Groups:
  • kubernetes-release-team (Add as Manager)
  • kubernetes-sig-leads (Add as Member)
• [ ] Remove from release-team-leads Slack Group (kubernetes/community)
  • Remove slack ID(s) from users.yaml, if no longer in a group
  • Remove username(s) from usergroups.yaml

cc: @kubernetes/release-engineering @kubernetes/release-team

[cici37]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF3ontws1w6c I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[leonardpahlke]

Me too, link to the LFC101 Certificate I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[jlbutler]

I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

I have previously completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF7pd08wfey1

[salaxander]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-13yswrm0q7

I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[gracenng]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-ocllb99cdq

I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[leonardpahlke]

Closing this issue. (The offboarding checkboxes are implicitly checked by the onboarding of the 1.26 team).

/close

[k8s-ci-robot]

@leonardpahlke: Closing this issue.

In response to this:

Closing this issue. (The offboarding checkboxes are implicitly checked by the onboarding of the 1.26 team).

/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.