Officially Departing Damián Avila

[aprilmj]

We started the process of offboarding Damián in August 2024, but didn't open an issue to track that we'd completed every task at that point. The majority of his offboarding process has already happened. We may need to refine this task more.

Departing person's name: Damián Avila
Departing person's manager: @choldgraf

Departure checklist

The manager should follow the checklist below to offboard a departing team member after exit.
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

• Schedule a 2i2c offboarding meeting
• Arrange with CS&S HR team to do formal exit interview (hr@codeforscience.org)

Accounts

Document accounts:

• 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

** After Departure**

Remove 2i2c accounts and remove from team accounts:

• Deactivate a @2i2c.org Google account for them

  • Note that this requires access to the Admin Panel, a permission held by any 2i2c team lead

• Remove them from the proper Google group in our Google Admin space.

• Remove them from 2i2c GitHub teams

• Remove them from Slack groups

  • Note that as 2i2c slack is open check to see if they are going to continue to be part of broader 2i2c community and their slack email address is changed

• Remove from the proper FreshDesk group

• Remove from PagerDuty Users group

• Remove from our bitwarden organization and remove from "Default collection"

• Role removal

  • File and complete a "Remove a team member from the Support Triager Team Role, calendar, and rotation" issue

Documentation

• Revoke 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 leaving our Engineering team.

• Remove from 2i2c hubs as an admin

• Remove from 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

• Remove from 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

• Remove from appropriate Azure projects

  • Outside-organization utoronto contact them for removal

• Remove from quay.io 2i2c team

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

External

• Remove from 2i2c website

[aprilmj]

@yuvipanda when you're available, can you review the engineering section of this and make sure we've appropriately removed Damian's access? Please delegate as appropriate.