Onboarding Angus Hollands

[choldgraf]

• Onboarding champion: @choldgraf
• New person's name: Angus Hollands
• New person's GitHub handle: @agoose77

Onboarding checklist

The Onboarding champion should follow the checklist below to onboard a new team member. Don't hesitate to delegate some actions to others (e.g. if another person needs to give access to an account because you aren't able to).

First steps

• Send them a welcome e-mail to introduce yourself and mention that you'll be onboarding them.
• Point them to our onboarding documentation

Accounts

Create new accounts and share their account name:

• Get member's GitHub.com account
• Get member's ReadTheDocs.org account
• Get member's Quay.io account
• Get member's NameCheap.com account
• Get member's PagerDuty account
• Get member's bitwarden account
• Get member's Zoom account
• Get member's Freshdesk account

Create 2i2c accounts and add to team accounts:

• Create a @2i2c.org Google account for them
  • Note that this requires access to the Admin Panel, a permission held by any 2i2c team lead
• Add them to the proper Google group in our Google Admin space.
• Add to the proper 2i2c GitHub teams
• Add to the proper Slack groups
• Add to the proper FreshDesk group
• Add to proper PagerDuty Users group
• Add to our bitwarden organization and add to "Default collection"

Communication

• Send them a link to the 2i2c Team Compass and its Team Operations section
• Send them a link to the 2i2c calendars and meetings
• Send them a link to the 2i2c Team Google Drive
• Schedule an onboarding meeting for after they've read through the docs

Documentation

• Grant appropriate permissions on ReadTheDocs projects
  • https://readthedocs.org/dashboard/2i2c-pilot-hubs/users/
  • https://readthedocs.org/dashboard/2i2c-team-compass/users/
  • https://readthedocs.org/dashboard/2i2c-pilot-documentation/users/

Cloud engineering permissions

Note

@choldgraf doesn't think this is necessary since Angus is focusing on executable books development, not cloud infrastructure, but somebody please correct him if he's wrong.

This is only relevant for others that are joining our Engineering team.

• Add to 2i2c hubs as an admin

• Add to appropriate GCP organizations and projects

  • Organization 2i2c.org's admin group
  • Organization 2i2c.orgs engineering group
  • Outside-organization project for cloudbank
  • Outside-organization project for meom-ige
  • Outside-organization project for callysto
  • (optional) Outside-organization project for pangeo-hubs
    • An agreement has to be signed first, and they require a copy of our passports, see https://github.com/2i2c-org/meta/issues/247

• Add to appropriate AWS projects

  • Management account 2i2c-sandbox (Grants SSO access at https://2i2c.awsapps.com/start#/)
  • Outside-SSO account carbonplan
  • Outside-SSO account openscapes
  • Outside-SSO account nasa-veda
    • An agreement has to be signed first, see https://github.com/2i2c-org/leads/issues/104

• Add to appropriate Azure projects

  • Outside-organization subscription for utoronto see Get all 2i2c engineers access to UToronto Azure portal #386

• Add to quay.io 2i2c team

• NameCheap administration privileges to 2i2c.org and 2i2c.cloud

Roles

• Onboard into the Support Triager Role

External

• Add to 2i2c website
• Celebrate their arrival on social media! (Twitter, Mastodon, LinkedIn)

Wrap up

• Have a one-on-one with the new team member to answer any questions they may have
• Announce in the #general Slack channel about our new team member
• Celebrate, they are now onboarded! 🎉

[agoose77]

• @choldgraf my RTD username is agoose77.
• I've opened a PR to update the website
• I don't have zoom or any of the other accounts. Are these all required in my instance?