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

doc: sync security policy with nodejs.org #29682

Closed
wants to merge 2 commits into from

Conversation

sam-github
Copy link
Contributor

The Node.js security disclosure policy has diverged between the website
and github:

The website is more recent and accurate, so sync the content from:

The Node.js security disclosure policy has diverged between the website
and github:
- https://nodejs.org/en/security/
- https://github.com/nodejs/node/security/policy

The website is more recent and accurate, so sync the content from:
- https://github.com/nodejs/nodejs.org/blob/master/locale/en/security.md
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Sep 23, 2019
@sam-github
Copy link
Contributor Author

/to @nodejs/tsc @nodejs/security-wg PTAL

SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
@sam-github
Copy link
Contributor Author

@Trott OK, I caved to linter pressure and reformatted the markdown. :-)

sam-github added a commit to nodejs/nodejs.org that referenced this pull request Sep 26, 2019
It doesn't matter here, but to keep this file textually identical to the
policy in Node.js, the markdown needs to lint clean.

See: nodejs/node#29682
@sam-github
Copy link
Contributor Author

@nodejs/tsc Actually, a meta-question, can we remove the content of this file and replace it with a link to https://nodejs.org/en/security/? That would mean it no longer needs to be kept in sync. I'm not sure actual content needs to be here, its not machine readable, for example, so just a URL might be sufficient.

Thoughts?

@jasnell
Copy link
Member

jasnell commented Sep 26, 2019

I'm good either way @sam-github ... but given GitHub has started to handle these files more directly it's likely better to keep this to avoid the user from having to deal with another layer of indirection.

Trott pushed a commit to nodejs/nodejs.org that referenced this pull request Sep 27, 2019
* Wrap security so it respects Node.js linter

It doesn't matter here, but to keep this file textually identical to the
policy in Node.js, the markdown needs to lint clean.

See: nodejs/node#29682

* Update locale/en/security.md

Co-Authored-By: Richard Lau <riclau@uk.ibm.com>

* Update locale/en/security.md

Co-Authored-By: Richard Lau <riclau@uk.ibm.com>
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

@Trott
Copy link
Member

Trott commented Sep 27, 2019

@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Sep 27, 2019
@Trott
Copy link
Member

Trott commented Sep 28, 2019

Landed in dd74b16

@Trott Trott closed this Sep 28, 2019
Trott pushed a commit to Trott/io.js that referenced this pull request Sep 28, 2019
The Node.js security disclosure policy has diverged between the website
and github:
- https://nodejs.org/en/security/
- https://github.com/nodejs/node/security/policy

The website is more recent and accurate, so sync the content from:
- https://github.com/nodejs/nodejs.org/blob/master/locale/en/security.md

PR-URL: nodejs#29682
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
targos pushed a commit that referenced this pull request Oct 1, 2019
The Node.js security disclosure policy has diverged between the website
and github:
- https://nodejs.org/en/security/
- https://github.com/nodejs/node/security/policy

The website is more recent and accurate, so sync the content from:
- https://github.com/nodejs/nodejs.org/blob/master/locale/en/security.md

PR-URL: #29682
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@sam-github sam-github deleted the sync-sec-report-policy branch November 28, 2019 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants