-
Notifications
You must be signed in to change notification settings - Fork 134
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
decharter Ecosystem Security Working Group #1351
Conversation
Feel free to close this if the situation has changed or there otherwise is not consensus that this is the right thing to do. (I expect @RafaelGSS in particular to have a strong "yes" or "no" opinion on this.) Let's close #1081 once whatever decision we arrive at is made. |
@nodejs/tsc @nodejs/security-wg |
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.
It seems there are a fair bit of drive-by fixes above the deleted lines?
Yes. I can remove them and put them in a separate PR if that's preferable. |
I think so. By their charter the security working group is responsible for keeping the node cves up-to-date. However, this is now done by the security steward. |
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
It seems that the working group can function as a GitHub team. Closes: #1081
It seems that the working group can function as a GitHub team.
Closes: #1081