Chair/Technical Lead access for @jeremyrickard

[justaugustus]

GitHub Username

@jeremyrickard

Chair/Technical Lead role

Technical Lead
ref: https://groups.google.com/g/kubernetes-dev/c/78E3IobBKH0

Chair and Technical Lead Onboarding

All pull requests within these checklists should be marked with an explicit
hold and only released once approved by a SIG Release (subproject) owner.

• Addition of a new Release Manager has been discussed with and approved by
  SIG Release owners
• Ensure new Chair/Technical Lead:
  • Has joined the following mailing lists:
    • kubernetes-sig-release
    • kubernetes-release-team
    • kubernetes-dev
    • kubernetes-announce
    • release-managers
    • release-managers-private
  • Has joined the following Slack channels:
    • #sig-release
    • #release-management
  • Is a Kubernetes GitHub org member
  • Is part of the @kubernetes/sig-release-admins GitHub team
• Update Release Managers page to include the new Chair or Technical Lead

Chair/Technical Lead

• Chair/Technical 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 Chair/Technical Lead.)
• Update GitHub teams (kubernetes/org)
  • milestone-maintainers
  • release-engineering
  • release-managers
  • sig-release-admins
• Update OWNERS
  • kubernetes/sig-release OWNERS_ALIASES (Update SECURITY_CONTACTS #1401)
    • Add entry in the sig-release-leads section
  • kubernetes/release OWNERS_ALIASES (Update SECURITY_CONTACTS release#1832)
    • Add entry in the sig-release-leads section
  • kubernetes/test-infra OWNERS_ALIASES (Update sig-release-leads OWNERS_ALIASES test-infra#20372)
    • Add entry in the sig-release-leads section
  • kubernetes/kubernetes OWNERS_ALIASES (OWNERS: Update SIG Release aliases kubernetes#97700)
    • Add entry in the sig-release-approvers section
  • kubernetes/k8s.io OWNERS_ALIASES (groups: Add Jeremy Rickard as a SIG Release Technical Lead k8s.io#1529)
    • Add entry in the release-engineering-approvers section
• Update SECURITY_CONTACTS
  • kubernetes/release (Update SECURITY_CONTACTS release#1832)
  • kubernetes/sig-release (Update SECURITY_CONTACTS #1401)
• Update Google Groups/GCP IAM membership (kubernetes/k8s.io) (groups: Add Jeremy Rickard as a SIG Release Technical Lead k8s.io#1529)
  • leads (members)
  • k8s-infra-release-admins (members)
  • k8s-infra-release-editors (members)
  • release-comms (owners)
  • release-managers (owners)
  • release-managers-private (owners)
• Manually grant permission to post on kubernetes-announce
• Manually add to the Release Team Google Group (groups: Add Jeremy Rickard as a SIG Release Technical Lead k8s.io#1529)
• Update Slack release-managers and release-team-leads User Group (kubernetes/community) (slack-config: Add Jeremy Rickard as a SIG Release Technical Lead community#5407)
• Manually add to the #release-private Slack channel

Dan already has a set of PRs in-flight, so I'll leave him to handle this onboarding.
/assign @hasheddan
cc: @kubernetes/sig-release-admins

[saschagrunert]

I think this is mostly done, right @justaugustus ? @jeremyrickard can you double check that you have all permissions?

[jeremyrickard]

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

[jeremyrickard]

@saschagrunert looks good, except for: I don't have posting permissions for Kubernetes-announce. If I don't need that, i think we are good.

[saschagrunert]

@saschagrunert looks good, except for: I don't have posting permissions for Kubernetes-announce. If I don't need that, i think we are good.

I think those permissions have to be granted manually, right @justaugustus?

[jeremyrickard]

I think the posting permission is only relevant for patch announcements and what not, so I think this is good. I'll open an issue if I need this in the future.

/close

[k8s-ci-robot]

@jeremyrickard: Closing this issue.

In response to this:

I think the posting permission is only relevant for patch announcements and what not, so I think this is good. I'll open an issue if I need this in the future.

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