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

Update Charter / Readme.md #874

Merged
merged 2 commits into from
Jun 22, 2023
Merged

Update Charter / Readme.md #874

merged 2 commits into from
Jun 22, 2023

Conversation

darcyclarke
Copy link
Member

@darcyclarke darcyclarke commented Feb 2, 2023

  • remove reference to legacy nsp (Node Security Project) which was acquired by npm inc. (which was then acquired by GitHub)
  • remove "ecosystem" prefix for the WG as this has been promoted & is canonically known as Node.js's "Security WG"

Notably, this does remove an item from the "Charter" but that may be reasonable/within scope.

/cc @mhdawson

- remove reference to legacy nsp (Node Security Project) which was acquired by npm inc. (which was then acquired by GitHub)
- remove "ecosystem" prefix for the WG as this has been promoted & is canonically known as Node.js's "Security WG"
@darcyclarke darcyclarke changed the title Update Readme.md Update Charter / Readme.md Feb 2, 2023
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mhdawson
Copy link
Member

mhdawson commented Feb 3, 2023

Went to look at governance etc. related to changing. I think we should change here first:

https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md#ecosystem-security

@darcyclarke interested/have time to submit PR there or would you like me to do it?

Copy link
Member

@fraxken fraxken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@sheelpriy sheelpriy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@UlisesGascon
Copy link
Member

Went to look at governance etc. related to changing. I think we should change here first:

https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md#ecosystem-security

@darcyclarke interested/have time to submit PR there or would you like me to do it?

@mhdawson It was done in nodejs/TSC@07153d0

@@ -3,7 +3,8 @@
[![Security WG Twitter Hashtag](https://img.shields.io/badge/Twitter-%23SecurityWG-blue.svg)](https://twitter.com/search?q=SecurityWG)
[![OpenJS Slack Invite](https://img.shields.io/badge/join%20slack%20on-nodejs--security--wg-green.svg)](https://slack-invite.openjsf.org/)
[![OpenSSF scorecard](https://api.securityscorecards.dev/projects/github.com/nodejs/security-wg/badge)](https://api.securityscorecards.dev/projects/github.com/nodejs/security-wg)
# Ecosystem Security Working Group

# Security Working Group
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and similar places should now be updated to say team instead of working group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants