Proposal: Add Security Contact role

Taken from the governance template
https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md
This commit is contained in:
Carolyn Van Slyck 2018-06-08 10:44:25 -05:00
parent 54c100c929
commit 1638bbd9e5
No known key found for this signature in database
GPG Key ID: 1C91EA2338067CBF
1 changed files with 6 additions and 0 deletions

View File

@ -34,6 +34,12 @@ The following, non-exhaustive, items are out of scope:
- A chair does not have more rights, or votes, than a maintainer.
- Responsible for reporting the SIGs status to the appropriate Kubernetes leadership teams.
- Security Contacts
- MUST be a contact point for the Product Security Team to reach out to for triaging and handling of incoming issues.
- MUST be a maintainer.
- MUST accept the Kubernetes [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy).
- Defined in [SECURITY_CONTACTS](https://github.com/kubernetes-incubator/service-catalog/blob/master/SECURITY_CONTACTS) file.
## Organizational management
- SIG meets every week on Zoom at 1 PM PST on Mondays