-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
doc: add security steward on/offboarding steps #41129
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
Changes from 3 commits
ef6e95e
19c9fb5
8813bd8
174df2a
76f43d9
d4700fb
f6d0bc2
a70b390
5411024
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| # Security Steward Onboarding/OffBoarding | ||
|
|
||
| ## Onboarding | ||
|
|
||
| * Confirm the new steward agrees to keep all private information confidential | ||
| to the project and not to use/disclose to their employer. | ||
| * Add them to the security-stewards team in the GitHub nodejs-private | ||
| organization | ||
| * Add them to the standard team in H1 using this | ||
| [page](https://hackerone.com/nodejs/team_members); | ||
|
mhdawson marked this conversation as resolved.
Outdated
|
||
| * Add them to the | ||
| [jenkin-admins team](https://GitHub.com/orgs/nodejs/teams/jenkins-admins) | ||
| in the GitHub nodejs org. This is needed for them to be able | ||
| to lock/unlock the CI during a security release. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't object to this, but this is a change -- currently locking/unlocking the CI for a security release is documented as being something to request the build team to do (see the template issue text for "Notify build-wg of upcoming security release date by opening an issue in nodejs/build to request WG members are available to fix any CI issues." in https://github.com/nodejs/node/blob/master/doc/guides/security-release-process.md).
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok that makes sense to me. I'll remove that part for now.
mhdawson marked this conversation as resolved.
Outdated
|
||
| * Add them as managers of the | ||
| [nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list. | ||
|
|
||
| ## Offboarding | ||
|
|
||
| * Remove them from security-stewards team in the GitHub nodejs-private | ||
| organization | ||
|
mhdawson marked this conversation as resolved.
Outdated
|
||
| * Unless they have access for another reason, remove them from the | ||
| standard team in H1 using this | ||
| [page](https://hackerone.com/nodejs/team_members). | ||
| * Unless they are a Jenkins admin for another reason, remove them from the | ||
| [jenkin-admins team](https://GitHub.com/orgs/nodejs/teams/jenkins-admins) | ||
| in the GitHub nodejs org. | ||
|
mhdawson marked this conversation as resolved.
Outdated
|
||
| * Downgrade their account to regular member in the | ||
| [nodejs-sec](https://groups.google.com/g/nodejs-sec/members) mailing list. | ||
Uh oh!
There was an error while loading. Please reload this page.