Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Onboard & Offboard: Engineering #1578

Open
3 tasks
ryanfchase opened this issue Sep 14, 2023 · 40 comments
Open
3 tasks

Onboard & Offboard: Engineering #1578

ryanfchase opened this issue Sep 14, 2023 · 40 comments
Assignees
@ryanfchase
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) Feature: GitHub Board/Onboarding Anything to do with team onboarding Role: Frontend React front end work size: 0.25pt Can be done in 1.5 hours
Milestone
W - Ongoing

Comments

@ryanfchase
Copy link
Member

ryanfchase commented Sep 14, 2023 •
edited
Loading

Overview

We need to have a checklist of items to do when an engineer onboard and offboards so that the process can be consistent and fast.

Date Updated

Created: 2023-09-13
Updated: 2024-08-24

Action Items

For each member onboarded/offboarded...

  • Copy template to comment below
  • Add name of person
  • Check off as done

Onboard

#### Onboard: YYYY-MM-DD <name>
- [ ] Slack channel membership
 - [ ] Google Drive
   - [ ] Add to drive as Contributor
- [ ] Add to Google calendar invites
   - [ ] Wednesday All-Team meeting
   - [ ] Saturday Dev meeting
- [ ] [Roster](https://docs.google.com/spreadsheets/d/1OsLDl7Ciwj7WjtzbgDz38g4kpOMNlUhdjlgzQxtQTvM/edit#gid=0)
  - [ ] Send link
  - [ ] Team member adds themselves
  - [ ] Check for Public
- [ ] GitHub
     - [ ] Add to write team
     - [ ] Add to read team
     - [ ] Confirm that their name is on their Github 
- [ ] Bookmark [Engineering Agenda Issue](https://github.com/hackforla/311-data/issues/1720)
- [ ] Visit [Open Github Issues](https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+label%3A%22Role%3A+Frontend%22+no%3Aassignee+-label%3ADependency+-label%3Adraft+-label%3AEpic)
- [ ] Update team page on Wiki
- [ ] Share Tokens and Environment Variables
- [ ] Complete 311-Data repo [Quickstart](https://github.com/hackforla/311-data?tab=readme-ov-file#quick-start)


<details><summary>Roster Required Fields</summary>
<p>


- Status: Active (required)
- Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
- Dashboard: M (I think it means member? required)
- email: required
- number/texting: optional
- Slack Name: required
- SlackID: required (click your slack picture > ellipses > copy member id)
- everything else: optional

<img src="https://github.com/hackforla/311-data/assets/6414668/45fc1596-ef3d-4aa5-a586-495e5eb1df58" width="254">

</p>
</details>

Offboard

#### Offboard: YYYY-MM-DD <name>
- [ ] Remove from Google calendar invite
   - You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
   - Choose to remove from "This and all following events"
   - Send the following cancelation message:
      - ``You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.``  
   - [ ] Wednesday All-Team meeting (ad-hoc)
- [ ] Google Drive
   - [ ] 311 Data (ie., project)  
      - [ ] demote to viewer
- [ ] Roster
  - [ ] mark as inactive
- [ ] GitHub
     - [ ] demote member to read only team and remove from write team
     - [ ] Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
- [ ] Update team page on WIKI
  - [How to activate-inactivate team members from roster and wiki]

Resources/Instructions
@ryanfchase ryanfchase self-assigned this Sep 15, 2023
@ryanfchase ryanfchase changed the title WIP: Onboard & Offboard: Engineering Onboard & Offboard: Engineering Sep 15, 2023
@ryanfchase ryanfchase mentioned this issue Sep 15, 2023
Closed
2 tasks
@ryanfchase ryanfchase added Role: Frontend React front end work and removed Role: Missing labels Sep 21, 2023
@ryanfchase ryanfchase added this to the 0.11 Onboarding Flow milestone Sep 21, 2023
@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 21, 2023 •
edited
Loading

Onboard 2023-09-20 Sophia Bui

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Share tokens and environment variables

@ryanfchase ryanfchase added Feature: GitHub Board/Onboarding Anything to do with team onboarding and removed Feature: agenda labels Sep 21, 2023
@ryanfchase

This comment was marked as outdated.

Sign in to view
@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 25, 2023 •
edited
Loading

Onboard 2023-09-24 Johnny Wu

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 28, 2023 •
edited
Loading

Onboard 2023-09-27 Tamara Lazerka

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 28, 2023 •
edited
Loading

Onboard 2023-09-27 Andre Abad

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 28, 2023 •
edited by nxgrizzle
Loading

Onboard 2023-09-27 Nicole Grizzle (nxgrizzle@gmail.com)

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Oct 18, 2023 •
edited
Loading

Onboard 2023-10-18 Robert Schacht

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@edwinjue
Copy link
Member

edwinjue commented Oct 18, 2023 •
edited by ryanfchase
Loading

Onboard 2023-10-18 Billy Phan

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@edwinjue
Copy link
Member

edwinjue commented Oct 18, 2023 •
edited by shavinski
Loading

Onboard 2023-10-18 Jakob Shavinski

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@edwinjue
Copy link
Member

edwinjue commented Oct 18, 2023 •
edited by aqandrew
Loading

Onboard 2023-10-18 Romain Yvernes (romainyvernes@gmail.com)

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@edwinjue
Copy link
Member

edwinjue commented Oct 19, 2023 •
edited by spencerleemeredith
Loading

Onboard 2023-10-18 Spencer Meredith (Spencerleemeredith@gmail.com)

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@edwinjue
Copy link
Member

edwinjue commented Oct 20, 2023 •
edited by ryanfchase
Loading

Onboard 2023-10-20 Jason Wong (jayywong92@gmail.com)

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Oct 26, 2023 •
edited
Loading

Onboard Zeke Arany-Lucas 10-25-2023

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Complete 311-Data repo Quickstart

@ryanfchase ryanfchase mentioned this issue Jun 5, 2024
Closed
@ryanfchase
Copy link
Member Author

ryanfchase commented Jun 5, 2024 •
edited by aqandrew
Loading

Onboard: 2024-06-04 Andrew Aquino

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

ryanfchase commented Jun 5, 2024 •
edited by kdow
Loading

Onboard: 2024-06-04 Kelly Downes

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase
Copy link
Member Author

ryanfchase commented Jun 6, 2024 •
edited by DrAcula27
Loading

Onboard: 2024-06-06 Danielle Andrews

For Lead/PM:

  • Slack channel membership
    • #311-data
    • #311-data-engineering
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Update team page on Wiki
  • Share Tokens and Environment Variables

For Member

Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@DrAcula27
Copy link
Member

@ryanfchase what is the 311-Data repo Quickstart? Is there a link I can follow?

@ryanfchase
Copy link
Member Author

@ryanfchase what is the 311-Data repo Quickstart? Is there a link I can follow?

We've just communicated on Slack, but I'll leave this here in case anyone else runs into the same issue. Also making this a link within the onboard template.

311-Data repo Quickstart

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Daniel Torres

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Tracy N

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Jason Wong

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Zeke

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Spencer Meredith

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Romain Yvernes

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Jakob Shavinski

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Robert Schacht

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Nicole Grizzle

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Andre Abad

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Tamera Lazerka

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

Offboard: YYYY-MM-DD Sophia Bui

  • Remove from Google calendar invite
    • You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
    • Choose to remove from "This and all following events"
    • Send the following cancelation message:
      • You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.
    • Wednesday All-Team meeting (ad-hoc)
  • Google Drive
    • 311 Data (ie., project)
      • demote to viewer
  • Roster
    • mark as inactive
  • GitHub
    • demote member to read only team and remove from write team
    • Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues
  • Update team page on WIKI
    • [How to activate-inactivate team members from roster and wiki]

@ryanfchase
Copy link
Member Author

ryanfchase commented Jun 20, 2024 •
edited
Loading

Onboard: 2024-06-19 Palak Pramod Keni

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
    • proof of Website team PR (or other team)
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase

This comment was marked as outdated.

Sign in to view
@ryanfchase
Copy link
Member Author

ryanfchase commented Aug 21, 2024 •
edited by Brandoncyu
Loading

Onboard: 2024-08-21 Brandon Yu

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase
Copy link
Member Author

ryanfchase commented Aug 22, 2024 •
edited by DorianDeptuch
Loading

Onboard: 2024-08-21 Dorian Deptuch

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase

This comment was marked as outdated.

Sign in to view
@ryanfchase
Copy link
Member Author

ryanfchase commented Sep 19, 2024 •
edited
Loading

Onboard: 2024-09-18 Sriya

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
    • Saturday Dev meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase
Copy link
Member Author

ryanfchase commented Nov 19, 2024 •
edited by efrenmarin45
Loading

Onboard: 2024-11-19 Efren Marin

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
    • Saturday Dev meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@ryanfchase
Copy link
Member Author

Onboard: 2024-11-26 Sagun Shrestha

  • Slack channel membership
  • Google Drive
    • Add to drive as Contributor
  • Add to Google calendar invites
    • Wednesday All-Team meeting
    • Saturday Dev meeting
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub
    • Add to write team
    • Add to read team
    • Confirm that their name is on their Github
  • Bookmark Engineering Agenda Issue
  • Visit Open Github Issues
  • Update team page on Wiki
  • Share Tokens and Environment Variables
  • Complete 311-Data repo Quickstart
Roster Required Fields

  • Status: Active (required)
  • Role: whatever name you'd like, but Fullstack Dev is good for consistency (required)
  • Dashboard: M (I think it means member? required)
  • email: required
  • number/texting: optional
  • Slack Name: required
  • SlackID: required (click your slack picture > ellipses > copy member id)
  • everything else: optional

@cottonchristopher cottonchristopher mentioned this issue Jan 31, 2025
Open
@cottonchristopher cottonchristopher added the Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ryanfchase ryanfchase

Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) Feature: GitHub Board/Onboarding Anything to do with team onboarding Role: Frontend React front end work size: 0.25pt Can be done in 1.5 hours
Projects
P: 311: Project Board
Status: Start Here
Milestone
W - Ongoing
Development

No branches or pull requests
5 participants
@edwinjue @ryanfchase @DrAcula27 @MBasil03 @cottonchristopher