Onboard & Offboard: Junior Developers

### Overview
We need to have a checklist of items to do when a new developer onboards and offboards so that the process can be consistent and fast.

### Action Items
Each time you do an onboarding or offboarding session:
- [ ] Copy the relevant template (either onboard or offboard) into a new comment below.
- [ ] Depending on the template you are using, do one of the following:
- [ ] For the onboarding template, where it says, `[INSERT NAME OF EVERY PERSON BEING ONBOARDED HERE]`, replace it with the names of every person being onboarded at the same time. For example, if I was onboarding 3 people at the same time, I would list all 3 people's names. If I was only onboarding 1 person, then I would just list 1 person's name.
- [ ] For the offboarding template, where it says, `[INSERT NAME OF EVERY PERSON BEING OFFBOARDED HERE]`, replace it with the names of every person being offboarded at the same time. For example, if I was offboarding 5 people at the same time, I would list all 5 people's names. If I was only onboarding 1 person, then I would just list 1 person's name.
- [ ] Click the "Comment" button
- [ ] Check off each Action Item as you complete the onboarding with them.

### Onboard template
```
#### Onboard [INSERT NAME OF EVERY PERSON BEING ONBOARDED HERE]

#### Preparation (while devs are completing the main HfLA onboarding and sorting)
- [ ] Have the link to the HfLA website dev onboarding slides ready and check that the `Hfla website dev onboarding form` has been enabled
- [ ] On Slide 3 of the deck, click through to the Accountability Buddy Sheet and make sure it is ready for devs to use to pair up.

#### In the `dev onboarding` room
- [ ] Person leading onboarding: please introduce yourself
- [ ] When devs come in, be sure they have the link to the `HfLA website dev onboarding` slide deck. You may have to paste the link in the chat frequently, because devs just joining the room will not see earlier chat messages
- [ ] Explain as needed. Make notes of FAQ so we can incorporate into the slides
- [ ] Zoom registration links for weekly meetings
- [ ] Encourage devs to register for every meeting series even if there is only a small chance that they could attend. Emphasize that there is no obligation to attend but that if they don't register, they won't have a calendar invite.
- [ ] Team roster entry - if there is time, check this was done correctly
- [ ] Pre-work Checklists - open Issues tab so you can view progress on the Pre-work Checklists
- [ ] Mention that "missing" labels (such as `role: missing`) should be removed
- [ ] Demonstrate how to find one's Pre-work Checklist

#### Post Meeting
- [ ] Check each Pre-work Checklist
- [ ] Hover over assigned dev name to check for public membership in Hack for LA organization.
- [ ] Check that the member has an entry in the roster
- [ ] Check labels and Project Board
- [ ] Add Milestone `08. Team Workflow` and move to the `In Progress` column
```

### Offboard template
Note: If a developer is inactive for more than two months, the "Schedule Monthly" workflow will automatically: a.) remove a developer from the website's Google Drive, b.) remove a developer's 'website-write' team access, and c.) close or flag any of the developer's open issues.
The below template assumes that you are off-boarding a developer manually because either:
a) the developer has let you know directly that they are leaving the team or
b) the developer has been `2 weeks inactive` and you have already reached out to them via Slack, email, and in a comment in their issue, which resulted in either them not responding to your messages or they have indicated they are no longer interested in being part of this team. (The `2 weeks inactive` check is usually done as part of the Dev/PM agenda (#2607).)
```
#### Offboard [INSERT NAME OF EVERY PERSON BEING OFFBOARDED HERE]
Only if needed- see note about "Schedule Monthly" workflow:
- [ ] (Only if needed) Remove developer from our [HackforLA.org website Google Drive](https://drive.google.com/drive/folders/0AKWbU6_2dvZuUk9PVA).
- [ ] (Only if needed) Confirm developer is on the ['website'](https://github.com/orgs/hackforla/teams/website) team, then
- [ ] (Only if needed) Remove developer from the ['website-write'] (https://github.com/orgs/hackforla/teams/website-write/members) team.
- [ ] (Only if needed) Go to https://github.com/hackforla/website/issues and filter by "Assignee" to check if the person has any open issues.
- [ ] Close the developer's "Skills Issue" if open,
- [ ] For any other open issue,
- [ ] if possible have the person/assignee follow the steps in [2.6 What to do when you need to stop mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue) otherwise
- [ ] otherwise, you will need to do the steps in [2.6.b What to do if you have to stop working mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26b-what-to-do-if-you-have-to-stop-working-mid-issue) for them.
- [ ] Note: For "Add a note in the comments with details and progress for the next developer" bullet point, you may or may not have a note to add depending on your familiarity with the issue.
Note that these steps will need to be done manually:
- [ ] Remove them from our meetings:
- [ ] Sun 10AM-12PM (PST) : HFLA Website Team Meeting
- [ ] Tue 7-8PM (PST) : [HFLA developer meeting](https://calendar.google.com/calendar/u/0/r/eventedit/NGZlNzFqN25vdXRkMmY0NHF0YWw5ZDJvaDRfMjAyMzAyMDFUMDMwMDAwWiBtYXR0aGV3ZGF2aWRwZXJlaXJhQG0)
- [ ] Thu 7-8PM (PST) : [HFLA Website office hours](https://calendar.google.com/calendar/u/0/r/eventedit/MzN1Njlka2ljMW1lMTJmZmk3b2RmOGJybGFfMjAyMzAyMDNUMDMwMDAwWiBtYXR0aGV3ZGF2aWRwZXJlaXJhQG0)

```

### Resources/Instructions
- ["People" GitHub page](https://github.com/orgs/hackforla/people) used to check if someone is a Hack for LA member and their membership is "Public"
- https://www.meetup.com/hackforla/events - If a person is not a member of Hack for LA, they need to sign up for an onboarding session at that link.
- [HackforLA.org website Google Drive](https://drive.google.com/drive/folders/0AKWbU6_2dvZuUk9PVA)
- [Team roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0)
- GitHub Teams:
- [website](https://github.com/orgs/hackforla/teams/website/members)
- [website-write](https://github.com/orgs/hackforla/teams/website-write/members)
- [Accountability buddies spreadsheet](https://docs.google.com/spreadsheets/d/1lGey-Jdb0f9DYsHgGtoAi_Fm2Vr1o9f75RTYvC74oWI/edit#gid=0)
- https://github.com/hackforla/website/issues - For offboarding to see if the person is assigned to any issues
- [2.6 What to do when you need to stop mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue) - For offboarding