SF Onboarding Week, May 20 2019

Checklist

[x] Several weeks before: send out an email to the participants reminding them that they are signed up and to clear their calendars. You can find a template in FACILITATING.md.
- [x] You will be communicating with these folks a lot. I find it helpful to save a copy/pasteable list of their names here:
- Kim Bassett <kbassett@pivotal.io>, Samia Nneji <snneji@pivotal.io>, Brian Upton <bupton@pivotal.io>, James Pollard <jpollard@pivotal.io>, Sarah Weinstein <sweinstein@pivotal.io>, Ramia Davis <radavis@pivotal.io>, Brendan Winter <bwinter@pivotal.io>
- kbassett@pivotal.io,snneji@pivotal.io,bupton@pivotal.io,jpollard@pivotal.io,sweinstein@pivotal.io,radavis@pivotal.io
[x] The week before: send out an email to each of the participants. You can find a template in FACILITATING.md.
[x] Get a Zoom room setup for remote participants. {} (Make sure to include this on your calendar invites.)

[x] Schedule a welcome/orientation session (1hr at 9:30 Monday morning). Discuss the goals of the week and prime the participants to consider what they'd like to get out of Onboarding week.
[x] Schedule daily standup (15min at 9:15, starting Tuesday).
[x] Schedule afternoon check in (30min at 1:30).
[x] Schedule retro at the end of the week (1hr at 4:00), include link to retro board: https://retros.cfapps.io/retros/onboarding-sf (pw: onboarding-sf (pls don't change it))
[x] Schedule any sessions that you know the group would be interested in -- for example, BOSH boxes and lines.
- [x] In SF we have a list of prior speakers
[x] In the past, non Engineers have appreciated it when we blocked out the entire days of onbaording. This is especially helpful if done a few weeks in advance; so, they have time to move meetings and avoid having new ones scheduled in the first place.

[x] Make sure you have GCP projects set up.
- [x] In SF, we use:
- cf-sf-onboarding-env-1
- cf-sf-onboarding-env-2
- cf-sf-onboarding-env-3
- [x] Otherwise, Fill out this form to create new environments.
[x] Clean up any VMs, networks, and DNS records that may have been leftover from the previous week
[x] Add all participants as owners to each of the GCP projects.
- [x] In SF:
- IAM for env-1
- IAM for env-2
- IAM for env-3
[x] If your CF on-boarding will include the GCP track (gcp tracker label / the oss build) then ensure participants have access to the CF-Onboarding-dns project in GCP (for DNS propagation). IAM for DNS

[x] Make sure you have Tracker projects prepared.
- [x] In SF, we use the following trackers projects:
- Pair 1
- Pair 2
- Pair 3
[x] Add all participants as members to each of the tracker projects.
[x] Delete everything from the tracker projects.
[x] Build the tracker back log csv
- [x] SF FACILITATORS: Run ./build oss from the onboarding project, this will generate onboarding-tracker.csv
  - Note: you need docker installed brew cask install docker
    - To get the command line tool to show up you may have to first start docker via Spotlight Search
    - If docker gives you this error: failed to dial gRPC: unable to upgrade to h2c, received 502 context canceled
    - In docker settings: enable experimental, restart docker, disable experiment and restart again.
[x] SF FACILITATORS: Import the CSV into each Tracker project (Taskbar > More > Import CSV > Choose File)
[x] ~~Move all stories from icebox to backlog.~~ I have not been doing this. Participants can use their own backlog management!

[x] Give all participants access to the shared LastPass folder:
- LastPass > Sharing Center > Shared-CF SF Onboarding > Manage > Invite Users

[ ] Optionally get a floater laptop to help pairs split up when reading docs.
[ ] Record any issues you have with this process so we can update this checklist.