-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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: add offboarding doc #21103
doc: add offboarding doc #21103
Conversation
doc/offboarding.md
Outdated
* Email the TSC mailing list to notify TSC members that the Collaborator is | ||
moving to Collaborator Emeritus. | ||
* Determine what GitHub teams the Collaborator belongs to. In consultation with | ||
the Collaborator, determine which of those teams they shoudl be removed from. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shoudl
->should
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, thanks!
Also commit message: |
Fixed commit message. Thanks! |
doc/offboarding.md
Outdated
moving to Collaborator Emeritus. | ||
* Determine what GitHub teams the Collaborator belongs to. In consultation with | ||
the Collaborator, determine which of those teams they should be removed from. | ||
* Some teams may also require a pull request to remove them from a team |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, but is them
a bit confusing here? Maybe a Collaborator
or someone
etc?
Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project.
A third lite CI, this time successful: https://ci.nodejs.org/job/node-test-pull-request-lite/805/ |
Landed in fc3fd60 |
Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project. PR-URL: nodejs#21103 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Lance Ball <lball@redhat.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project. PR-URL: #21103 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Lance Ball <lball@redhat.com> Reviewed-By: Matheus Marchini <matheus@sthima.com>
Add minimal document for what to do when a Collaborator moves to
Collaborator Emeritus or leaves the project.
Checklist