Onboard & Offboard: Engineering

### Overview
We need to have a checklist of items to do when an engineer onboard and offboards so that the process can be consistent and fast.

### Date Updated
Created: 2023-09-13
Updated: 2024-08-24

### Action Items
For each member onboarded/offboarded...
- [ ] Copy template to comment below
- [ ] Add name of person
- [ ] Check off as done

#### Onboard

```
#### Onboard: YYYY-MM-DD
- [ ] Slack channel membership
- [ ] `#311-data-engineering`
- [ ] Google Drive
- [ ] Add to drive as Contributor
- [ ] Add to Google calendar invites
- [ ] Wednesday All-Team meeting
- [ ] Saturday Dev meeting
- [ ] [Roster](https://docs.google.com/spreadsheets/d/1OsLDl7Ciwj7WjtzbgDz38g4kpOMNlUhdjlgzQxtQTvM/edit#gid=0)
- [ ] Send link
- [ ] Team member adds themselves
- [ ] Check for Public
- [ ] GitHub
- [ ] Add to write team
- [ ] Add to read team
- [ ] Confirm that their name is on their Github
- [ ] Bookmark [Engineering Agenda Issue](https://github.com/hackforla/311-data/issues/1720)
- [ ] Visit [Open Github Issues](https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+label%3A%22Role%3A+Frontend%22+no%3Aassignee+-label%3ADependency+-label%3Adraft+-label%3AEpic)
- [ ] Update team page on Wiki
- [ ] Share Tokens and Environment Variables
- [ ] Complete 311-Data repo [Quickstart](https://github.com/hackforla/311-data?tab=readme-ov-file#quick-start)

Roster Required Fields

- Status: Active (required)
- Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
- Dashboard: M (I think it means member? required)
- email: required
- number/texting: optional
- Slack Name: required
- SlackID: required (click your slack picture > ellipses > copy member id)
- everything else: optional

```

#### Offboard

```
#### Offboard: YYYY-MM-DD
- [ ] Remove from Google calendar invite
- You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
- Choose to remove from "This and all following events"
- Send the following cancelation message:
- ``You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.``
- [ ] Wednesday All-Team meeting (ad-hoc)
- [ ] Google Drive
- [ ] 311 Data (ie., project)
- [ ] demote to viewer
- [ ] Roster
- [ ] mark as inactive
- [ ] GitHub
- [ ] demote member to read only team and remove from write team
- [ ] Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
- [ ] Update team page on WIKI
- [How to activate-inactivate team members from roster and wiki]

```

### Resources/Instructions

* [Developer Self Test](https://docs.google.com/presentation/d/1RUQk4mOrv4G1fja_D3GMWMtCyCqsdj64fNPlrIDJhxg/edit#slide=id.g114a9db5138_0_0)
* [Google Drive Link](https://drive.google.com/drive/folders/0AK9EyXeY81U5Uk9PVA)
* [311 Data Team Roster](https://docs.google.com/spreadsheets/d/1OsLDl7Ciwj7WjtzbgDz38g4kpOMNlUhdjlgzQxtQTvM/edit?usp=drive_link)
* Check public and 2FA at [people page](https://github.com/orgs/hackforla/people)
* [GitHub Team URL](https://github.com/hackforla/internship)
- [base (read)](https://github.com/orgs/hackforla/teams/311-data)
- [write](https://github.com/orgs/hackforla/teams/311-data-write)
* WIKI: https://github.com/hackforla/311-data/wiki
* [311-Data Issue tab](https://github.com/hackforla/311-data/issues)
* [311-Data Team Meeting Agenda](https://github.com/hackforla/311-data/issues/1545)
* [311-Data Onboard & Offboard: Engineering](https://github.com/hackforla/311-data/issues/1578)