-
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
Formation of a Security Working Group #175
Comments
@sam-github I want to discuss nodejs/security-wg#11 (which relates to nodejs/security-wg#9) at the next TSC meeting so I've added the To me, it seems like the Board has handed us a new Top-Level Project... not a Working Group. If this is true, then a Technical Committee needs to be formed instead. To answer your question though- you can review: https://github.com/nodejs/TSC/blob/master/WORKING_GROUPS.md#starting-a-wg |
We just discussed this a bit in the CTC meeting. @sam-github if you like I'd love to chat I can fill you in a lot of the back story. A few updates:
|
This effort has been underway and is making progress. |
Related: nodejs/security-wg#11 |
@sam-github ... can you provide an update on where things are at on this? Does this issue need to remain open? |
There are a group of people meeting semi-regularly, but I don't think we are officially incorporated (?) as a Working Group, or if we have to be. @williamkapke or someone more familiar with the process might have better feedback. I think the people in the meeting are happy with the status, I don't know if the CTC/TSC/whoever is responsible wants it to be more official. |
The choice of whether it needs to be more official is largely up to what the security team is looking to accomplish. If you're able to get the stuff done that you feel you need to get done, without an official charter, then awesome, that just makes the job easier for everyone. If you feel a charter is necessary, then that is something you can work out amongst yourselves then open a PR with the Charter. You will need to decide if you want that to be chartered under the CTC or TSC -- which depends entirely on the scope of what you're looking to accomplish. For the time being, let's close this specific issue. If the security team wishes to charter, then a PR with the draft charter should be opened. |
The README currently mentions that we're seeking charter and points to <nodejs/TSC#175>, but that issue has been closed for some time. A newer, more urgent-sounding issue now up at <nodejs/TSC#486>.
The README currently mentions that we're seeking charter and points to <nodejs/TSC#175>, but that issue has been closed for some time. A newer, more urgent-sounding issue is now up at <nodejs/TSC#486>.
The README currently mentions that we're seeking charter and points to <nodejs/TSC#175>, but that issue has been closed for some time. A newer, more urgent-sounding issue is now up at <nodejs/TSC#486>.
The README currently mentions that we're seeking charter and points to <nodejs/TSC#175>, but that issue has been closed for some time. A newer, more urgent-sounding issue is now up at <nodejs/TSC#486>.
There was a meeting at the collab summit after NINA16 in Austin to discuss forming of a Security Working Group.
A number of people are interested, there seems to be work to do.
See nodejs/security-wg#9 for initial project boiler plate, and nodejs/security-wg#10 for the WIP PR for meeting minutes.
What is the process for forming this working group?
What is the process for naming it, as well? See discussion in nodejs/security-wg#9
The text was updated successfully, but these errors were encountered: