Skip to content
Snippets Groups Projects

Offboard Florian Pritz

Offboarding an Arch Linux team member

Details

All roles checklist

  • Remove user email by reverting instructions from docs/email.md.
    • Remove entry in group_vars/all/archusers.yml.
    • Remove SSH pubkey from pubkeys/<username>.pub.
    • Run ansible-playbook -t archusers $(git grep -l archusers playbooks/ | grep -v phrik).
    • Setup forwarding if requested (please add the current date as a comment above the mail address in Postfix's users file).
      • Inform the user of the conditions for forwarding.
        • In most cases we only offer forwarding for 6 months.
        • We will inform the user prior to disabling the forwarding.
        • The forwarding can be extended if there are good reasons for doing so.
  • Set user to inactive in archweb: https://www.archlinux.org/admin/auth/user/
  • Remove member from staff mailing list.
  • Moderate email address on arch-dev-public (find member and moderate).
  • Ask the user to leave #archlinux-staff on Libera Chat and forget the password.
  • Remove staff cloak on Libera Chat (Group contacts). :arrow_right: doesn't have a staff cloak
  • Remove the user from relevant staff groups on Keycloak.
  • Move the user from the public list of their usergroup on archweb (support staff / TUs / devs) to the respective fellow site (fellow support staff / fellow TUs / fellow devs)
  • Remove the user from the Arch Linux GitHub organisation

Main key offboarding checklist

Package Maintainer/Developer offboarding checklist

Edited by Christian Heusel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information