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 ([email protected])

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.

[jnywong]

I've done the FreshDesk deactivation whilst I was looking at it today.

[yuvipanda]

@aprilmj I think I've added you to the appropriate group in google workspaces that lets you do google workspace things with respect to user management in https://admin.google.com.

[aprilmj]

@yuvipanda I can deactivate him as a user in Google (thank you!), but don't seem to be able to edit the department settings (we only have the one department, 2i2c.org).

[aprilmj]

I've removed Damián from our private team Slack channels, which also turned up that Davina was still in some, as is Sean Morris. Who is Sean, and should he still be in the private Slack channels?

PS doing this process in Slack is making me wish we'd implemented the suggestions in https://github.com/2i2c-org/meta/issues/1556

[GeorgianaElena]

I removed Damián from GitHub team and checked ReadTheDocs membership. I also tried to remove it from pagerduty, but he is Base Role:Account Owner and couldn't

[damianavila]

Hey folks, let me know if you need any help from me on this one.
FYI, after checking, I am still owner in the 2i2c GH organization, you probably need to make me just a member?

Cheers.

[Gman0909]

@aprilmj could you please update this and transfer it to a more appropriate board?

[aprilmj]

I've moved to to the Ops board but it's blocked on @yuvipanda or someone else with the permissions needed to help Damián exit GitHub and other things on this list.

[damianavila]

someone else with the permissions needed to help Damián exit GitHub and other things on this list.

I was eefectively removed AFAIK.

Btw, folks, is there any way to move https://github.com/2i2c-org/meta/issues/1398 out of meta? I can not access it anymore and I think that discussion would benefit from my feedback. Thanks!

[aprilmj]

@jmunroe will take the last step on the website