summaryrefslogtreecommitdiff
path: root/committee-security-response
AgeCommit message (Collapse)Author
2022-08-08Update enj companyMonis Khan
2022-03-04Fix tallclair affiliationTim Allclair
s/Apple/Google/
2022-02-01Onboard/offboard Mo/Swamy to SRCTim Allclair
2021-12-01steering: Add Committee liaisonsStephen Augustus
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>
2021-10-13Merge pull request #5868 from lukehinds/rem-pscKubernetes Prow Robot
Remove committee-product-security
2021-09-24Replace k/security with k/committee-security-response in ↵Pushkar Joglekar
k/community/sig-security (#6008) * Replace k/security with k/committee-security-response Minor updates from PSC to SRC * Updated references from master to main branch
2021-07-01Remove committee/product-securityLuke Hinds
As per PR #5597, the PSC is being renamed to SRC (security response commitee). This removes the former directory and files for the PSC naming convention Signed-off-by: Luke Hinds <lhinds@redhat.com>
2021-06-20Psc rename (#5597)Luke Hinds
* 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>