Onboard Konstantin Gizdov as developer
Onboarding an Arch Linux team member
Details
- Team member username: @kgizdov
- Application: N/A
- Voting result: N/A
- SSH public key: N/A
- Full Name: N/A
- Personal e-mail address: N/A
- PGP key ID used with personal e-mail address: N/A
- Communication e-mail address: arch
All roles checklist
The mailing list password can be found in misc/vaults/additional-credentials.vault
.
-
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.
-
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)
- Go to Arch Linux group -> Enter Admin mode -> go to members -> add username as "minimal access"
- Go to Arch Staff group -> Enter Admin mode -> go to members -> add username as "reporter"
Packager onboarding checklist
Developer onboarding checklist
-
Add entry in
group_vars/all/archusers.yml
. -
Add SSH pubkey to
pubkeys/<username>.pub
. -
Run
ansible-playbook -t archusers $(git grep -l archusers playbooks/ | grep -v phrik)
. -
Assign the user to the
Developers
groups on Keycloak. -
Assign the user to the
Developers
group on archlinux.org. - Subscribe communication e-mail address to internal arch-dev mailing list.
- Allow sending from communication e-mail address on arch-dev-public (subscribe and/or find address and remove moderation).