Onboarding Lahwaacz

Onboarding an Arch Linux team member

Details

• Team member username: @lahwaacz
• Application: https://lists.archlinux.org/hyperkitty/list/aur-general@lists.archlinux.org/thread/A52KAVOYSRNVE2GDJN5ENV67Z4Y3S2PP/
• Voting result: https://lists.archlinux.org/hyperkitty/list/aur-general@lists.archlinux.org/message/QE24VOLL6BX26CPWQIWLYEREVU34ECLI/
• SSH public key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKPAJokquWeVyMNd7am5gtJhwoVUHNtm/ydLiOjKKQTG
• Full Name: Jakub Klinkovský
• Personal e-mail address: existing user
• PGP key ID used with personal e-mail address: should already exist
• Communication e-mail address: [arch, personal] arch (already in use)

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 (the mentioned information is already public).
• Request staff cloak on Libera Chat (Group contacts)

TU/Developer onboarding checklist

• Create an issue in archlinux-keyring using the "New Packager Key" template (archlinux-keyring#252 (closed)).
• Assign the user to the Trusted Users or Developers group on Keycloak.
• Assign the user to the Trusted Users 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 on Libera Chat (the user has access to #archlinux-packaging, it is unclear if #archlinux-tu is still used)

jakub.txt.asc