a4dea68e7d
Proposing Steering Committee liaisons for the following groups: - Code of Conduct Committee (Tim) - Security Response Committee (Stephen) Choosing Tim and Stephen here, because: - they're newly-appointed SC members with a lighter liaison load - they have served on (or [have] operate[d] in) the respective committee's private spaces and are familiar with their processes Signed-off-by: Stephen Augustus <foo@auggie.dev> |
||
|---|---|---|
| .. | ||
| OWNERS | ||
| README.md | ||
README.md
Security Response Committee
The Kubernetes Security Response Committee is the body that is responsible for receiving and responding to reports of security issues in Kubernetes projects.
Members
- CJ Cullen (@cjcullen), Google
- Joel Smith (@joelsmith), Red Hat
- Luke Hinds (@lukehinds), Red Hat
- Micah Hausler (@micahhausler), Amazon
- Swamy Shivaganga Nagaraju (@swamymsft), Microsoft
- Tabitha Sable (@tabbysable), Datadog
- Tim Allclair (@tallclair), Apple
Contact
- Private Mailing List: security@kubernetes.io
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/security-response-committee - General Discussion
- Steering Committee Liaison: Stephen Augustus (@justaugustus)
Subprojects
The following subprojects are owned by the Security Response Committee:
committee-security-response
Policies and documentation for the Security Response Committee