diff options
| author | Rich Trott <rtrott@gmail.com> | 2021-07-14 01:15:59 +0300 |
|---|---|---|
| committer | Michaël Zasso <targos@protonmail.com> | 2021-09-04 16:14:28 +0300 |
| commit | c3cfefc2d3158471a64a1d3b6a121cfbb0a6b52d (patch) | |
| tree | 5e010b5a0b41f337daec10ed89c56544dbf5d144 /onboarding.md | |
| parent | e9c46107d7ee775439b60655b9e7e137a60353fd (diff) | |
doc: standardize on not capitalizing _collaborator_
Sometimes we capitalize _collaborator_ and sometimes not. After
consulting the Microsoft Style Guide and The Chicago Manual of Style,
I've concluded it is best to not capitalize it. For consistency, apply
that to our various .md files.
Refs: https://docs.microsoft.com/en-us/style-guide/capitalization
PR-URL: https://github.com/nodejs/node/pull/39379
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Zijian Liu <lxxyxzj@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
Diffstat (limited to 'onboarding.md')
| -rw-r--r-- | onboarding.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/onboarding.md b/onboarding.md index 938d683ee50..1cab6132e30 100644 --- a/onboarding.md +++ b/onboarding.md @@ -1,6 +1,6 @@ # Onboarding -This document is an outline of the things we tell new Collaborators at their +This document is an outline of the things we tell new collaborators at their onboarding session. ## One week before the onboarding session @@ -18,7 +18,7 @@ onboarding session. ## 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). + [the collaborators team](https://github.com/orgs/nodejs/teams/collaborators). * Ask them if they want to join any subsystem teams. See [Who to CC in the issue tracker][who-to-cc]. @@ -46,7 +46,7 @@ onboarding session. * `git merge --ff-only upstream/master` (or `REMOTENAME/BRANCH`) * Make a new branch for each PR you submit. * Membership: Consider making your membership in the Node.js GitHub - organization public. This makes it easier to identify Collaborators. + organization public. This makes it easier to identify collaborators. Instructions on how to do that are available at [Publicizing or hiding organization membership][]. @@ -101,11 +101,11 @@ The project has two venues for real-time discussion: * Some are WGs with some process around adding people, others are only there for notifications -* When a discussion gets heated, you can request that other Collaborators keep +* When a discussion gets heated, you can request that other collaborators keep an eye on it by opening an issue at the private [nodejs/moderation](https://github.com/nodejs/moderation) repository. * This is a repository to which all members of the `nodejs` GitHub - organization (not just Collaborators on Node.js core) have access. Its + organization (not just collaborators on Node.js core) have access. Its contents should not be shared externally. * You can find the full moderation policy [here](https://github.com/nodejs/admin/blob/HEAD/Moderation-Policy.md). @@ -224,7 +224,7 @@ needs to be pointed out separately during the onboarding. * Don't worry about making mistakes: everybody makes them, there's a lot to internalize and that takes time (and we recognize that!) * Almost any mistake you could make can be fixed or reverted. -* The existing Collaborators trust you and are grateful for your help! +* The existing collaborators trust you and are grateful for your help! * Other repositories: * [https://github.com/nodejs/TSC](https://github.com/nodejs/TSC) * [https://github.com/nodejs/build](https://github.com/nodejs/build) |