Giters

kubernetes / committee-security-response

Kubernetes Security Process and Security Committee docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Offboard @sfowl

tallclair opened this issue · comments

commented

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

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

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

commented

Just waiting for:

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

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

commented

/remove-lifecycle rotten

commented

@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!

commented

#security-release-team has been updated