Onboard @PushkarJ as associate

[Mo Khan]

• kubernetes/security PR:
  • README.md #158
• kubernetes/k8s.io PR: kubernetes/k8s.io#3700 kubernetes/k8s.io#3703
  • groups/security-response-committee/groups.yaml
    • [e-mail]
• kubernetes/community PR:
  • sigs.yaml
  • communication/slack-config/usergroups.yaml
  • make generate
• kubernetes/org PR:
  • config/kubernetes/org.yaml
• Verify Discuss account
• github.com/kubernetes-security membership
• Slack
  • 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 @PushkarJ

[Pushkar Joglekar]

Thanks for doing this @enj . I just setup 2FA for K8s slack

[Pushkar Joglekar]

@enj Is this ready to be closed? I am assuming the slack channels are not for associates. Rest of it seems to be completed!

[Mo Khan]

@PushkarJ I still need to sync with CJ to make sure I covered everything.

[Kubernetes 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