kubernetes/committee-security-response

Offboard @lukehinds

cji opened this issue · 4 comments

cji commented

This was already started but opening this to make sure we get everything.

  • kubernetes/security PR: #181
    • README.md
    • OWNERS_ALIASES
  • kubernetes/k8s.io PR: kubernetes/k8s.io#5396
    • groups/security-response-committee/groups.yaml
      • security@kubernetes.io
      • security-discuss-private@kubernetes.io
      • distributors-announce@kubernetes.io
    • OWNERS_ALIASES
  • kubernetes/community PR: kubernetes/community#7385
    • sigs.yaml
    • communication/slack-config/usergroups.yaml
    • make generate
  • kubernetes/org PR: kubernetes/org#4321
    • config/kubernetes/org.yaml
  • kubernetes/enhancements PR: kubernetes/enhancements#4118
    • OWNERS_ALIASES
  • HackerOne project membership
  • OpsGenie rotation
    • Remove new user
  • Mailing lists
  • github.com/kubernetes-security membership
  • Slack
    • #SRC-private membership
    • #security-release-team membership
  • Calendar meetings
  • Google Docs access
cji commented

For mailing lists offboarding I only reduced to a "Member" on the public lists and didn't remove entirely.

cji commented

Opened #183 to also add Luke to the emeritus list

cji commented

Mirroring another PR Luke had made (but was closed) that's not in our checklist: kubernetes/enhancements#4118

cji commented

I need some help with the following to wrap this up:

  • Get kubernetes/enhancements#4118 approved/merged
  • H1 Offboarding (instructions are out of date) received an email that Luke was removed from the org
  • Removal from H1 meeting
  • Removal from Slack channels