Offboard @sfowl

[tallclair]

@sfowl stepped down from the associate role, but it looks like we never went through the full offboarding process.

• [x] kubernetes/security PR: https://github.com/kubernetes/committee-security-response/pull/173
  • [x] README.md
  • [x] OWNERS_ALIASES
• [x] kubernetes/k8s.io PR: https://github.com/kubernetes/k8s.io/pull/4816
  • [x] groups/security-response-committee/groups.yaml
  • security@kubernetes.io
  • security-discuss-private@kubernetes.io
  • distributors-announce@kubernetes.io
  • [x] OWNERS_ALIASES
• [x] kubernetes/community PR: N/A for associates
  • [x] sigs.yaml
  • [x] communication/slack-config/usergroups.yaml
  • [x] make generate
• [x] kubernetes/org PR: N/A for associates
  • [x] config/kubernetes/org.yaml
• [x] HackerOne project membership
• [x] OpsGenie rotation
  • [x] Remove user
• [x] Mailing lists
  • [x] Security Discuss - owner
  • [x] Security Announce - owner
  • [x] Kubernetes Announce - manager
  • [ ] Kubernetes Dev - member
• [x] github.com/kubernetes-security membership
• [x] Slack
  • [x] #SRC-private membership
  • [x] #security-release-team membership
• [x] Calendar meetings
• [x] Google Docs access

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[joelsmith]

Just waiting for:

• H1 to remove Sam from the quarterly calendar invite
• @sfowl to leave the k8s slack channel #security-release-team

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[joelsmith]

/remove-lifecycle rotten

[joelsmith]

@sfowl I think the last thing that needs to do is for you to depart the channel #security-release-team. Once that is complete, please let me know and I will close this issue. Thanks for all your efforts as part of the SRC!

[cji]

security-release-team has been updated