Skip to content
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

Closed
sam-github opened this issue Dec 13, 2016 · 7 comments
Closed

Formation of a Security Working Group #175

sam-github opened this issue Dec 13, 2016 · 7 comments

Comments

@sam-github
Copy link
Contributor

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

@williamkapke
Copy link
Contributor

@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 tsc-agenda label.

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

@mikeal
Copy link
Contributor

mikeal commented Dec 15, 2016

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:

  • The TSC would like a recommendation from the participants on how they would like it structured.
  • My recommendation, and I believe Rod's as well, is for this to be a Top Level Working Group, but ultimately we want to hear from the people doing the work how they would like to be organized.
  • In addition, I would recommend a WG over a TLP as a starting point and only migrate to a TLP once the WG needs the additional structure to manage the work.

@jasnell
Copy link
Member

jasnell commented Jan 12, 2017

This effort has been underway and is making progress.

@joshgav
Copy link
Contributor

joshgav commented Jan 20, 2017

Related: nodejs/security-wg#11

@jasnell
Copy link
Member

jasnell commented Apr 17, 2017

@sam-github ... can you provide an update on where things are at on this? Does this issue need to remain open?

@sam-github
Copy link
Contributor Author

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.

@jasnell
Copy link
Member

jasnell commented Apr 18, 2017

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.

@jasnell jasnell closed this as completed Apr 18, 2017
drifkin added a commit to nodejs/security-wg that referenced this issue Mar 14, 2018
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>.
drifkin added a commit to nodejs/security-wg that referenced this issue Mar 15, 2018
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>.
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
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>.
mattstern31 added a commit to mattstern31/security-wg-process that referenced this issue Nov 11, 2023
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>.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants