Onboard tcanabrava as junior package maintainer

Onboarding an Arch Linux team member

Details

• Team member username: @tcanabrava
• Application: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/BR63Z2CBPSZYSDMZ47Z7PV2VOQ5VK3X7/
• Voting result: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/JHSCYJLXKX2JJQF5DA3UCCGBUSCRCTMH/
• SSH public key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCsYxVUGkLvZXuXCMPC4FtXuqqENy+SRt0BNiGiiWDC/gaKNJq+HRHgKo3NPf9zpdjA/QTt2k/Eu+RMIy/ogb+LRiFwPoXpW17oUuuaO6J1MPikZ7MIn08/pTWcwDLOl5qdgGMPQQVSPIyYUGPtQvvL9/MDkIJSWup1+VPTVCo+aHEwzDd/2ojyjJxq3wLHEKjhhY6OH7G9Qo5NqWbTdjTG0XUuNwvPnKGZcFy+ldOOLTPWDF38J9cUwyC/F1g8VrV+dhNtndI0lOk5Zs+cEhu6X7zU+qN/o2DYMKg78eq8oiCogxXshe4I4iEVvLJGRP+4dzY64JYa0cErkktwE6tHY3qpBJsTMYVwcMPg2gdHu4O5EJiwcC+xntPrUW3h6hZyRYAzeXYZe+EmXaZ8DQtfCajFkpt3AumFJ46Q7YKCqiEiHkWYc+AnuAmLqOdebknRm8JXFPF4A4jzHjjSo2Yq7WEwpacvWHarJowIJJ8TQv8XRPskNacBTzFTJTRzWM7tOrsJ4Fb3TtN2UT3H7FVpkpbstPMy+n8Ed9s15IShz6pzlcwDXOh77bN90yimQUcsLEO/YgKmIp5xe2ol0OCeKtoAes96Ai1HheCUOg3b3+Tn6ka7/y4UOpQeHfwM5iwOT73A8GR4p26IHV31Ezb2Ky4qFmxG/b9xDctga2LfxQ== tcanabrava@archlinux.org
• Full Name: redacted
• Personal e-mail address: redacted
• PGP key ID used with personal e-mail address: redacted
• Communication e-mail address: personal

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) (not relevant as he uses Matrix)

TU/Developer onboarding checklist

• Create an issue in archlinux-keyring using the "New Packager Key" template (archlinux-keyring#242 (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.