kubernetes/committee-security-response

Onboard @cji

joelsmith opened this issue · 5 comments

  • kubernetes/security PR: #176
    • README.md
    • OWNERS_ALIASES
    • SECURITY_CONTACTS
  • kubernetes/k8s.io PR: kubernetes/k8s.io#5212
    • 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#7282
    • sigs.yaml
    • communication/slack-config/usergroups.yaml
      • Verify slack 2-factor auth
    • make generate
  • kubernetes/org PR: kubernetes/org#4195
    • config/kubernetes/org.yaml
  • HackerOne project membership
    • Verify 2-factor auth
  • OpsGenie rotation
    • Add new user
    • Update rotation
  • Mailing lists
  • Verify Discuss account
  • github.com/kubernetes-security membership
  • Slack
    • Verify 2-factor auth
    • #SRC-private membership
    • #security-release-team membership
  • Calendar meetings
  • Google Docs access
cji commented

@joelsmith

thank you!

cji commented

@joelsmith I noticed this is open with an unchecked item to add me to meetings. I see the SRC monthly on my calendar. Is this good to close now?

@cji do you have a meeting with H1 on your calendar on Thursday, July 13th? If you have that, then I think we can close it.

cji commented

I confirmed I have the meeting on my calendar - thanks!