Onboard & Offboard: Tech Leads and Merge team #2689

ExperimentsInHonesty · 2022-01-16T22:22:23Z

Dependency

When we need to onboard some new people to the tech lead team

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 template

#### 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
- [ ] If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
- [ ] (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
  - [ ] (Tech leads only) Add to HackforLA.org website drive as Manager
  - [ ] (Tech leads only) 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)
  - [ ] hfla-site-merge channel
  - [ ] hfla-site-onboarding
- [ ] [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)
       - [ ] (Tech leads only) Change membership to maintainer
     - [ ] (Tech leads only) 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.
       - [ ] (Tech leads only) Change membership to maintainer 
- [ ] 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)
  - [ ] Mon 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)
- [ ] (Tech leads only) 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)
   - [ ] (Tech leads only) 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 template

When they leave the team use the Offboarding template

#### 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
- [ ] Remove from hfla-site-merge Slack channel (Only Bonnie/Admin can do this)
- [ ] Google Drive
   - [ ] Demote to "Contributor" in [HfLA website drive](https://drive.google.com/drive/u/0/folders/0AKWbU6_2dvZuUk9PVA)
   - [ ] 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   
- [ ] [Roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0)
  - [ ] Change "Permissions" to "Member"
- [ ] GitHub
     - [ ] Before removing them from any teams, make sure they are already a member of the [website team](https://github.com/orgs/hackforla/teams/website/members) They should already been added to the website team when they joined.
     - [ ] Remove "Maintainer" membership role from [website-write team](https://github.com/orgs/hackforla/teams/website-write/members) and [website team](https://github.com/orgs/hackforla/teams/website/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 (if they are on there)
- [ ] 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
  - [ ] Mon 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

Once offboarded, hide their onboarding and offboarding comment

Resources/Instructions

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

The text was updated successfully, but these errors were encountered:

SAUMILDHANKAR · 2022-02-11T23:41:16Z

SAUMILDHANKAR · 2022-03-04T02:37:17Z

t-will-gillis · 2023-03-21T23:57:42Z

Onboard Bitian Zhang to merge team

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
(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 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
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

t-will-gillis · 2023-03-21T23:58:03Z

Onboard Christina Or to merge team

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
(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 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
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

roslynwythe · 2023-04-14T02:19:20Z

Onboard Chris Menke, Brian Mui

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
(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 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
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

jdingeman · 2023-04-30T19:20:29Z

Onboard MJ Shelton - Merge Team

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
(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 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
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

roslynwythe · 2023-05-30T23:03:28Z

Onboard Drake Nguyen

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
(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 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
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

roslynwythe · 2023-07-06T07:11:16Z

Onboard Johnny Wu, Ronald Paek, Ren Demeis-Ortiz

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
(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 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

roslynwythe · 2023-07-20T02:02:34Z

Onboard Adrian Ang, Richard Kwang

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
(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 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Only applies to tech leads) Change membership to maintainer
- (Only applies to tech leads) Add to website-admins team
  - 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)
- Mon 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
Add to or edit team wiki page
Share Google Data Studio: Hack for LA Organizational Dashboard
- 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
- Unsubscribe from getting notifications from issues and prs unless you are at mentioned

roslynwythe · 2023-07-25T19:30:19Z

roslynwythe · 2023-08-03T02:17:43Z

roslynwythe · 2023-09-08T08:27:02Z

roslynwythe · 2024-01-14T19:07:37Z

Onboard Jay Pham to merge team

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-02-14T08:21:47Z

Onboard Nayan Bhatt, Niki Prasadh

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-02-14T08:22:58Z

roslynwythe · 2024-04-03T07:24:06Z

Onboard Gayle Martin

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-05-20T19:51:15Z

Onboard Mario Antonini

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-06-10T19:35:15Z

t-will-gillis · 2024-07-22T21:41:41Z

roslynwythe · 2024-09-02T21:29:42Z

roslynwythe · 2024-09-12T01:12:46Z

Onboard Danielle Hanson Aras

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-11-13T08:38:14Z

Onboard Daniel Franco

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

roslynwythe · 2024-11-13T23:11:02Z

daras-cu · 2024-11-27T04:17:05Z

Onboard Siyun Feng (Merge Team)

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
If a merge team member is willing to lead dev meetings, request access to the Zoom vault for that member by posting a request in the #admin Slack channel
(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
- (Tech leads only) Add to HackforLA.org website drive as Manager
- (Tech leads only) Add to HfLA website Admin drive as Manager
- 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)
- hfla-site-merge channel
- hfla-site-onboarding
Roster (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
- Add to website team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-write team (They may already be on this team when they did onboarding as a junior developer)
  - Change membership to maintainer
- Add to website-merge team
  - (Tech leads only) Change membership to maintainer
- (Tech leads only) Add to website-admins team
  - Note: website-admins has permissions to allow for deleting of the whole repo, so please be VERY careful.
  - (Tech leads only) Change membership to maintainer
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)
- Mon 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
Add to or edit team wiki page
(Tech leads only) Share Google Data Studio: Hack for LA Organizational Dashboard
- 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)
- (Tech leads only) 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

ExperimentsInHonesty added role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less labels Jan 16, 2022

ExperimentsInHonesty added this to the 08. Team workflow milestone Jan 16, 2022

github-actions bot added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Jan 16, 2022

This comment was marked as outdated.

Sign in to view

ExperimentsInHonesty added Feature: Onboarding/Contributing.md and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Jan 16, 2022

ExperimentsInHonesty mentioned this issue Jan 16, 2022

HfLA: Dev/PM Agenda and Notes #2607

Open

2 tasks

ExperimentsInHonesty removed the Feature: Onboarding/Contributing.md label Jan 18, 2022

This comment was marked as resolved.

Sign in to view

JessicaLucindaCheng mentioned this issue Jan 27, 2022

HfLA Website: Technical leads meeting agenda (and office hours attendance) #2699

Closed

3 tasks

Providence-o mentioned this issue Jan 29, 2022

HfLA: PM Weekly Meeting Agenda #2212

Open

2 tasks

This comment was marked as outdated.

Sign in to view

This comment was marked as resolved.

Sign in to view

ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. Feature: Onboarding/Contributing.md and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Mar 1, 2022

JessicaLucindaCheng self-assigned this Mar 11, 2022

github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 18, 2022

hackforla deleted a comment from github-actions bot Mar 18, 2022

JessicaLucindaCheng removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 18, 2022

github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 25, 2022

JessicaLucindaCheng removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 25, 2022

hackforla deleted a comment from github-actions bot Mar 25, 2022

JessicaLucindaCheng assigned SAUMILDHANKAR Mar 31, 2022

JessicaLucindaCheng added role: dev leads Tasks for technical leads role: back end/devOps Tasks for back-end developers labels Mar 31, 2022

ExperimentsInHonesty unassigned jdingeman Feb 28, 2023

ExperimentsInHonesty added Dependency An issue is blocking the completion or starting of another issue and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Feb 28, 2023

JessicaLucindaCheng mentioned this issue Apr 17, 2023

ER: Remove inactive members from team resources #4541

Closed

3 tasks

ExperimentsInHonesty added the manual dependency release label Jun 9, 2024

ExperimentsInHonesty added this to P: HfLA Website: Project Board Jun 23, 2024

ExperimentsInHonesty moved this to Ice box in P: HfLA Website: Project Board Jun 23, 2024

This comment was marked as duplicate.

Sign in to view

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Onboard & Offboard: Tech Leads and Merge team #2689

Onboard & Offboard: Tech Leads and Merge team #2689

ExperimentsInHonesty commented Jan 16, 2022 •

edited by t-will-gillis

Loading

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as resolved.

SAUMILDHANKAR commented Feb 11, 2022 •

edited by JessicaLucindaCheng

Loading

SAUMILDHANKAR commented Mar 4, 2022 •

edited by JessicaLucindaCheng

Loading

t-will-gillis commented Mar 21, 2023 •

edited

Loading

t-will-gillis commented Mar 21, 2023 •

edited by jdingeman

Loading

roslynwythe commented Apr 14, 2023 •

edited by jdingeman

Loading

jdingeman commented Apr 30, 2023 •

edited

Loading

roslynwythe commented May 30, 2023 •

edited

Loading

roslynwythe commented Jul 6, 2023 •

edited

Loading

roslynwythe commented Jul 20, 2023 •

edited

Loading

roslynwythe commented Jul 25, 2023 •

edited

Loading

roslynwythe commented Aug 3, 2023 •

edited

Loading

roslynwythe commented Sep 8, 2023 •

edited

Loading

roslynwythe commented Jan 14, 2024 •

edited

Loading

roslynwythe commented Feb 14, 2024 •

edited

Loading

roslynwythe commented Feb 14, 2024 •

edited

Loading

roslynwythe commented Apr 3, 2024 •

edited

Loading

roslynwythe commented May 20, 2024 •

edited

Loading

roslynwythe commented Jun 10, 2024 •

edited

Loading

t-will-gillis commented Jul 22, 2024 •

edited

Loading

This comment was marked as duplicate.

roslynwythe commented Sep 2, 2024 •

edited by t-will-gillis

Loading

roslynwythe commented Sep 12, 2024 •

edited

Loading

roslynwythe commented Nov 13, 2024 •

edited

Loading

roslynwythe commented Nov 13, 2024 •

edited by t-will-gillis

Loading

daras-cu commented Nov 27, 2024 •

edited by t-will-gillis

Loading

Onboard & Offboard: Tech Leads and Merge team #2689

Onboard & Offboard: Tech Leads and Merge team #2689

Comments

ExperimentsInHonesty commented Jan 16, 2022 • edited by t-will-gillis Loading

Dependency

Overview

Date Updated

Action Items

Onboard template

Offboard template

Resources/Instructions

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as resolved.

SAUMILDHANKAR commented Feb 11, 2022 • edited by JessicaLucindaCheng Loading

Onboard Jessica Cheng to Tech Lead

SAUMILDHANKAR commented Mar 4, 2022 • edited by JessicaLucindaCheng Loading

Onboard Tamara Snyder to Merge Team

t-will-gillis commented Mar 21, 2023 • edited Loading

Onboard Bitian Zhang to merge team

t-will-gillis commented Mar 21, 2023 • edited by jdingeman Loading

Onboard Christina Or to merge team

roslynwythe commented Apr 14, 2023 • edited by jdingeman Loading

Onboard Chris Menke, Brian Mui

jdingeman commented Apr 30, 2023 • edited Loading

Onboard MJ Shelton - Merge Team

roslynwythe commented May 30, 2023 • edited Loading

Onboard Drake Nguyen

roslynwythe commented Jul 6, 2023 • edited Loading

Onboard Johnny Wu, Ronald Paek, Ren Demeis-Ortiz

roslynwythe commented Jul 20, 2023 • edited Loading

Onboard Adrian Ang, Richard Kwang

roslynwythe commented Jul 25, 2023 • edited Loading

Offboard Chris Menke, Brian Mui

roslynwythe commented Aug 3, 2023 • edited Loading

Offboard Phillip Sanchez, MJ Shelton

roslynwythe commented Sep 8, 2023 • edited Loading

Offboard Johnny Wu

roslynwythe commented Jan 14, 2024 • edited Loading

Onboard Jay Pham to merge team

roslynwythe commented Feb 14, 2024 • edited Loading

Onboard Nayan Bhatt, Niki Prasadh

roslynwythe commented Feb 14, 2024 • edited Loading

Offboard Merge team members: Christina Or, Ronald Paek, Richard Kwang, Sarah Sanger, Adrian Ang

roslynwythe commented Apr 3, 2024 • edited Loading

Onboard Gayle Martin

roslynwythe commented May 20, 2024 • edited Loading

Onboard Mario Antonini

roslynwythe commented Jun 10, 2024 • edited Loading

Offboard Gayle Martin

t-will-gillis commented Jul 22, 2024 • edited Loading

Offboard Drake Nguyen

This comment was marked as duplicate.

roslynwythe commented Sep 2, 2024 • edited by t-will-gillis Loading

Offboard Nayan (Freaky Wrld), Mario Antonini from merge team

roslynwythe commented Sep 12, 2024 • edited Loading

Onboard Danielle Hanson Aras

roslynwythe commented Nov 13, 2024 • edited Loading

Onboard Daniel Franco

roslynwythe commented Nov 13, 2024 • edited by t-will-gillis Loading

Offboard Nikileshwari Prasadh

daras-cu commented Nov 27, 2024 • edited by t-will-gillis Loading

Onboard Siyun Feng (Merge Team)

ExperimentsInHonesty commented Jan 16, 2022 •

edited by t-will-gillis

Loading

SAUMILDHANKAR commented Feb 11, 2022 •

edited by JessicaLucindaCheng

Loading

SAUMILDHANKAR commented Mar 4, 2022 •

edited by JessicaLucindaCheng

Loading

t-will-gillis commented Mar 21, 2023 •

edited

Loading

t-will-gillis commented Mar 21, 2023 •

edited by jdingeman

Loading

roslynwythe commented Apr 14, 2023 •

edited by jdingeman

Loading

jdingeman commented Apr 30, 2023 •

edited

Loading

roslynwythe commented May 30, 2023 •

edited

Loading

roslynwythe commented Jul 6, 2023 •

edited

Loading

roslynwythe commented Jul 20, 2023 •

edited

Loading

roslynwythe commented Jul 25, 2023 •

edited

Loading

roslynwythe commented Aug 3, 2023 •

edited

Loading

roslynwythe commented Sep 8, 2023 •

edited

Loading

roslynwythe commented Jan 14, 2024 •

edited

Loading

roslynwythe commented Feb 14, 2024 •

edited

Loading

roslynwythe commented Feb 14, 2024 •

edited

Loading

roslynwythe commented Apr 3, 2024 •

edited

Loading

roslynwythe commented May 20, 2024 •

edited

Loading

roslynwythe commented Jun 10, 2024 •

edited

Loading

t-will-gillis commented Jul 22, 2024 •

edited

Loading

roslynwythe commented Sep 2, 2024 •

edited by t-will-gillis

Loading

roslynwythe commented Sep 12, 2024 •

edited

Loading

roslynwythe commented Nov 13, 2024 •

edited

Loading

roslynwythe commented Nov 13, 2024 •

edited by t-will-gillis

Loading

daras-cu commented Nov 27, 2024 •

edited by t-will-gillis

Loading