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: add offboarding doc #21103

Closed
wants to merge 1 commit into from
Closed

doc: add offboarding doc #21103

wants to merge 1 commit into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Jun 2, 2018

Add minimal document for what to do when a Collaborator moves to
Collaborator Emeritus or leaves the project.

Checklist

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Jun 2, 2018
@Trott
Copy link
Member Author

Trott commented Jun 2, 2018

* 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.
Copy link
Member

Choose a reason for hiding this comment

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

shoudl->should

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed, thanks!

@richardlau
Copy link
Member

Also commit message:
theproject->the project

@Trott
Copy link
Member Author

Trott commented Jun 3, 2018

Fixed commit message. Thanks!

@Trott
Copy link
Member Author

Trott commented Jun 3, 2018

@vsemozhetbyt vsemozhetbyt added the meta Issues and PRs related to the general management of the project. label Jun 3, 2018
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
Copy link
Contributor

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?

@vsemozhetbyt vsemozhetbyt added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jun 3, 2018
Add minimal document for what to do when a Collaborator moves to
Collaborator Emeritus or leaves the project.
@Trott
Copy link
Member Author

Trott commented Jun 3, 2018

@lance
Copy link
Member

lance commented Jun 4, 2018

A third lite CI, this time successful: https://ci.nodejs.org/job/node-test-pull-request-lite/805/

@Trott
Copy link
Member Author

Trott commented Jun 5, 2018

Landed in fc3fd60

@Trott Trott closed this Jun 5, 2018
Trott added a commit to Trott/io.js that referenced this pull request Jun 5, 2018
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>
MylesBorins pushed a commit that referenced this pull request Jun 6, 2018
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>
@MylesBorins MylesBorins mentioned this pull request Jun 6, 2018
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. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants