We have offered a arch mail address, for support staff, for over a
year[1][2] and the only difference, is that support staff must only be
granted SSH access to mail.archlinux.org. SSH access to
homedir.archlinux.org is also allowed, but it is opt-in[3].

[1] 7287d6d3 ("archroles: Add support-staff group")
[2] 50c3e0f9 ("archusers: Support restricting users to specific hosts")
[3] e0e52552 ("Allow Alad access to homedir.archlinux.org")

Fix #372

[1] https://lists.archlinux.org/archives/list/staff@lists.archlinux.org/thread/3LFY3OVV4MHXR2WTYDFS6EWNATGFCE3E/

Reaching out to the user is cumbersome, especially if the user is being
offboarded due to inactivity.

Fixes: bb000824 ("mailman: Second batch of mailman3 migrated lists")

There is no need to run all playbooks for this.

Kristian Klausen authored 3 years ago and Jelle van der Waa committed 3 years ago

We are usually setting up forwarding when offboarding, so it should be
documented, also we shouldn't keep the forwards around forever.

Only run it for te required playbooks, exclude the phrik playbook as we
only need it to give demize access to phrik and only running archusers
removes demize from the phrik group. Seperate bug which should be
fixed...

Kristian Klausen authored 3 years ago and Jelle van der Waa committed 3 years ago

[1] https://archlinux.org/news/move-of-official-irc-channels-to-liberachat/

.gitlab/issue_templates/Offboarding.md:
Add more specific information for developer offboarding (e.g. also
remove from arch-dev mailing list).
Add more specific information on which templates to choose and where to
open a ticket for signing key removal.

Levente Polyak authored 4 years ago and Sven-Hendrik Haase committed 3 years ago

Strictly speaking this is not a devops duty, but I believe this is
currently the best place to ensure we won't ever forget to create a
keyring revocation ticket for an offboarded former staff.

Jelle van der Waa authored 4 years ago and Jelle van der Waa committed 4 years ago

Add the relevant mailing list subscriptions for all, Devops, TU and
Developer specific mailing lists.