Onboard & Offboard: Tech Leads and Merge team

[ExperimentsInHonesty]

Overview

We need to have a checklist of items to do when a technical lead or merge team member onboard and offboards so that the process can be consistent and fast.

Date Updated

• 2022-03-16
• When you integrate the changes from the Changelog, update the date above
• Note: Changelog is based on changes in the org template

Action Items

• [ ] Check to see if the Changelog for this process has new steps in it. If it does and the change is applicable to tech leads and/or merge team members, update this issue's templates (see below) and add the last date you updated the template in the date updated section above
• [ ] Copy template into a new comment below and click "Comment" button
  • [ ] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them and tell them about everything they are gaining access to.
• [ ] Where it says, [ADD NAME AND ROLE OF PERSON BEING ONBOARDED/OFFBOARDED], replace it with the name of the person being onboarded and the role they are onboarding for. For example, John Doe to Merge Team or Jane Doe to Tech Lead
• [ ] Check off as done

#### Onboard [ADD NAME AND ROLE OF PERSON BEING ONBOARDED]
- [ ] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
- [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  - [ ] Invitation
  - [ ] Acceptance
  - [ ] Add to vaults
    - [ ] hackforla.org website vault
    - [ ] Zoom vault
    - [ ] website devs vault
- [ ] (Tech leads only) Grant access to [Zoom Meeting Setup spreadsheet](https://docs.google.com/spreadsheets/d/15P3MYyNQ7Xn0pqdrTynDDipjrLl5LCN9xHVLhk9SWa8/edit#gid=1276874845)
- [ ] (Tech lead only) Set up email forwarding for the following accounts:
  - [ ] websitedevs
  - [ ] webadmins
  - Here are instructions for how to set up email forwarding for each account:
    - Sign into Google account
    - Go to Settings --> See all settings --> Forwarding and POP/IMAP
    - In the "Forwarding", click "Add a forwarding address" and add the email address you want emails to be forwarded to
    - Click "Next". Then confirm that is the email address you want to forward to by clicking "Proceed"
    - A confirmation code will be sent to the forwarding email address. Enter that code in the "confirmation code" box and click "Verify"
    - Then go to "Filters and Blocked Addresses" tab and click "Create a new filter"
      - In the "To" field, enter the email address of the account you are in right now and then click "Create a filter".
      - Check off "Forward it to" and then in the "Choose an address" dropdown, select an email address.
      - Then click the "Create filter" button.
- [ ] Google Drive
  - [ ] Add to HackforLA.org website drive as Manager
  - [ ] Add to HfLA website Admin drive as Manager
  - [ ] Update [on-call spreadsheet](https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=236697191) by
    - [ ] Removing them from "Developers" columns 
    - [ ] If they are joining as a Merge Team member, add them to be on-call at least 2 days a week in the "Tech Lead/Merge Team Member" column. (If there are a lot of Merge Team members, such as 4 or more, this can be reduced to 1 day a week at the discretion of the Tech Lead.)
    - [ ] If they are joining as a Tech Lead and there aren't enough Merge Team members, add the Tech Lead as needed to the the "Tech Lead/Merge Team Member" column. Otherwise, if there are enough Merge Team members, remove the Tech Lead from the "Tech Lead/Merge Team Member" column.
- [ ] Slack channel membership
  - [ ] hfla-site channel (May already have joined as a junior developer)
  - [ ] hfla-site-pr channel (May already have joined as a junior developer)
  - [ ] website-merge channel
- [ ] [Roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0) (They may already be added when they did onboarding as a junior developer but double check.)
  - [ ] Send link
  - [ ] Team member adds themselves
- [ ] GitHub
     - [ ] Check "Public" at [People page](https://github.com/orgs/hackforla/people)
     - [ ] Add to [website team](https://github.com/orgs/hackforla/teams/website/members) (They may already be on this team when they did onboarding as a junior developer)
       - [ ] Change membership to maintainer
     - [ ] Add to [website-write team](https://github.com/orgs/hackforla/teams/website-write/members) (They may already be on this team when they did onboarding as a junior developer)
       - [ ] Change membership to maintainer
     - [ ] Add to [website-merge team](https://github.com/orgs/hackforla/teams/website-merge/members)
       - [ ] (Only applies to tech leads) Change membership to maintainer
     - [ ] (Only applies to tech leads) Add to [website-admins team](https://github.com/orgs/hackforla/teams/website-admins/members)
       - [ ] Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
       - [ ] (Only applies to tech leads) Change membership to maintainer 
- [ ] Figma
  - [ ] Invite
  - [ ] Acceptance
- [ ] Add to Google calendar invites
  - [ ] Sun All Leads Meeting (occurs the first Sunday of each month) 
  - [ ] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  - [ ] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  - [ ] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  - [ ] Sat Dev/PM Meeting (Only required for tech leads)
- [ ] Create issue to add them as a Technical Lead or Merge Team member on the [project page](https://www.hackforla.org/projects/website)
- [ ] Add to or edit [team wiki page](https://github.com/hackforla/website/wiki/Meet-the-Team)
- [ ] Share Google Data Studio: [Hack for LA Organizational Dashboard](https://datastudio.google.com/reporting/16J9XI19pQejSDNFvjl_V3ZezJ502rM_a/page/e1JSB)
  - [ ] Show them where the info from the Dashboard appears on our website: https://www.hackforla.org/dashboard/
- [ ] Train how to 
   - [ ] (Tech leads only) Login to team account
   - [ ] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
     - [ ] Go to `chrome://settings/manageProfile` and click “Create Desktop Shortcut” at the very bottom. Then, look at your desktop and you will see a Google icon for your profile.
     - [ ] This creates desktop shortcuts for Google accounts, which is
       - [ ] Valuable for using different accounts and emails for testing
       - [ ] Handy to have a folder for various Google profile shortcuts 
   - [ ] (Tech leads only) Use Zoom spreadsheet, vault and accounts
   - [ ] Calendar invite
   - [ ] (Tech leads only) Update and change GitHub tokens
   - [ ] Merge pull requests (including "Squash and merge" option)
   - [ ] Go over the Admin drive and how this should only be shared with admin members (including merge team members and tech leads) and only developers working on an issue that needs access
     - [ ] Tell them to read [Wins Form Admin Guide](https://docs.google.com/document/d/1j1JTX5XzotgVCVZ91ImvenedPN5-IVjdSKDukq1B9iE/edit#heading=h.c8tc614ce3iu)
   - [ ] Unsubscribe from getting notifications from issues and prs unless you are at mentioned

#### Offboard [ADD NAME AND ROLE OF PERSON BEING OFFBOARDED]
  - [ ] 1password removal (Only Bonnie/Admin can do this. Only need to do for tech leads because merge team members are not set up with 1password.)
    - [ ] Remove from 
      - [ ] hackforla.org website team vault
      - [ ] Zoom vault
      - [ ] website devs vault
- [ ] Google Drive
   - [ ] Demote to viewer in HackforLA.org website drive
   - [ ] Remove from HfLA website Admin drive
   - [ ] Remove from [on-call spreadsheet](https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=236697191)
- [ ] Remove email forwarding for them in the following accounts:
  - [ ] websitedevs
  - [ ] webadmins   
- [ ] Remove from following Slack channels
  - [ ] website-merge channel (Only Bonnie/Admin can do this)
  - [ ] hfla-site channel
  - [ ] hfla-site-pr channel
- [ ] [Roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0)
  - [ ] Mark as inactive
- [ ] GitHub
     - [ ] Before removing them from website-write, website-merge, or website-admins teams, make sure they are already a member of [website team](https://github.com/orgs/hackforla/teams/website/members) (They may have already been added to website team when they joined. If they are not on the team, please add them.)
       - [ ] Remove maintainer membership role
     - [ ] Remove from [website-write team](https://github.com/orgs/hackforla/teams/website-write/members)
     - [ ] Remove from [website-merge team](https://github.com/orgs/hackforla/teams/website-merge/members)
     - [ ] Remove from [website-admins team](https://github.com/orgs/hackforla/teams/website-admins/members) (Only for tech leads)
- [ ] Figma
  - [ ] Remove from team
- [ ] Remove from Google calendar invites
  - [ ] Sun All Leads Meeting (occurs the first Sunday of each month) 
  - [ ] Sun All Team Meeting
  - [ ] Tue Dev Team Meeting
  - [ ] Thu Dev Office Hours
  - [ ] Sat Dev/PM Meeting (if they are on the invite)
- [ ] Create issue to remove them as a Technical Lead or Merge Team member on the [project page](https://www.hackforla.org/projects/website)
- [ ] Remove them from the [team wiki page](https://github.com/hackforla/website/wiki/Meet-the-Team)
- [ ] Remove access to Google Data Studio: [Hack for LA Organizational Dashboard](https://datastudio.google.com/reporting/16J9XI19pQejSDNFvjl_V3ZezJ502rM_a/page/e1JSB)
- [ ] (Tech leads only) Revoke access to Zoom Meeting Setup spreadsheet

Resources/Instructions

• 1password.com
• HackforLA.org website Google Drive
• HfLA website Admin Google Drive
• Team roster
• Check "Public" at People page
• GitHub Teams:
  • website
  • website-write
• On-call spreadsheet
• WIKI team page
• Hack for LA website Figma

Changelog is based on changes in the [org template](https://raw.githubusercontent.com/hackforla/.github/main/.github/ISSUE_TEMPLATE/onboard---offboard--product.md

[github-actions[bot]]

Hi @ExperimentsInHonesty.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Feature

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[ExperimentsInHonesty]

@JessicaLucindaCheng @SAUMILDHANKAR please review the list above and see if there are additonal items that need to be added or if we need to remove some.

[JessicaLucindaCheng]

@ExperimentsInHonesty @SAUMILDHANKAR I wasn't sure if I was allowed to edit the original post/checklists, so I copy and pasted the checklists below. I made edits below along with some notes about some checklist items I wasn't sure about.

@SAUMILDHANKAR Feel free to make edits to the checklists below.

#### Onboard
- [ ] 1password 
     - [ ] invitation
     - [ ] acceptance
     - [ ] add to vaults
       - [ ] hackforla.org website vault
       - [ ] Zoom vault
- [ ] Google Drive
   - [ ] Add to website drive as Manager
   - [ ] Add to admin drive as Manager
- [ ] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  - [ ] Send link
  - [ ] Team member adds themselves
  - [ ] Check for Public
- [ ] GitHub
     - [ ] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
     - [ ] Add to website-merge team
     - [ ] Add to website-admins team (Not sure if this applies only to tech leads)
     - [ ] Change membership to maintainer
- [ ] Figma
  - [ ] invite
  - [ ] acceptance
- [ ] Invite to Google Calendar meetings
  - [ ] Sun All Team Meeting (may already have invite if joined team as a junior developer)
  - [ ] Tue Dev Team Meeting (may already have invite if joined team as a junior developer)
  - [ ] Thu Dev Office Hours (may already have invite if joined team as a junior developer)
  - [ ] Sat Dev/PM Meeting (Only required for tech leads)
- [ ] Create issue to add them as a Technical Lead on the [project page](https://www.hackforla.org/projects/website) (Only applies to Technical Leads)
- [ ] Add them to the [Website Leadership Team card](https://github.com/hackforla/website/projects/7#card-69730135) on the Project Board
- [ ] Train how to 
   - [ ] login to team account
   - [ ] setup chrome extension shortcut
   - [ ] use zoom spreadsheet, vault and accounts
   - [ ] calendar invite

#### Offboard
  - [ ] 1password setup
    - [ ] remove from team vaults
       - [ ] hackforla.org website vault
       - [ ] Zoom vault
- [ ] Google Drive
   - [ ] demote to viewer in website drive
   - [ ] remove from admin drive
- [ ] Roster
  - [ ] mark as inactive
- [ ] GitHub
     - [ ] Demote member to website-write team
     - [ ] Remove from website-merge team
     - [ ] Remove from website-admins team (Not sure if this applies only to tech leads)
     - [ ] Remove maintainer membership
- [ ] Figma
  - [ ] remove from team (or did we want to demote to viewer?)
- [ ] Remove from Google Calendar meetings
  - [ ] Sun All Team Meeting
  - [ ] Tue Dev Team Meeting
  - [ ] Thu Dev Office Hours
  - [ ] Sat Dev/PM Meeting (Only required for tech leads)
- [ ] Create issue to remove them as a Technical Lead on the [project page](https://www.hackforla.org/projects/website) (Only applies to Technical Leads)
- [ ] Remove them from the [Website Leadership Team card](https://github.com/hackforla/website/projects/7#card-69730135) on the Project Board

[JessicaLucindaCheng]

@SAUMILDHANKAR I updated the templates in https://github.com/hackforla/website/issues/2689#issue-1105203766. I wasn't sure about some of the checklist items, so you will see comments next to some items; edit or remove my comments if you do know the answer. Feel free to make edits to the checklists.

[SAUMILDHANKAR]

Offboard R-Tomas-Gonzalez from Tech Lead

• [x] 1password removal (Only Bonnie can do this)
  • [x] remove from team vaults
    • [x] hackforla.org website vault
    • [x] Zoom vault
• [x] Google Drive
  • [x] demote to viewer in website drive
  • [x] remove from admin drive
• [x] Slack
  • [x] Remove from website-merge channel (Need admin access to remove)
• [x] Roster
  • [x] mark as inactive
• [x] GitHub
  • [x] Demote member to website team
  • [x] Remove from website-write team
  • [x] Remove from website-merge team
  • [x] Remove from website-admins team (Applies only to tech leads)
  • [x] Remove maintainer membership
• [x] Figma
  • [x] remove from team (or did we want to demote to viewer?)
    • [x] Note: Check with Bonnie
• [x] Remove from Google Calendar meetings
  • [x] Sun All Team Meeting
  • [x] Tue Dev Team Meeting
  • [x] Thu Dev Office Hours
  • [x] Sat Dev/PM Meeting (Only required for tech leads)
• [x] Create issue to remove them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Remove them from the Website Leadership Team card on the Project Board

[SAUMILDHANKAR]

Onboard Jessica Cheng to Tech Lead

• [x] 1password (Only Bonnie can do these steps)
  • [x] invitation
  • [x] acceptance
  • [x] add to vaults
    • [x] hackforla.org website vault
    • [x] Zoom vault
• [x] Google Drive
  • [x] Add to website drive as Manager
  • [x] Add to admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Slack
  • [x] Add to website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [x] GitHub
  • [x] Add to website team (Do I, Jessica, request to join myself?)
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  • [x] Add to website-merge team
  • [x] Add to website-admins team (Only for tech leads)
  • [x] Change membership to maintainer
  • [x] Check for Public
• [x] Figma
  • [x] invite
  • [x] acceptance
• [x] Invite to Google Calendar meetings
  • [x] Sun All Team Meeting (may already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (may already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (may already have invite if joined team as a junior developer)
  • [x] Sat Dev/PM Meeting (Only required for tech leads)
• [x] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Add them to the Website Leadership Team card on the Project Board
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [ ] Train how to
  • [x] login to team account (tech leads only)
  • [ ] setup chrome shortcut for adding to desktop
  • [x] use zoom spreadsheet, vault and accounts (tech leads only)
  • [x] calendar invite

[SAUMILDHANKAR]

Onboard Tamara Snyder to Merge Team

• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Add to following Slack channels
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [ ] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [ ] Change membership to maintainer (Only applies to tech leads)
  • [ ] Add to website-admins team (Only applies to tech leads)
    • [ ] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [x] Invite to Google Calendar meetings
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Add them to the Website Leadership Team card on the Project Board
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [ ] Train how to
  • [ ] login to team account (tech leads only)
  • [ ] setup chrome shortcut for adding to desktop
  • [ ] use zoom spreadsheet, vault and accounts (tech leads only)
  • [x] calendar invite

[JessicaLucindaCheng]

Onboard Adolf Schmuck to Merge Team

• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Add to following Slack channels
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [ ] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [ ] Change membership to maintainer (Only applies to tech leads)
  • [ ] Add to website-admins team (Only applies to tech leads)
    • [ ] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [x] Invite to Google Calendar meetings
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Add them to the Website Leadership Team card on the Project Board
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [ ] Train how to
  • [ ] login to team account (tech leads only)
  • [ ] setup chrome shortcut for adding to desktop
  • [ ] use zoom spreadsheet, vault and accounts (tech leads only)
  • [x] calendar invite

[JessicaLucindaCheng]

@SAUMILDHANKAR I'm done editing the templates. Passing this on to you to check if we need to add/modify anything else in the templates: https://github.com/hackforla/website/issues/2689#issue-1105203766.

[SAUMILDHANKAR]

@SAUMILDHANKAR I'm done editing the templates. Passing this on to you to check if we need to add/modify anything else in the templates: #2689 (comment).

@JessicaLucindaCheng Thank you. I have added updating On-call spreadsheet to our template. Also, planning to remove setup chrome shortcut action item once you confirm, since it is not applicable to our team.

[JessicaLucindaCheng]

@SAUMILDHANKAR

@SAUMILDHANKAR I'm done editing the templates. Passing this on to you to check if we need to add/modify anything else in the templates: #2689 (comment).

@JessicaLucindaCheng Thank you. I have added updating On-call spreadsheet to our template. Also, planning to remove setup chrome shortcut action item once you confirm, since it is not applicable to our team.

I'm not sure what setup chrome shortcut refers to, so you could ask Bonnie about it before you delete it.

[github-actions[bot]]

@SAUMILDHANKAR, @JessicaLucindaCheng

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "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, April 5, 2022 at 12:20 AM PST.}

[JessicaLucindaCheng]

• Progress: Done editing the template, except for not knowing what the Chrome Extension refers to.
• Blockers: None
• Availability: N/A because this is just an onboarding/offboarding checklist that is an ongoing issue and only done when needed.
• ETA: N/A because this is just an onboarding/offboarding checklist that is an ongoing issue and only done when needed.

[SAUMILDHANKAR]

@SAUMILDHANKAR

@SAUMILDHANKAR I'm done editing the templates. Passing this on to you to check if we need to add/modify anything else in the templates: #2689 (comment).

@JessicaLucindaCheng Thank you. I have added updating On-call spreadsheet to our template. Also, planning to remove setup chrome shortcut action item once you confirm, since it is not applicable to our team.

I'm not sure what setup chrome shortcut refers to, so you could ask Bonnie about it before you delete it.

We are going to leave the chrome shortcut as it is but add more description to it as well as a link.

[SAUMILDHANKAR]

Onboard Devin Krizwold to Merge Team

• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Add to following Slack channels
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [ ] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [ ] Change membership to maintainer (Only applies to tech leads)
  • [ ] Add to website-admins team (Only applies to tech leads)
    • [ ] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [ ] Invite to Google Calendar meetings
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Add them to the Website Leadership Team card on the Project Board
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [ ] Train how to
  • [ ] login to team account (tech leads only)
  • [ ] setup chrome shortcut for adding to desktop
  • [ ] use zoom spreadsheet, vault and accounts (tech leads only)
  • [x] calendar invite

[SAUMILDHANKAR]

Onboard Jaret Balba to Merge Team

• [x] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [ ] Set up email forwarding for the following accounts:
  • [ ] websitedevs
  • [ ] webadmins
• [x] Slack channel membership
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [x] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [ ] Change membership to maintainer (Only applies to tech leads)
  • [ ] Add to website-admins team (Only applies to tech leads)
    • [ ] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [ ] Add to Google calendar invites
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads)
• [x] Add to team page on Wiki
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [x] Grant access to Zoom Meeting Setup spreadsheet
• [x] Train how to
  • [ ] Login to team account (tech leads only)
  • [x] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
  • [ ] Use Zoom spreadsheet, vault and accounts (tech leads only)
  • [x] Calendar invite
  • [ ] Update and change GitHub tokens (tech leads only)
  • [x] Merge pull requests (including "Squash and merge" option)
  • [x] Go over the Admin drive

[JessicaLucindaCheng]

Onboard Tamara Snyder to Tech Lead

• [x] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [x] (Tech leads only) Grant access to Zoom Meeting Setup spreadsheet
• [ ] Set up email forwarding for the following accounts:
  • [ ] websitedevs
  • [ ] webadmins
• [ ]
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Slack channel membership
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [ ] Send link
  • [ ] Team member adds themselves
• [x] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [x] Change membership to maintainer (Only applies to tech leads)
  • [x] Add to website-admins team (Only applies to tech leads)
    • [x] Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
    • [x] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [x] Add to Google calendar invites
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [x] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] (Technical leads only )Create issue to add them as a Technical Lead on the project page
• [x] Add to team page on Wiki
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website: https://www.hackforla.org/dashboard/
• [ ] Train how to
  • [ ] (Tech leads only) Login to team account
  • [x] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
    • [ ] Go to chrome://settings/manageProfile and click “Create Desktop Shortcut” at the very bottom. Then, look at your desktop and you will see a Google icon for your profile.
    • [ ] This creates desktop shortcuts for Google accounts, which is
      • [ ] Valuable for using different accounts and emails for testing
      • [ ] Handy to have a folder for various Google profile shortcuts
  • [ ] (Tech leads only) Use Zoom spreadsheet, vault and accounts
  • [x] Calendar invite
  • [ ] (Tech leads only) Update and change GitHub tokens
  • [x] Merge pull requests (including "Squash and merge" option)
  • [x] Go over the Admin drive and how this should only be shared with admin members (including merge team members and tech leads) and only developers working on an issue that needs access
    • [x] Tell them to read Wins Form Admin Guide
  • [ ] Unsubscribe from getting notifications from issues and prs unless you are at mentioned

[tamara-snyder]

Onboard Kathryn Silva Conway to Merge Team

• [x] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
• [x] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [x] Invitation
  • [x] Acceptance
  • [x] Add to vaults
    • [x] hackforla.org website vault
    • [x] Zoom vault
    • [x] website devs vault
• [x] (Tech leads only) Grant access to Zoom Meeting Setup spreadsheet
• [ ] (Tech leads only) Set up email forwarding for the following accounts:
  • [ ] websitedevs
  • [ ] webadmins
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet
• [x] Slack channel membership
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [x] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [x] Change membership to maintainer (Only applies to tech leads)
  • [x] Add to website-admins team (Only applies to tech leads)
    • [x] Note: website-admins have permissions to allow for deleting of the whole repo, so please be VERY careful.
    • [x] Change membership to maintainer (Only applies to tech leads)
• [x] Figma
  • [x] Invite
  • [x] Acceptance
• [x] Add to Google calendar invites
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [x] Sat Dev/PM Meeting (Only required for tech leads)
• [x] Create issue to add them as a Technical Lead on the project page (Only applies to Technical Leads) - https://github.com/hackforla/website/issues/3177#issuecomment-1147979492
• [x] Add to team page on Wiki
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website
• [x] Train how to
  • [x] Login to team account (tech leads only)
  • [x] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
    • [x] Go to chrome://settings/manageProfile and click “Create Desktop Shortcut” at the very bottom. Then, look at your desktop and you will see a Google icon for your profile.
    • [x] This creates desktop shortcuts for Google accounts, which is
      • [x] Valuable for using different accounts and emails for testing
      • [x] Handy to have a folder for various Google profile shortcuts
  • [x] Use Zoom spreadsheet, vault and accounts (tech leads only)
  • [x] Calendar invite
  • [x] Update and change GitHub tokens (tech leads only)
    • [x] ElizabethHonestBot
    • [x] HackforLABot
  • [x] Merge pull requests (including "Squash and merge" option)
  • [x] Go over the Admin drive

[JessicaLucindaCheng]

@SAUMILDHANKAR We need to update this. @JessicaLucindaCheng will update it.

• [x] Update instructions for the change log and clarify it
• [x] Update "Add name" update so it says add name and role
• [x] Add action item to copy paste template and click Comment button before checking off items
• [x] Template
  • [x] Explain update on-call spreadsheet and specify what to update. Also, add link in-line.
  • [x] Add link to roster in action item in-line
  • [x] Add link for where to check public in-line
  • [x] Add link for where to add to website, website-write, etc
  • [x] Add (Tech leads only) to beginning of each action item
  • [x] Restrict email forwarding to tech leads only
  • [x] Add instructions for How to email forwarding:
    • [x] Sign into Google account
    • [x] Go to Settings --> See all settings --> Forwarding and POP/IMAP
    • [x] In the "Forwarding", click "Add a forwarding address" and add the email address you want emails to be forwarded to
    • [x] Click Next. Then confirm that is the email address you want to forward to by clicking Proceed
    • [x] A confirmation code will be sent to the forwarding email address. Enter that code in the "confirmation code" box and click Verify
    • [x] Then go to Filters and Blocked Addresses tab and click Create a new filter
      • [x] In the To field, enter the email address of the account you are in right now and then click Create a filter.
      • [x] Check off Forward it to and Choose an email address
      • [x] Then click the Create filter button.

[github-actions[bot]]

@SAUMILDHANKAR, @JessicaLucindaCheng, @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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "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 7, 2022 at 12:21 AM PST.}

[JessicaLucindaCheng]

• Progress: I still need to update this issue based on the comments in here: https://github.com/hackforla/website/issues/2689#issuecomment-1145512547
• Blockers: None
• Availability: Not sure
• ETA: July 9, 2022 (at the latest but hopefully will get this done sooner)

[github-actions[bot]]

@SAUMILDHANKAR, @JessicaLucindaCheng, @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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. 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.}

[JessicaLucindaCheng]

• Progress: I still need to update this issue based on the comments in here: https://github.com/hackforla/website/issues/2689#issuecomment-1145512547
• Blockers: None
• Availability: 2 hours
• ETA: July 2, 2022 (at the latest but hopefully will get this done sooner)

[tamara-snyder]

Onboard [Wilny Duong and Sarah Sanger]

• [x] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
• [ ] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [ ] Invitation
  • [ ] Acceptance
  • [ ] Add to vaults
    • [ ] hackforla.org website vault
    • [ ] Zoom vault
    • [ ] website devs vault
• [ ] (Tech leads only) Grant access to Zoom Meeting Setup spreadsheet
• [ ] Set up email forwarding for the following accounts:
  • [ ] websitedevs
  • [ ] webadmins
• [x] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet by
    • [x] Removing them from "Developers" columns
    • [x] If they are joining as a Merge Team member, add them to be on-call at least 2 days a week in the "Tech Lead/Merge Team Member" column. (If there are a lot of Merge Team members, such as 4 or more, this can be reduced to 1 day a week at the discretion of the Tech Lead.)
    • [x] If they are joining as a Tech Lead and there aren't enough Merge Team members, add the Tech Lead as needed to the the "Tech Lead/Merge Team Member" column. Otherwise, if there are enough Merge Team members, remove the Tech Lead from the "Tech Lead/Merge Team Member" column.
• [x] Slack channel membership
  • [x] hfla-site channel (May already have joined as a junior developer)
  • [x] hfla-site-pr channel (May already have joined as a junior developer)
  • [x] website-merge channel
• [x] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [x] Send link
  • [x] Team member adds themselves
• [ ] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [ ] Change membership to maintainer (Only applies to tech leads)
  • [ ] Add to website-admins team (Only applies to tech leads)
    • [ ] Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
    • [ ] Change membership to maintainer (Only applies to tech leads)
• [ ] Figma
  • [x] Invite
  • [ ] Acceptance
• [x] Add to Google calendar invites
  • [x] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [x] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [x] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [ ] (Technical leads only )Create issue to add them as a Technical Lead on the project page
• [x] Add to team page on Wiki
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website: https://www.hackforla.org/dashboard/
• [ ] Train how to
  • [ ] (Tech leads only) Login to team account
  • [ ] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
    • [ ] Go to chrome://settings/manageProfile and click “Create Desktop Shortcut” at the very bottom. Then, look at your desktop and you will see a Google icon for your profile.
    • [ ] This creates desktop shortcuts for Google accounts, which is
      • [ ] Valuable for using different accounts and emails for testing
      • [ ] Handy to have a folder for various Google profile shortcuts
  • [ ] (Tech leads only) Use Zoom spreadsheet, vault and accounts
  • [x] Calendar invite
  • [ ] (Tech leads only) Update and change GitHub tokens
  • [ ] Merge pull requests (including "Squash and merge" option)
  • [x] Go over the Admin drive and how this should only be shared with admin members (including merge team members and tech leads) and only developers working on an issue that needs access
    • [x] Tell them to read Wins Form Admin Guide
  • [x] Unsubscribe from getting notifications from issues and prs unless you are at mentioned

[github-actions[bot]]

@SAUMILDHANKAR, @JessicaLucindaCheng, @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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. 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.}

[tamara-snyder]

Onboard Kathryn Silva Conway as Tech Lead

• [x] If you are onboarding a tech lead or merge team member, please set up a 1 hour time slot to meet with them so that you can go through this checklist with them, and add them to and tell them about everything they are gaining access to.
• [x] 1password (Only Bonnie/Admin can do these steps and this should only be set up for tech leads)
  • [x] Invitation
  • [x] Acceptance
  • [x] Add to vaults
    • [x] hackforla.org website vault
    • [x] Zoom vault
    • [x] website devs vault
• [x] (Tech leads only) Grant access to Zoom Meeting Setup spreadsheet
• [ ] (Tech lead only) Set up email forwarding for the following accounts:
  • [ ] websitedevs
  • [ ] webadmins
  • Here are instructions for how to set up email forwarding for each account:
    • Sign into Google account
    • Go to Settings --> See all settings --> Forwarding and POP/IMAP
    • In the "Forwarding", click "Add a forwarding address" and add the email address you want emails to be forwarded to
    • Click "Next". Then confirm that is the email address you want to forward to by clicking "Proceed"
    • A confirmation code will be sent to the forwarding email address. Enter that code in the "confirmation code" box and click "Verify"
    • Then go to "Filters and Blocked Addresses" tab and click "Create a new filter"
      • In the "To" field, enter the email address of the account you are in right now and then click "Create a filter".
      • Check off "Forward it to" and then in the "Choose an address" dropdown, select an email address.
      • Then click the "Create filter" button.
• [ ] Google Drive
  • [x] Add to HackforLA.org website drive as Manager
  • [x] Add to HfLA website Admin drive as Manager
  • [x] Update on-call spreadsheet by
    • [ ] Removing them from "Developers" columns
    • [ ] If they are joining as a Merge Team member, add them to be on-call at least 2 days a week in the "Tech Lead/Merge Team Member" column. (If there are a lot of Merge Team members, such as 4 or more, this can be reduced to 1 day a week at the discretion of the Tech Lead.)
    • [ ] If they are joining as a Tech Lead and there aren't enough Merge Team members, add the Tech Lead as needed to the the "Tech Lead/Merge Team Member" column. Otherwise, if there are enough Merge Team members, remove the Tech Lead from the "Tech Lead/Merge Team Member" column.
• [ ] Slack channel membership
  • [ ] hfla-site channel (May already have joined as a junior developer)
  • [ ] hfla-site-pr channel (May already have joined as a junior developer)
  • [ ] website-merge channel
• [ ] Roster (They may already be added when they did onboarding as a junior developer but double check.)
  • [ ] Send link
  • [ ] Team member adds themselves
• [x] GitHub
  • [x] Check for Public
  • [x] Add to website team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
    • [x] Change membership to maintainer
  • [x] Add to website-merge team
    • [x] Change membership to maintainer (Only applies to tech leads)
  • [x] Add to website-admins team (Only applies to tech leads)
    • [x] Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
    • [x] Change membership to maintainer (Only applies to tech leads)
• [ ] Figma
  • [ ] Invite
  • [ ] Acceptance
• [x] Add to Google calendar invites
  • [ ] Sun All Leads Meeting (occurs the first Sunday of each month)
  • [ ] Sun All Team Meeting (May already have invite if joined team as a junior developer)
  • [ ] Tue Dev Team Meeting (May already have invite if joined team as a junior developer)
  • [ ] Thu Dev Office Hours (May already have invite if joined team as a junior developer)
  • [ ] Sat Dev/PM Meeting (Only required for tech leads)
• [x] (Technical leads only )Create issue to add them as a Technical Lead on the project page
• [x] Add to team page on Wiki
• [x] Share Google Data Studio: Hack for LA Organizational Dashboard
  • [x] Show them where the info from the Dashboard appears on our website: https://www.hackforla.org/dashboard/
• [ ] Train how to
  • [x] (Tech leads only) Login to team account
  • [ ] Setup shortcut for adding a profile to the desktop: chrome://settings/manageProfile
    • [ ] Go to chrome://settings/manageProfile and click “Create Desktop Shortcut” at the very bottom. Then, look at your desktop and you will see a Google icon for your profile.
    • [ ] This creates desktop shortcuts for Google accounts, which is
      • [ ] Valuable for using different accounts and emails for testing
      • [ ] Handy to have a folder for various Google profile shortcuts
  • [x] (Tech leads only) Use Zoom spreadsheet, vault and accounts
  • [ ] Calendar invite
  • [ ] (Tech leads only) Update and change GitHub tokens
  • [ ] Merge pull requests (including "Squash and merge" option)
  • [x] Go over the Admin drive and how this should only be shared with admin members (including merge team members and tech leads) and only developers working on an issue that needs access
    • [ ] Tell them to read Wins Form Admin Guide
  • [ ] Unsubscribe from getting notifications from issues and prs unless you are at mentioned

[JessicaLucindaCheng]

• Progress: I still need to update this issue based on the comments in here: https://github.com/hackforla/website/issues/2689#issuecomment-1145512547
• Blockers: None
• Availability: 2 hours
• ETA: July 17, 2022 (at the latest but hopefully will get this done sooner)

[github-actions[bot]]

@SAUMILDHANKAR, @JessicaLucindaCheng, @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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. 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 19, 2022 at 12:21 AM PST.}

[JessicaLucindaCheng]

• Progress: I'm done editing this issue.
• Blockers: None
• Availability: N/A
• ETA: Done

[github-actions[bot]]

Hi @kathrynsilvaconway, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)