mirror/infrastructure
1
1
Fork 0
mirror of https://gitlab.archlinux.org/archlinux/infrastructure.git synced 2026-08-06 12:12:58 +02:00
Code Issues Activity
Files
update-buildbtw-wireguard
infrastructure/.gitlab/issue_templates/Onboarding.md
T
Robin Candau b6f9cba839 Update email doc and onboarding issue template 
email doc:

- Fix a typo (missing slash in username's homedir path).
- Add procedure to promote a postorius account to supersuser (a
  superuser account is required to subscribe onboarded staff to mailing
  lists).

onboarding issue template:

- Replace leftover mentions of "trusted user / TU" by "package maintainer"
  (except for the arch-tu ML and #archlinux-tu IRC channel, which are actually
  named that way).
- Move the "Add new user mail" entry after the user creation entry in the
  checklist (as the user needs to be created before being able to fully follow
  the related procedure).
- Add a mention that we should use our own postorius account to
  subscribe onboarded staff to the mailing lists (we don't have a
  generic admin account) as well as a mention that said account should
  be superuser to do so (including a link to the new related procedure
  about how to promote a postorius account to superuser).
- Add a link to the Keycloak admin panel / realm, from where onboarded
  staff account's should be updated.
2026-05-28 08:20:01 +02:00

5.9 KiB
Raw Permalink Blame History

/confidential

Onboarding an Arch Linux team member

Details

  • Team member username:
  • Application:
  • Voting result:
  • SSH public key:
  • Full Name:
  • Personal e-mail address:
  • PGP key ID used with personal e-mail address:
  • Communication e-mail address: [arch, personal]

All roles checklist

  • Add user mail if package maintainer or developer, or support staff and communication e-mail address is arch.
    • 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).
    • Add new user email as per docs/email.md.
  • 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 (using your own postorious account, which needs to be superuser).
  • 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

Main key onboarding checklist

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 (using your own postorious account, which needs to be superuser).
  • Give the user access to #archlinux-tu or #archlinux-dev aswell as #archlinux-packaging on Libera Chat.

Support staff checklist

  • Assign the user to the proper support staff group on Keycloak.

DevOps onboarding checklist

Wiki Administrator checklist

View Git Blame Copy Permalink