Onboarding Jenny Wong

[jmunroe]

(Starting from the generic onboarding template -- not all of these might apply for a Technical Content Developer and will be adjusted as we work through them)

• Onboarding champion: @jmunroe
• New person's name: Jenny Wong
• New person's GitHub handle: @jnywong

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

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](https://2i2c.freshdesk.com/a/admin/groups
• Add to propoer 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

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 Steward 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! 🎉

[jmunroe]

Created a Google Workspace account and invited Jenny to the 2i2c-org GitHub org

[jmunroe]

Get member's bitwarden account

Looks like to add bitwarden user you invite them by email address, so I don't think "bitwarden account" is needed.

Invited [email protected] to the 2i2c org on Bitwarden

[jmunroe]

I don't think this are needed for non-engineering roles:

Get member's NameCheap.com account
Get member's PagerDuty account

[jmunroe]

Added to FreshDesk (since there is a lot of historical information there that I believe Jenny will need to access to)

[jmunroe]

Looking at the our RTD sites now:

• Hub Service Guide: https://docs.2i2c.org/ (RTD link)
• Infrastructure Guide: https://infrastructure.2i2c.org/ (RTD project link)
• Team Compass: https://team-compass.2i2c.org/ (RTD project link)

I doesn't look like we have been added our whole team to these projects.

@choldgraf -- you appear to have admin access to all of these: could you please add me (jmunroe) as a maintainer so that I can in turn add Jenny?

[jmunroe]

All the links to the Team Compass in this GitHub issue template seem broken.

• We need to change the prefixes https://team-compass.2i2c.org/en/latest/ to https://compass.2i2c.org/ throughout the GH template. (See Update team compass URLs in onboarding GH template #776 )

[choldgraf]

@jmunroe invites sent to each of those RTD pages!

[jmunroe]

RTD invites and quay.io invites done.

[jmunroe]

I've added a stub in 2i2c-org/2i2c-org.github.io#189

@jnywong, please add a bio / update the profile image used / set your socials as you like by editing content/authors/jenny-wong on https://github.com/2i2c-org/2i2c-org.github.io

[jnywong]

Stub updated and 2i2c-org/2i2c-org.github.io#193 opened.

[jnywong]

Created PR to update template issue with a prompt to edit helm chart for 2i2c hubs for the following item:

• Add to 2i2c hubs as an admin

[jnywong]

Closing this issue as I consider my onboarding is done!