diff options
| author | Luke Hinds <7058938+lukehinds@users.noreply.github.com> | 2021-06-20 18:04:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-20 10:04:51 -0700 |
| commit | ef108be474a4e7154511515b4a1316ec9bda7177 (patch) | |
| tree | 5562bfc3e19f804cf26cae6bb5fa66ec50b22f11 /sigs.yaml | |
| parent | e6c864a1647e1ac395897918b9f8861a45a83083 (diff) | |
Psc rename (#5597)
* Rename of Product Security Committee
After some discussions, we decided to put it to the steering
committee that a rename may be prudent, as 'Product' can be
confusing (suggests downstream).
The recommendation is Security Response Committee
Ref: #5596
Signed-off-by: Luke Hinds <lhinds@redhat.com>
* Generate docs
Signed-off-by: Luke Hinds <lhinds@redhat.com>
* Fix spelling mistake
Signed-off-by: Luke Hinds <lhinds@redhat.com>
Diffstat (limited to 'sigs.yaml')
| -rw-r--r-- | sigs.yaml | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -3161,13 +3161,13 @@ committees: teams: - name: code-of-conduct-committee description: General Discussion -- dir: committee-product-security - name: Product Security +- dir: committee-security-response + name: Security Response mission_statement: > - The Kubernetes Product Security Committee is the body that is responsible for - receiving and responding to reports of security issues in Kubernetes products. + The Kubernetes Security Response Committee is the body that is responsible for + receiving and responding to reports of security issues in Kubernetes projects. - label: product-security + label: security-response leadership: chairs: - github: cjcullen @@ -3195,11 +3195,11 @@ committees: contact: private_mailing_list: security@kubernetes.io teams: - - name: product-security-committee + - name: security-response-committee description: General Discussion subprojects: - name: security - description: Policies and documentation for the Product Security Committee + description: Policies and documentation for the Security Response Committee owners: - https://raw.githubusercontent.com/kubernetes/security/master/OWNERS - dir: committee-steering |