Open ryanfchase opened 1 year ago
- 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
For Lead/PM:
#311-data
#311-data-engineering
For Member
- 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 what is the 311-Data repo Quickstart
? Is there a link I can follow?
@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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
- 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
- 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
- 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
- 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
- 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
- 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
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...
Onboard
Offboard
Resources/Instructions