Onboard Dan Johansen as Junior Package maintainer

Onboarding an Arch Linux team member

Details

• Team member username: @strit (prefers capitalized Strit where possible)
• Application: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/GSZACMOF2T744IPOO2LU3J3QSR5IBF36/
• Voting result: https://aur.archlinux.org/package-maintainer/159
• SSH public key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCz3y1rl9ZwCk3l3pk3HDk9oYs5hxKR/J4Th9Dnx+ifJ+91vfAjoOlCALc5Mi8GcbVWlK91tuvJamsIHk3p+9lqHJe22XU/BpDzrNQRi9yAndbQKwgx9nFKUp69zZ8nhBRcOxVfvICEVsoDcvjh9upY2vMvHiIntlXHLQ7gkArh94JhX9E9jlZ8vQANmxdN486jDI0+UWBXL7tRWiZwJna5VIYo6kT6OzQKah5swrXGKqZxdVKE56Lr/cXIB7E/tTsSK79/Dx9Vy2dVwIagY91VPmFMuHmfDMGt9aBSBJJHLwXMMWiD9V+TcaoGmJWBgpJXX/dvcQWa6XhaopiQ/vj strit@strit-pc
• Full Name: Dan Johansen
• Personal e-mail address: redacted
• PGP key ID used with personal e-mail address: 7A44 3CEE 69B6 B377 7740 E258 084A 7FC0 035B 1D49
• Communication e-mail address: arch

All roles checklist

• Add user mail if TU or developer, or support staff and communication e-mail address is arch.
  • Add new user email as per docs/email.md.
  • Add entry in group_vars/all/archusers.yml.
    • If support staff hosts should be set to mail.archlinux.org.
    • homedir.archlinux.org is also allowed for support staff, but it is opt-in.
  • Add SSH pubkey to pubkeys/<username>.pub.
  • Run ansible-playbook -t archusers $(git grep -l archusers playbooks/ | grep -v phrik).
• Create a new user in archweb. Select the appropriate group membership and allowed repos (if applicable).
• Subscribe communication e-mail address to internal staff mailing list.
• Allow sending from communication e-mail address on arch-dev-public (subscribe and/or find address and remove moderation).
• Give the user access to #archlinux-staff on Libera Chat.
• Give the user a link to our staff services page.
• Replace the Team member username with the @-prefixed username on Gitlab.
• Remove personal information (such as Full Name and Personal e-mail address, as well as the clearsigned representation of this data), remove the description history and make the issue non-confidential.
• Request staff cloak on Libera Chat (Group contacts) cc @archlinux/teams/irc/group-contacts

Package Maintainer/Developer onboarding checklist

• Create an issue in archlinux-keyring using the "New Packager Key" template.
• Assign the user to the correct group in the Arch Linux Staff/Package Maintainer Team/ group on Keycloak.
• Assign the user to the Package Maintainers or Developers group on archlinux.org.
• Subscribe communication e-mail address to internal arch-tu or arch-dev mailing list.
• Give the user access to #archlinux-tu or #archlinux-dev aswell as #archlinux-packaging on Libera Chat.