-
Notifications
You must be signed in to change notification settings - Fork 133
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
Update Security Working Group #1348
Conversation
If I'm not mistaken, the name and the responsibilities come from the working group's charter and can only be changed by the TSC. However, consensus should be sufficient for such a change. @nodejs/tsc |
When this working group was initially chartered, it was proposed to name it "Security working group" but people (including me) were concerned that they would start receiving vulnerability reports about Node.js from well-meaning researchers and other community members. Is that still a concern of TSC members? |
I'm putting this on the TSC agenda to maximize TSC input. Consensus should be enough for this--it shouldn't require a vote unless there are one or more TSC members opposed (and one or more in favor). |
5ad80f9
to
f37ae3d
Compare
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
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
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
Hello 👋
Updating the
WORKING_GROUPS.md
file following recommandation of @mhdawson in the following issue: nodejs/security-wg#874I've made the same changes: