Onboarding Checklist Issue

[epierotti3]

Guidelines

• I agree to follow this project's Contributing Guidelines.

Is there an existing issue for this?

• I have searched the existing issues

Dependencies

None

Overview

We need to create a checklist of items to do whenever a new volunteer joins TrashAI so that they know exactly where to get started. This should make this process consistent and efficient.

Action Items

THIS ISSUE WILL NEVER CLOSE! Simply follow the instructions below to create a thread of comments every time we onboard new volunteers.

• Copy template to comment below
• Add name of person into comment
• Check off each item as they are completed.

#### Onboard [replace with name] 
- [ ] GitHub
     - [ ] Add to code for sacramento team
     - [ ] Add to trash-ai team
     - [ ] Confirm that their name is on their Github (makes it easier to know who is working on what)
- [ ] Slack channel membership
     - [ ] ```#proj-trash-ai```
- [ ] [Google Drive](https://drive.google.com/drive/folders/1Hk4LdyVFcVPGCAd5bncswaxLKX1bDuNe)
     - [ ] Add to drive as Viewer first, change to Contributor as needed
(As of right now there are a few different google drives, which is another problem, but make sure the new volunteer is added to whatever they need)
- [ ] [Figma](https://www.figma.com/file/TBRSf0DLvmqnuV1hLNkwbo/Trash-AI?type=design&node-id=0-1&t=SXt8TycSQC7pZv9j-0) (as needed)
     - [ ] send them an invite
     - [ ] make sure they accept
- [ ] Walk them through the [project board](https://github.com/orgs/code4sac/projects/13)
     - [ ] talk about open issues

Anything else?

No response

[epierotti3]

Here's an example:

Onboard Elizabeth Pierotti

• Slack channel membership
  • #proj-trash-ai
• Google Drive
  • Add to drive as Viewer first, change to Contributor as needed
    (As of right now there are a few different google drives, which is another problem, but make sure the new volunteer is added to whatever they need)
• GitHub
  • Add to code for sacramento team
  • Add to trash-ai team
  • Confirm that their name is on their Github (makes it easier to know who is working on what)
• Figma (as needed)
  • send them an invite
  • make sure they accept
• Walk them through the project board and talk about open issues

[epierotti3]

Onboard Jacob @gandalfthegreenery

• GitHub
  • Add to code for sacramento team (Brianda needs to do this)
  • Add to trash-ai team (Elizabeth can do this)
  • Confirm that their name is on their Github (makes it easier to know who is working on what) - > "gandalfthegreenery"
• Slack channel membership
  • #proj-trash-ai
• Google Drive
  • Add to drive as Viewer first, change to Contributor as needed
    (As of right now there are a few different google drives, which is another problem, but make sure the new volunteer is added to whatever they need)
• Figma (as needed)
  • send them an invite
  • make sure they accept
• Walk them through the project board
  • talk about open issues

[epierotti3]

Onboard Ade

• GitHub
  • Add to code for sacramento team
  • Add to trash-ai team
  • Confirm that their name is on their Github (makes it easier to know who is working on what)
• Slack channel membership
  • #proj-trash-ai
• Google Drive
  • Add to drive as Viewer first, change to Contributor as needed
    (As of right now there are a few different google drives, which is another problem, but make sure the new volunteer is added to whatever they need)
• Figma (as needed)
  • send them an invite
  • make sure they accept
• Walk them through the project board
  • talk about open issues

[epierotti3]

Onboard Ruoyu Li

• GitHub -> username is RuoyuLII
  • Add to code for sacramento team
  • Add to trash-ai team
  • Confirm that their name is on their Github (makes it easier to know who is working on what)
• Slack channel membership
  • #proj-trash-ai
• Google Drive
  • Add to drive as Viewer first, change to Contributor as needed
    (As of right now there are a few different google drives, which is another problem, but make sure the new volunteer is added to whatever they need)
• Figma (as needed)
  • send them an invite
  • make sure they accept
• Walk them through the project board
  • talk about open issues