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: update 2fa information in onboarding.md #18968

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions doc/onboarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,20 +5,17 @@ onboarding session.

## One week before the onboarding session

* Confirm that the new Collaborator is using two-factor authentication on their
GitHub account. Unless two-factor authentication is enabled, do not give an
account elevated privileges such as the ability to land code in the main
repository or to start continuous integration (CI) jobs.
* If the new Collaborator is not yet a member of the nodejs GitHub organization,
Copy link
Contributor

Choose a reason for hiding this comment

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

A nit: nodejs -> Node.js?

Copy link
Member

Choose a reason for hiding this comment

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

Or [@nodejs](https://github.com/nodejs): @nodejs
To correspond to @nodejs (which isn't available in *.md files).

confirm that they are using two-factor authentication. It will not be possible
to add them to the organization if they are not using two-factor
authentication.
* Announce the accepted nomination in a TSC meeting and in the TSC
mailing list.

## Fifteen minutes before the onboarding session

* Prior to the onboarding session, add the new Collaborator to
[the Collaborators team](https://github.com/orgs/nodejs/teams/collaborators).
Note that this is the step that gives the account elevated privileges, so do
not perform this step (or any subsequent steps) unless two-factor
authentication is enabled on the new Collaborator's GitHub account.

## Onboarding session

Expand Down