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.

Sign up for GitHub

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

Jump to bottom

Time to charter the security working group #486

Closed
mhdawson opened this issue Feb 5, 2018 · 14 comments
Closed

Time to charter the security working group #486

mhdawson opened this issue Feb 5, 2018 · 14 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 5, 2018

The security working group has been up and running for quite some time now. I'm wondering if people think it might be time to formally charter it ?
@mcollina
Copy link
Member

mcollina commented Feb 6, 2018

I am 👍 to chartering with the responsibilities defined in the README.

@jasnell
Copy link
Member

jasnell commented Feb 17, 2018

+1 to chartering.

@Trott
Copy link
Member

Trott commented Feb 17, 2018

This hasn't happened yet? Oh, yes, let's do it if they have all the necessary docs in order.

@mhdawson
Copy link
Member Author

I'll add it to my list of TODOs to get the docs in order and get it chartered

@evanlucas
Copy link
Contributor

+1 to chartering

1 similar comment
@mcollina
Copy link
Member

+1 to chartering

@joyeecheung
Copy link
Member

SGTM

drifkin added a commit to nodejs/security-wg that referenced this issue Mar 14, 2018
@drifkin
Update link to TSC charter issue
3dbd27e 
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 drifkin mentioned this issue Mar 14, 2018
Merged
drifkin added a commit to nodejs/security-wg that referenced this issue Mar 15, 2018
@drifkin
Update link to TSC charter issue (#161)
dc89351 
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>.
@ChALkeR
Copy link
Member

ChALkeR commented Mar 23, 2018 •
edited
Loading

👍

@mhdawson What should the next steps be?

@mhdawson
Copy link
Member Author

We just need to write the charter with the scope etc. Its on my list I've just been travelling but have not quite gotten to it.

@Trott
Copy link
Member

Trott commented Mar 23, 2018

We just need to write the charter with the scope etc. Its on my list I've just been travelling but have not quite gotten to it.

I could be wrong, but it seems like a draft charter could probably be written in less than 30 minutes if someone else on the WG wants to take it off your hands.

@mhdawson
Copy link
Member Author

+1 if somebody has the time I'd be happy if that happened.

@mhdawson
Copy link
Member Author

mhdawson commented May 9, 2018

Still on my todo list, sorry for not getting to it yet.

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

PR has been submitted here: #548

@mhdawson
Copy link
Member Author

PR landed. closing.

@ChALkeR ChALkeR mentioned this issue Aug 4, 2018
Closed
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
@patrickm68
Update link to TSC charter issue (#161)
58f9a64 
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
@mattstern31
Update link to TSC charter issue (#161)
e88355c 
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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@mcollina @ChALkeR @jasnell @evanlucas @Trott @joyeecheung @mhdawson