-
Notifications
You must be signed in to change notification settings - Fork 70
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
Adding members to Security Response Team #232
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Varun Lodaya <varunml@amazon.com>
@dblock @peternied can you'll review this? |
GH issue - #219 |
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.
LGTM, I made some nits if you want to iterate more.
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.
Thanks @varun-lodaya for the update - thanks also to the new community members that are actively engaged in the security response process for the project.
I like @dblock suggestions and would recommend you take them.
Co-authored-by: Daniel (dB.) Doubrovkine <dblock@dblock.org> Signed-off-by: Varun Lodaya <varunml@amazon.com>
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.
Addressing nitpic comments from dbock@
Description
This change creates a new Security Response Team and adds core security maintainers to it
Issues Resolved
N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.