website 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 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
Team roster
GitHub Teams:
- website
- website-write
Accountability buddies spreadsheet
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 - For offboarding

May 25 '22 01:05 JessicaLucindaCheng

Hi @JessicaLucindaCheng.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

May 25 '22 01:05 github-actions[bot]

Just testing what the template looks like in this comment

Offboard [INSERT PERSON'S NAME HERE]

[ ] In our HackforLA.org website Google Drive, change membership to “Viewer”.
[ ] Mark them Inactive in our Hack for LA Website Team Roster
[ ] Remove them from our meetings:
- [ ] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [ ] Tue 7-8pm Pacific Time - HfLA developer meeting
- [ ] Thu 7-8pm Pacific Time - HFLA Website office hours
[ ] Go to https://github.com/hackforla/website/issues and filter by "Assignee" to check if the person has any open issues.
- [ ] If they have any open issues,
  - [ ] If it's a prework issue, you can close the issue.
  - [ ] If it's any other issue and if possible, have the person/assignee follow the steps in 2.6 What to do when you need to stop mid issue
    - [ ] If it is not possible for the person/assignee to follow the steps in 2.6 What to do when you need to stop mid issue, you will need to do the steps in 2.6.b 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.
[ ] On GitHub, using their GitHub handle from the roster:
- [ ] Demote member to website only. You may not need to do this step if they were added to website when they joined the team.
- [ ] Remove them from website-write

Jun 22 '22 07:06 JessicaLucindaCheng

Just testing what the template looks like in this comment

Onboard [INSERT NAME OF EACH PERSON HERE]

[ ] Person leading onboarding: please introduce yourself
[ ] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [ ] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [ ] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [ ] Check that their membership is “Public” for the Hack for LA organization.
  - [ ] If it is set to “Private”
    - [ ] Copy the link of the page you are seeing and send it to them in the chat.
    - [ ] Then ask them to change their membership to “Public”.
    - [ ] Then check it again once they are done
[ ] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[ ] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [ ] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [ ] Tue 7-8pm Pacific Time - HfLA developer meeting
- [ ] Thu 7-8pm Pacific Time - HFLA Website office hours
[ ] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [ ] website
- [ ] website-write

Training

[ ] Have the new member create the new issue pre-work checklist for themselves by
- [ ] Adding their name to the title where it says, “[replace brackets with your name]”
- [ ] Click “Submit new issue” button
[ ] Show them how to assign themselves to their pre-work and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jun 22 '22 07:06 JessicaLucindaCheng

@tamara-snyder, @kathrynsilvaconway

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 21, 2022 at 12:20 AM PST.}

Jun 24 '22 07:06 github-actions[bot]

@tamara-snyder

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 28, 2022 at 12:21 AM PST.}

Jul 01 '22 07:07 github-actions[bot]

@tamara-snyder

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, July 5, 2022 at 12:19 AM PST.}

Jul 08 '22 07:07 github-actions[bot]

Onboard Neev Liberman, Justin Dingeman

[x ] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jul 13 '22 02:07 blulady

@tamara-snyder

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, July 12, 2022 at 12:20 AM PST.}

Jul 15 '22 07:07 github-actions[bot]

Onboard Brian Aguda

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jul 20 '22 03:07 kathrynsilvaconway

Onboard John Barrett

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Aug 10 '22 02:08 blulady

Onboard David Attali Maria Paula Reeves

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Aug 31 '22 03:08 kathrynsilvaconway

Onboard Aric Forrest, Bay Bui, Suman and Azania Baker

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Sep 13 '22 06:09 kathrynsilvaconway

Onboard Carole Lago, Paloma Soltys, Rafaela Grison

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [ ] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[ ] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Sep 16 '22 02:09 kathrynsilvaconway

Onboard Sonali Martinez-Najera, Michael Magen, Rolando Zarate

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [ ] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [ ] Tue 7-8pm Pacific Time - HfLA developer meeting
- [ ] Thu 7-8pm Pacific Time - HFLA Website office hours
[ ] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [ ] website
- [ ] website-write
[ ] Have the new member create the new issue pre-work checklist for themselves by
- [ ] Adding their name to the title where it says, “[replace brackets with your name]”
- [ ] Click “Submit new issue” button
[ ] Show them how to assign themselves to their pre-work and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Sep 21 '22 02:09 kathrynsilvaconway

Onboard Josh Bialkin

[ ] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Sep 28 '22 02:09 kathrynsilvaconway

Onboard Dwight Diesmo, George Stemann, Jamie Park, Johnny Wu

[ ] Person leading onboarding: please introduce yourself
[ ] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [ ] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [ ] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [ ] Check that their membership is “Public” for the Hack for LA organization.
  - [ ] If it is set to “Private”
    - [ ] Copy the link of the page you are seeing and send it to them in the chat.
    - [ ] Then ask them to change their membership to “Public”.
    - [ ] Then check it again once they are done
[ ] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[ ] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [ ] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [ ] Tue 7-8pm Pacific Time - HfLA developer meeting
- [ ] Thu 7-8pm Pacific Time - HFLA Website office hours
[ ] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [ ] website
- [ ] website-write
[ ] Have the new member create the new issue pre-work checklist for themselves by
- [ ] Adding their name to the title where it says, “[replace brackets with your name]”
- [ ] Click “Submit new issue” button
[ ] Show them how to assign themselves to their pre-work and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Oct 12 '22 02:10 kathrynsilvaconway

Onboard Dmitrii Tsyplakov, Henry Mu, Eric Santiano, Joshua Juarez, Will Gillis, Suman

[x] Person leading onboarding: please introduce yourself
[ ] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[ ] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [ ] website
- [ ] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Oct 12 '22 02:10 blulady

Onboard Peter Yoo & Matt Bozin & Patrick Oh

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Oct 19 '22 02:10 arpitapandya

Onboard Angelene Manalo and Ernie Pelay

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Nov 13 '22 18:11 blulady

Onboard Satenik

[x] Person leading onboarding: please introduce yourself
[ ] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [ ] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Nov 20 '22 19:11 blulady

Onboard Mai Vang

[x] Person leading onboarding: Justin
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Nov 30 '22 04:11 jdingeman

Onboard Luis Herrera

[x] Person leading onboarding: Justin
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Content Manager”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jan 04 '23 03:01 jdingeman

Onboard Kyra Kwak, Steven Tran, Tea M, Christina Or, Brian Fuentes, Chris Menke, Vincent Dang

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [ ] Copy the link of the page you are seeing and send it to them in the chat.
    - [ ] Then ask them to change their membership to “Public”.
    - [ ] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jan 17 '23 03:01 JessicaLucindaCheng

Onboard Perla Royer

[x] Person leading onboarding: Justin
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10am-12pm Pacific Time- HFLA Website Team Meeting
- [x] Tue 7-8pm Pacific Time - HfLA developer meeting
- [x] Thu 7-8pm Pacific Time - HFLA Website office hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] website
- [x] website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to "role: front end" or "role: back end/devOps" or both label(s) to this issue and remove the "role missing" label
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Jan 25 '23 03:01 jdingeman

Onboard Brian Mui, Jessica DelVecchio, Maria Herzer Natalia Kondratyuk, Nikileshwari Prasadh, Phuong Vu, Ryan Gehris, Samuel Ibarra, Vanessa Vun

[x] Person leading onboarding: Justin Dingeman
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [x] Tue 7-8PM (PST) : HFLA Developers Meeting
- [x] Thu 7-8PM (PST) : HFLA Website Office Hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] Add member to website
- [x] Add member to website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Navigating to the Pre-work Template Issue
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [x] Check their pre-work issue to verify the role label has been handled
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Feb 01 '23 03:02 jdingeman

Onboard Nicolette Mabeza

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [ ] Tue 7-8PM (PST) : HFLA Developers Meeting
- [x] Thu 7-8PM (PST) : HFLA Website Office Hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] Add member to website
- [x] Add member to website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Navigating to the Pre-work Template Issue
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [x] Check their pre-work issue to verify the role label has been handled
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[ ] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [ ] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Feb 14 '23 00:02 plang-psm

Onboard Christopher Foose

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [ ] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [ ] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [ ] If it is set to “Private”
    - [ ] Copy the link of the page you are seeing and send it to them in the chat.
    - [ ] Then ask them to change their membership to “Public”.
    - [ ] Then check it again once they are done
[ ] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[ ] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [ ] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [ ] Tue 7-8PM (PST) : HFLA Developers Meeting
- [ ] Thu 7-8PM (PST) : HFLA Website Office Hours
[ ] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [ ] Add member to website
- [ ] Add member to website-write
[ ] Have the new member create the new issue pre-work checklist for themselves by
- [ ] Navigating to the Pre-work Template Issue
- [ ] Adding their name to the title where it says, “[replace brackets with your name]”
- [ ] Click “Submit new issue” button
[ ] Show them how to assign themselves to their pre-work and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [ ] Check their pre-work issue to verify the role label has been handled
[ ] Show them how to move their pre-work onto the Project Board and have them do it
- [ ] Check their pre-works to make sure they have done it correctly
[ ] Once you have checked their prework has 1) their name in the title, 2) self-assigned the prework, 3) added the role label(s) correctly, and 4) moved it on to the Project Board, do the following
- [ ] Add the milestone 08. Team workflow
- [ ] Move their prework to the In Progress column
[ ] Show them how to navigate to the Project Board
- [ ] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[ ] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[ ] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Feb 14 '23 02:02 JessicaLucindaCheng

Onboard 2/13/23 - Aryan Arora, Samantha Randolph, Keri Medeiros, Andy Arensman, Krista Strucke

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[ ] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [x] Tue 7-8PM (PST) : HFLA Developers Meeting
- [x] Thu 7-8PM (PST) : HFLA Website Office Hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] Add member to website
- [x] Add member to website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Navigating to the Pre-work Template Issue
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [x] Check their pre-work issue to verify the role label has been handled
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Feb 14 '23 03:02 plang-psm

Onboard Micah Elm

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [ ] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [x] Tue 7-8PM (PST) : HFLA Developers Meeting
- [x] Thu 7-8PM (PST) : HFLA Website Office Hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] Add member to website
- [x] Add member to website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Navigating to the Pre-work Template Issue
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [x] Check their pre-work issue to verify the role label has been handled
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Feb 17 '23 03:02 roslynwythe

Onboard Katrina Avena, Vanessa Rodriguez, Billy Phan, Elvis Espinoza, Nancy Luu, Niva Razin, Karen Garcia Cecena, Aldrin Tunque, Garrett Allen, Luis Sotelo, Matthew Malane, Joy Lu, Armando Perez, Ronald Paek, Ashelle Cancio, Erin Pattison

[x] Person leading onboarding: please introduce yourself
[x] On GitHub, go to https://github.com/orgs/hackforla/people and search for their GitHub handle.
- [x] If you search for their GitHub handle and can’t find it, they are not a member of Hack for LA.
  - [x] If they are not a member, tell them to go sign up for onboarding with Bonnie at https://www.meetup.com/hackforla/events. If they have already been tell them they can join 35 minutes late and ask in Q&A (IMPORTANT: Do not add them to anything and just say, “I’m sorry but you need to complete onboarding for the Hack for LA organization before we can onboard you to the team.” Do not continue onboarding them to the team because they can’t start contributing anyways.)
- [x] Check that their membership is “Public” for the Hack for LA organization.
  - [x] If it is set to “Private”
    - [x] Copy the link of the page you are seeing and send it to them in the chat.
    - [x] Then ask them to change their membership to “Public”.
    - [x] Then check it again once they are done
[x] In our HackforLA.org website Google Drive, add the new member(s) as a “Contributor”
[x] Once they are added to the Drive, have them add themselves to the Hack for LA Website Team Roster
- [x] Check that they have completed adding themselves to the Hack for LA Website Team Roster
[x] Ask them if they have been added to our meeting invites in Google Calendar for the following meetings. If not, add them using their email from the roster.
- [x] Sun 10AM-12PM (PST) : HFLA All Website Teams Meeting
- [x] Tue 7-8PM (PST) : HFLA Developers Meeting
- [x] Thu 7-8PM (PST) : HFLA Website Office Hours
[x] On GitHub, add them to the following teams using their GitHub handle from the roster:
- [x] Add member to website
- [x] Add member to website-write
[x] Have the new member create the new issue pre-work checklist for themselves by
- [x] Navigating to the Pre-work Template Issue
- [x] Adding their name to the title where it says, “[replace brackets with your name]”
- [x] Click “Submit new issue” button
[x] Show them how to assign themselves to their pre-work and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Show them how to change the role label to role: front end or role: back end/devOps or both label(s) for this issue and how to remove the role missing label
- [x] Check their pre-work issue to verify the role label has been handled
[x] Show them how to move their pre-work onto the Project Board and have them do it
- [x] Check their pre-works to make sure they have done it correctly
[x] Tell them to leave the pre-work issue in the New Issue Approval column because Bonnie/PMs will move it to In Progress column for them
- [x] Emphasize that the pre-work issue is the only time they will work on an issue that is in the New Issue Approval column and with a Ready for milestone label
[x] Show them how to navigate to the Project Board
- [x] Explain any issue that you are working on besides the pre-work issue should remain in the In Progress column and stay open. Once a member of the merge team or a tech lead merges your pull request associated with that issue, there is automation through GitHub Actions that will take care of moving the issue to a different column and closing the issue.
[x] Explain what accountability buddies are and how it works. Then, add the new members to the accountability buddies spreadsheet
[x] Show them where on their personal GitHub dashboard they can find the issues they are assigned to (including their pre-work) by clicking "Issues" at the very top and "Assigned".

Mar 01 '23 02:03 Adastros

website website copied to clipboard

Onboard & Offboard: Junior Developers

Overview

Action Items

Onboard template

Offboard template

Resources/Instructions

Offboard [INSERT PERSON'S NAME HERE]

Onboard [INSERT NAME OF EACH PERSON HERE]

Onboard Neev Liberman, Justin Dingeman

Onboard Brian Aguda

Onboard John Barrett

Onboard David Attali Maria Paula Reeves

Onboard Aric Forrest, Bay Bui, Suman and Azania Baker

Onboard Carole Lago, Paloma Soltys, Rafaela Grison

Onboard Sonali Martinez-Najera, Michael Magen, Rolando Zarate

Onboard Josh Bialkin

Onboard Dwight Diesmo, George Stemann, Jamie Park, Johnny Wu

Onboard Dmitrii Tsyplakov, Henry Mu, Eric Santiano, Joshua Juarez, Will Gillis, Suman

Onboard Peter Yoo & Matt Bozin & Patrick Oh

Onboard Angelene Manalo and Ernie Pelay

Onboard Satenik

Onboard Mai Vang

Onboard Luis Herrera

Onboard Kyra Kwak, Steven Tran, Tea M, Christina Or, Brian Fuentes, Chris Menke, Vincent Dang

Onboard Perla Royer

Onboard Brian Mui, Jessica DelVecchio, Maria Herzer Natalia Kondratyuk, Nikileshwari Prasadh, Phuong Vu, Ryan Gehris, Samuel Ibarra, Vanessa Vun

Onboard Nicolette Mabeza

Onboard Christopher Foose

Onboard 2/13/23 - Aryan Arora, Samantha Randolph, Keri Medeiros, Andy Arensman, Krista Strucke

Onboard Micah Elm

Onboard Katrina Avena, Vanessa Rodriguez, Billy Phan, Elvis Espinoza, Nancy Luu, Niva Razin, Karen Garcia Cecena, Aldrin Tunque, Garrett Allen, Luis Sotelo, Matthew Malane, Joy Lu, Armando Perez, Ronald Paek, Ashelle Cancio, Erin Pattison

website
website copied to clipboard