Skip to content
Snippets Groups Projects
Code owners
Assign users and groups as approvers for specific file changes. Learn more.

Offboarding an Arch Linux team member

Details

  • Team member username:
  • Currently held roles:
  • Removal request:
    • Voting result:

All roles checklist

  • Remove user email by reverting instructions from docs/email.md.
    • Setup forwarding if desired (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
  • Ask the user to leave #archlinux-staff on Libera Chat and forget the password
  • Remove staff cloak on Libera Chat (Group contacts)

TU/Developer offboarding checklist

  • 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).
  • Remove the user from the Trusted Users/Developers groups on Keycloak.
  • Moderate email address on arch-dev-public (find member and moderate)
  • Remove member from arch-tu and/or arch-dev mailing lists
  • Create issue in archlinux-keyring (choose "Remove Packager Key" and/or "Remove Main Key" template)

DevOps offboarding checklist

  • Remove entries in group_vars/all/root_access.yml.
  • Run ansible-playbook -t root_ssh playbooks/*.yml.
  • Run ansible-playbook playbooks/hetzner_storagebox.yml playbooks/rsync.net.yml.
  • Remove the user from the DevOps group on Keycloak.
  • Remove member from arch-devops-private mailing lists
  • Remove pubkey from Hetzner's key management

Wiki Administrator checklist