Onboard @ritazh as associate

[enj]

• [ ] kubernetes/security PR:
  • [x] README.md #158
• [ ] kubernetes/k8s.io PR: https://github.com/kubernetes/k8s.io/pull/3700
  • [x] groups/security-response-committee/groups.yaml
  • distributors-announce@kubernetes.io
• [ ] kubernetes/community PR:
  • [ ] sigs.yaml
  • [ ] communication/slack-config/usergroups.yaml
  • [ ] make generate
• [ ] kubernetes/org PR:
  • [ ] config/kubernetes/org.yaml
• [x] Verify Discuss account
• [x] github.com/kubernetes-security membership
• [ ] Slack
  • [x] Verify 2-factor auth
  • [ ] #SRC-private membership -> not sure about this?
  • [ ] #security-release-team membership -> not sure about this?
• [ ] Calendar meetings
• [ ] Google Docs access cc @ritazh

[ritazh]

Confirming I have 2FA setup for K8s slack. Thanks @enj!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale