-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Psc rename #5597
Psc rename #5597
Conversation
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>
Signed-off-by: Luke Hinds <lhinds@redhat.com>
cc @kubernetes/product-security-committee |
+1 from me (with steering hat on) cc @kubernetes/sig-security @kubernetes/sig-auth-misc |
@lukehinds needs spelling fix to make pull-community-verify green + would need to remove the |
+1 from me (steering hat on) cc @kubernetes/steering-committee |
Signed-off-by: Luke Hinds <lhinds@redhat.com>
/test pull-community-verify |
@lukehinds needs a run of |
+1 |
lgtm |
How do I do that is that a prow command? |
It's not possible via a prow command, you'll need to run |
Signed-off-by: Luke Hinds <lhinds@redhat.com>
lgtm I'm a little worried about this causing some confusion in the short term, but I think longer term this name does a much better job of conveying our responsibilities. How will we abbreviate this? SRC is maybe too common an abbreviation for "source". We could through "Kubernetes" in there to get "KSRC" or just "KSR". But maybe we really just need to avoid the abbreviation jargon... |
/committee product-security |
Signed-off-by: Luke Hinds <lhinds@redhat.com>
@nikhita this should be in order now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/hold
for more reviews
/approve |
/lgtm I think this will make it easier for folks outside the community to find us when they need us |
/lgtm /hold cancel |
* 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: kubernetes#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>
Related: - Part of: kubernetes/community#5597 - Supercedes: kubernetes#2596
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, lukehinds, nikhita, vagobon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
Which issue(s) this PR fixes:
Ref: #5596