nodejs / inclusivity

Improving inclusivity in the node community
80 stars 22 forks source link

Create checklists for onboarding and offboarding members #109

Closed nebrius closed 8 years ago

nebrius commented 8 years ago

Purpose

Now that we're starting to admit new members (sorry for the huge delays everyone!), we should formalize everything that needs to be done to onboard them properly. There are a number of details that need to be covered, and it's proven easy to forget some of the steps.

Proposal

The onboarding and offboarding lists need to include :

I feel like I may be forgetting one or two more items, so if you know of any, let me know!

Focus

This issue is focused purely on codifying the list of actions that need to be taken when onboarding and offboarding members. This means that we want to focus on documenting the existing process only.

Some off topic examples include:

As always, if you would like to discuss these issues, please open a new issue that follows our issue policy.

scottgonzalez commented 8 years ago

I've created a template that we can use to create issues. Every time a new member is accepted, we can create an issue from this template and then work through the list. If this seems good, I can create a PR from this and then we can wait a few days for any other items that we might need to add.

Template for adding a WG member

Template for removing a WG member

I guessed at the URL for editing the GitHub team. Can someone with access verify that this is correct?

nebrius commented 8 years ago

hmm, I would have thought you'd have access? Both URLs worked for me

nebrius commented 8 years ago

I think this looks good to PR

scottgonzalez commented 8 years ago

hmm, I would have thought you'd have access?

Oh, look at that; I do have access. I guess that makes sense so you can leave a group on your own. I always assumed you needed to be an admin to get to the teams. I think I just made a bad assumption based on getting access to a single repo's collaborator list, since you need to be an admin to get to the repo settings.