Onboard & Offboard: Junior Developers

[JessicaLucindaCheng]

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

[blulady]

Onboard Neev Liberman, Justin Dingeman

• [x ] 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".

[kathrynsilvaconway]

Onboard Brian Aguda

• 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".

[roslynwythe]

Onboard Troy Freed, Dylan Prosser, Monica Karasek, Daniel Beyon, Augusto Cerdeira, Adrian Ang, Bin Ma, Jose Padilla, Whitney Gould, Ren Sharon McCane, Louisa Whitaker. In addition, Matthew McCane left before completing roster or creating pre-work checklist.

• 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. 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.)
  • 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".

[roslynwythe]

Onboard John Howell, Janine Soo Thow, Luke Lowrey, Jalen McCloud, Youngsuk Park, Youngsuk Park, Michael Ngo, Divya Prakash Manivannan, Jason McGrath, Alfonso Gutierrez, Michelle Shirk, Si Si, Andrew Kim, Aadil Ahmed, Douglas Rank, Sam Hay, Demi Zayas, Yuji Oshiro, Matthew Chau, Loc Bui, Tomomi Kosaka, Wayne Tsai, Mary Ann Hereford, Tesia Hwang, Jennifer Tieu, Kesang Dingtsa, Taioh Kubota,

• 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. 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.)
  • 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".

[roslynwythe]

Offboard Michael Ngo, mattmalane, aaronweixiangli, richardmundyiii, janice87, mjh-projects, cjmedina95, cristinadz, xewar, anthonylo87, wKategianes, katiehermalik, JSTUN9, thinhmai1027, iuddin, curtis-chung, TJameel120, Nick-McCarthy, Maia-Cochran, vanyanv, codinghorizons, EllenKellyb, Garretallen0, Mayank2808sharma, neshacascia, SeyiAkinwale, imvan2, AndyB909, MitchellMaliglig, aahx, Jimmy-Vu, soleilherring. Abdessittir Harkati, ezchung. louiewhitz, EmmaBin. Dprosser4

• 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 (PST) : HFLA Website Team Meeting
  • Tue 7-8PM (PST) : HFLA developer meeting
  • Thu 7-8PM (PST) : 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

[roslynwythe]

Onboard Brian Joo, Dorian Deptuch, Khinememe Kyaw (prework needs help), Joel Fuelling, Ha Bach, Parag Dhama, Archilkumar Chovatiya, Yuanfang Fu, Homero Ochoa, Hubert Yang, David Wiese, Evan Hesketh, Sai Kiran uriti , Julia Luong, Ravikanth Gundala, John Howell, Rishav Acharya,

• 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. 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.)
  • 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 - why are some set to 03.02 onboarding flow ??
  • 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".

[roslynwythe]

Onboard Erin Zhuang, Daniel Miller, Meru Alimaganbetova, Andy Moc, Dheeraj Koppu, Audrey Rose Wooden, Arturo Ortega, Allison Truhlar, Morgan O'Shaughnessey, Nicholas Jackman, Robert Rodriguez, Jonathan Fang, Gigi Pan, Domenic Scozzafava, Jakob Shavinski, Celena Louissant, Kevin Lei, Nathan Lee, Etyene Franzene, Trevor Kozek, Cameren, Aiden Shaw, Illia Shatts, Rafaeli Rangel, Ajay Bennett, Wassim Chakib

• 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. 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.)
  • 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".

[roslynwythe]

Onboard Anthony Wu, Victor Adeoye, Abu Sayeed Khan, Yolanda Haynes, Bakiballah Sakib, Charlie Sheppard, Robert Njenga, Tony Vang, Kabucho Kuria

• 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. 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.)
  • 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".

[roslynwythe]

Onboard Kyle Foral, Romain Yvernes, Jin Im, Rick Liu, Anh Tran

• 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. 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.)
  • 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".

[roslynwythe]

Onboard Christopher Langley, dustin thomson, Michael Siller, , jack yuan, ethan chen, kevin yu, sediqa fahimi

• 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. 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.)
  • 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".

[roslynwythe]

Payne Fulcher, Sarven Ornekian, James A, Angela Lee, James Leung, Irais Valenzuela, Anahis Valenzuela, Karen Du, James Aguirre, Colin Macrae, Roy Chan

• 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. 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.)
  • 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".

[roslynwythe]

Onboard Michelle Too, Chris Kildunne, Amanda Putney, Iris Jeong, Jack Casica, Dimitra Prousalis, Heejung Hong, Khwa Oo, Jason Lin, Ji Young Kim, Joshua Girgis, J Pham, Vivian Nguyen

• 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. 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.)
  • 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".
• 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. 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.)
  • 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".

[roslynwythe]

Onboard Elton Lin, Eric Pratt, Justin Song, Codi Yost, Max Kasbar, John Apale, Nelson Uprety, Georgette Koo, Ian Cooperman, Daniel Garcia, Josh Wu, Jenny Tak, , Jean-Baptiste Le Vot, Aiden Lee

• 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. 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.)
  • 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".

[roslynwythe]

DRAFT - Junior Dev Onboarding Checklist

• Person leading onboarding: please introduce yourself
• Refer devs to HfLA website dev onboarding slides, which provides these instructions:
  • Complete and submit the Hfla website dev onboarding form to provide access to Google Drive and GitHub website and website-write teams
  • Zoom Registration links for weekly meetings
  • team roster entry
  • pre-work checklist
    • create
    • self-assign
    • apply role labels
    • assign Project Board
    • explain that the pre-work checklist will remain open while they work on other issues, and that this is an exception to the normal process of working through issues serially.
    • demonstrate how to find one's pre-work checklist
  • Project Board demo
    • demonstrate how to navigate to Project Board
    • point out key cards in the leftmost "Onboarding info/links" column
    • demonstrate how to find the Prioritized Backlog column and the importance of assigning issues only from that column. Mention that issues are listed in order of decreasing priority. Open an issue and describe the steps of taking on an issue:
      • self-assignment
      • moving the issue to the "In Progress" column
      • creating a comment with Availability and ETA
      • mention that the process of working on an issue and submitting a PR is described in CONTRIBUTING.md. Demonstrate how to browse to CONTRIBUTING.md
      • what to do if there are blockers
        • Demo creating a comment describing the blocker, then copying the comment link and posting in Slack
        • Demo adding Status: Help label
        • Mention Questions/In Review column

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

[roslynwythe]

Onboard Zachary Kamenov, Alex Constas, Alexander Vasquez, Shi Kuang. Giovanni Mogi, Alexis, Rodriguez, Kim Le, Gina Castromonte, Alex Constas, Carlos Martinez, Vincent Pham, Quyson Nguyen, Param Singh, Zach Yu, Eileen Burdekin, Marcos Garcia, Jonathan Olsen

These members were onboarded on Feb 5: Kuanhsien Yeh, Jessie Wong, Kevin Deakers, Christopher Lee, John Ranier Bueno, Lui Canlas, Ramita Indurkhya, Evan Ishibashi, Ethan Nguyen, Alejandra Dominguez,

• 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. 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.)
  • 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".

[roslynwythe]

Onboard [INSERT NAME OF EVERY PERSON BEING ONBOARDED 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. 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.)
  • 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".

[roslynwythe]

Onboard Yarun Yadav, Taylor Behrens, Sydney Puni, Michael Ruiz, Dana, Denise Lewis, Beatriz Guerrero, Nansamba Ssensalo

• 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. 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.)
  • 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".

[roslynwythe]

Onboard: Miguelcloid Reniva, Kenny Nguyen, Delara Daryaei, Dane Artis, Danielle Andrews, Marek Sautter, Elise Ngo, Wenhao Chen, Tony Li, Briana Preciado, Moaz Ali, Lucca Wang, Urvish Patel, Juan Ramirez

• Person leading onboarding: please introduce yourself
• Refer devs to HfLA website dev onboarding sheet, which provides these instructions:
  • Complete and submit the Hfla website dev onboarding form to provide access to Google Drive and GitHub website and website-write teams
  • Zoom Registration links for weekly meetings
  • team roster entry
  • pre-work checklist
    • self-assign
    • apply role labels
    • assign Project Board
    • explain that the pre-work checklist will remain open while they work on other issues, and that this is an exception to the normal process of working through issues serially.
    • demonstrate how to find one's pre-work checklist
  • Project Board demo
    • demonstrate how to navigate to Project Board
    • point out key cards in the leftmost "Onboarding info/links" column
    • demonstrate how to find the Prioritized Backlog column and the importance of assigning issues only from that column. Mention that issues are listed in order of decreasing priority. Open an issue and describe the steps of taking on an issue:
      • self-assignment
      • moving the issue to the "In Progress" column
      • creating a comment with Availability and ETA
      • mention that the process of working on an issue and submitting a PR is described in CONTRIBUTING.md. Demonstrate how to browse to CONTRIBUTING.md
      • what to do if there are blockers
        • Demo creating a comment describing the blocker, then copying the comment link and posting in Slack
        • Demo adding Status: Help label
        • Mention Questions/In Review column

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

[jphamtv]

@roslynwythe , here’s my feedback and suggestions:

• Remove the Project Board demo completely and place it in the Pre-work Checklist, including any related video demo. Too many people are coming in randomly and waiting around during the meeting, and by that point, they’ve already been in the meeting for over an hour, and taken in so much info already.
• For the Accountability Buddy section, reset the list every onboarding session or break it up by dates. The way it is currently is confusing.
• On slide 2, clarify or remove the “Correction: disregard the 3rd bullet” note if it’s no longer relevant.
• After the new hires finish setting up, let them leave the meeting. Place everything from slides 3 to the end in the Pre-work Checklist. This way, they can complete the remaining tasks at their own pace instead of staying for the entire session.
• Here’s some edits I made for the setting up part: https://docs.google.com/presentation/d/1jg2UusQkY4APKf6Jn-q-pRDYZrae1DzI5cH76GXsMKQ/edit?usp=sharing

[roslynwythe]

DRAFT - Junior Dev Onboarding Checklist

Onboard:

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

[roslynwythe]

@roslynwythe , here’s my feedback and suggestions:

• Remove the Project Board demo completely and place it in the Pre-work Checklist, including any related video demo. Too many people are coming in randomly and waiting around during the meeting, and by that point, they’ve already been in the meeting for over an hour, and taken in so much info already.
• For the Accountability Buddy section, reset the list every onboarding session or break it up by dates. The way it is currently is confusing.
• On slide 2, clarify or remove the “Correction: disregard the 3rd bullet” note if it’s no longer relevant.
• After the new hires finish setting up, let them leave the meeting. Place everything from slides 3 to the end in the Pre-work Checklist. This way, they can complete the remaining tasks at their own pace instead of staying for the entire session.

@jphamtv I agree with your suggestions and the revised slides look great! I just have two minor comments:

• The slides include a note that meetings are not mandatory. That is not consistent with instructions in the pre-work checklists, so I just want to make sure that is ok with Bonnie. Perhaps she is planning to change those instructions regarding meetings. I always tell developers that registration for meetings does not imply a committment to attend a particular meeting but that they should attend at least one meeting a week.
• One common issue in the pre-work issue is that developers don't remove the role: Missing label, so maybe we should include a statement about removing (but not deleting) it.

Thank you J for doing this work. It will really improve the onboarding process and that is a big win for everyone!

[roslynwythe]

@jphamtv I started revising this checklist, please feel free to edit. #3175 (comment)

[jphamtv]

@jphamtv I agree with your suggestions and the revised slides look great! I just have two minor comments:

• The slides include a note that meetings are not mandatory. That is not consistent with instructions in the pre-work checklists, so I just want to make sure that is ok with Bonnie. Perhaps she is planning to change those instructions regarding meetings. I always tell developers that registration for meetings does not imply a committment to attend a particular meeting but that they should attend at least one meeting a week.
• One common issue in the pre-work issue is that developers don't remove the role: Missing label, so maybe we should include a statement about removing (but not deleting) it.

@roslynwythe - Thanks for the feedback! I updated the slides to address your comments.

[t-will-gillis]

Onboard: Saul Mendoza, Jonathan Chue, Delgira Dordzhieva, Deepak Acharya, Shama Tabussum

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

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

[roslynwythe]

Onboard: Pyae (John) Kyaw, Erica Hagle, Jazz B. Chris Flemmond

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

[roslynwythe]

Onboard Andy Phan, Ha Bach, Jennifer S, Monae, Tejas, Aditya Jadnav, David Cotelessa

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

[roslynwythe]

Onboard Troy Freed , Ellis Song, Danielle Aras, Chris, Lindsay Jin, Cindy Guzman, Chase Mayer, Naveen Tata, Crystal Ramos, Mohamed Sharif

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

[roslynwythe]

Onboard Purna Sai Madala, Tony Jin, Austin Labador, Sri Vikas arathanapu, Sai Teja Reddy, Ethan Loh, Mohith Jarapala, Jack S, Colin Buettler, Mimi Boonyasurat, Izma Mujeeb, Izma Mujeeb, Mylavarapu Venkata, Isaac Laster, Sahith Mylavarapu, Jacques Arzu

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. Add a border and date so it is ready for devs 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

[roslynwythe]

Onboard Klavdia Goldshteyn, Jonathan Marin, Nola Dodd, Juan Luis Ramirez, Joseph Katona, Priya Kumbham, Priya Kumbham, John V, Saiteja Siddana, Jonathon Marin, Min Kang, Jacky Hong, Rebecca Crane, Balpreet Hehar, Pluto Bell, Jonathan Rodriguez, Henry Khaung, Maadesh Sivakumar, Michael McClanahan, Syed Mudassir Hussain, Rakshana Balamurugan Santhakumari, Juan Luis Ramirez, Rajwinder Singh

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