Onboard svartkanin as Support Staff

Onboarding an Arch Linux team member

Details

• Team member username: @svartkanin
• Application: https://lists.archlinux.org/hyperkitty/list/staff@lists.archlinux.org/message/A2KK6BUVB3JUICPTJYC5KNEALB22HOLB/
• Voting result: https://lists.archlinux.org/hyperkitty/list/staff@lists.archlinux.org/message/A2KK6BUVB3JUICPTJYC5KNEALB22HOLB/
• SSH public key:
• Full Name: Daniel Girtler
• Personal e-mail address: <redacted>
• PGP key ID used with personal e-mail address:
• Communication e-mail address: personal

I left some fields blank on purpose, until svartkanin gets a GitLab account so that they can choose themselves which SSH and GPG-key they prefer.

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)

Support staff checklist

• Assign the user to the proper support staff group on Keycloak (added to /Arch Linux Staff/Project Maintainers)
• Add merge permissions on https://github.com/archlinux/archinstall (@torxed will still sign and perform releases, but wants help managing increased workload. If possible, prohibit creating releases/tags on github - but if that's not possible it's fine since @torxed will sign release artifacts and perform that arch packaging updates accordingly)