-
-
Notifications
You must be signed in to change notification settings - Fork 129
Name this Working Group #4
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
Comments
Thinking and thinking, Security seems the most concise and descriptive title for what this WG proposes to do. Other suggestions that come to mind include:
So I think we should call this group Security as proposed, and rename the private group as Disclosures or Vulnerabilities.
We could have a big (blinking!) banner on the README and in the issue and PR templates redirecting people to the Disclosures email for actual vulnerability reports. Seems that would be sufficient diligence. |
+1 to The private group is only used for reporting vulnerabilities right? So that name really makes more sense. (IMHO). |
At NINA, there was positive opinion towards the existing one being called the My opinion is that the new group should be called the |
I like the names proposed in #4 (comment), with the caveat that we most emphatically do not oversee the Node Security Project, that is an existing project, not ours, we shouldn't steal its name, and the name wasn't given to use. The group will oversee a Node Foundation Vulnerabilty Database (EDIT: actual name is still TBD) (seeded with a donation from |
Any other thoughts, @nodejs/security-wg ? |
👍 to |
I don't think there is any appetite to rename this from "Security WG", though perhaps if the security response team at-nodejs/security gets reorganized the issue will come up again. Shall we close for now if there isn't something actionable? |
As raised by @Trott in #2 (comment), "Node.js Security Working Group" might not be the best name as it may lure people to think that they should report issues via the issue tracker here.
So, one of the first jobs of the group forming here is to decide on the name, both the full name and the repository name.
The text was updated successfully, but these errors were encountered: