-
-
Notifications
You must be signed in to change notification settings - Fork 129
Join the Node.js Security Working Group #3
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
+1 ... Add me to the list
…On Tue, Nov 29, 2016 at 9:31 AM Rod Vagg ***@***.***> wrote:
Add your name here or tag people that you think might be interested in
joining a public working group focused on Node.js core and ecosystem
security matters.
At Node.js Interactive today, @evilpacket <https://github.com/evilpacket>
announced that the @nodesecurity <https://github.com/nodesecurity>
project will be moving in to the Node.js Foundation. This Working Group
should be able to inform how that integration will happen and may end up
maintaining that project. The evolution of this group and its relationship
with the @nodesecurity <https://github.com/nodesecurity> project is not
defined and will be up to those involved to guide.
See #1 <#1> for a proposed
purpose and scope of work for this group.
See #2 <#2> for the proposed
relationship between activities here and the private management of security
vulnerability reporting, patching and releasing of Node.js core.
/cc @nodejs/security <https://github.com/orgs/nodejs/teams/security>
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#3>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAa2eQuQmlOamR99Jn6APU-y6icL4WD0ks5rDEVAgaJpZM4K_G3F>
.
|
+1 add me. |
I'd like to be involved if possible :) |
+1 add me |
o/ +! |
me plz! |
+1 for myself of @mlfbrown |
Hey, it's me. I'm interested if this covers infra/ci. |
I'm interested for representing some of the ecosystem. |
+1, count me in =). |
+1 for me. |
Please add me to the list.
… On Nov 29, 2016, at 9:31 AM, Rod Vagg ***@***.***> wrote:
Add your name here or tag people that you think might be interested in joining a public working group focused on Node.js core and ecosystem security matters.
At Node.js Interactive today, @evilpacket <https://github.com/evilpacket> announced that the @nodesecurity <https://github.com/nodesecurity> project will be moving in to the Node.js Foundation. This Working Group should be able to inform how that integration will happen and may end up maintaining that project. The evolution of this group and its relationship with the @nodesecurity <https://github.com/nodesecurity> project is not defined and will be up to those involved to guide.
See #1 <#1> for a proposed purpose and scope of work for this group.
See #2 <#2> for the proposed relationship between activities here and the private management of security vulnerability reporting, patching and releasing of Node.js core.
/cc @nodejs/security <https://github.com/orgs/nodejs/teams/security>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHEOfar0OcWRuus3TGJFSg8yACFoFCTks5rDEVAgaJpZM4K_G3F>.
|
+1 |
Please add me. /cc @jasongin @digitalinfinity (please indicate if you'd like to join). /cc @williamkapke to help us follow best practices for setting this up. |
+1 |
1 similar comment
+1 |
+1 for me |
Please add me. |
I'd like to join |
+1 |
+1 I actually work full time on Node.js security related stuff |
Closing this now, follow @sam-github's instructions here to request to join. |
Add your name here or tag people that you think might be interested in joining a public working group focused on Node.js core and ecosystem security matters.
At Node.js Interactive today, @evilpacket announced that the @nodesecurity project will be moving in to the Node.js Foundation. This Working Group should be able to inform how that integration will happen and may end up maintaining that project. The evolution of this group and its relationship with the @nodesecurity project is not defined and will be up to those involved to guide.
See #1 for a proposed purpose and scope of work for this group.
See #2 for the proposed relationship between activities here and the private management of security vulnerability reporting, patching and releasing of Node.js core.
/cc @nodejs/security
The text was updated successfully, but these errors were encountered: