Retire the Tails Sysadmins calendar

The Tails Sysadmins shift process helps the Tails Team know who they should poke or assign issues to for "urgent" matters.

Notes:

• That calendar is the last one left to retire from the old setup
• Neither Tails Sysadmins have been integrated into TPA star rotation nor TPA members have been integrated into Tails shifts yet
• This is part of: TPA-RFC-73

Proposal:

• Create a new calendar for Tails shifts in Tor's Nextcloud
• Move shift info from the old calendar to the new one
• Update documentation
• Inform Tails Team of the change
• Delete the old Tails shifts calendar

@tpo/tpa, any concerns or comments?

EDIT: Updated the proposal as per anarcat's suggestion

added Next Tails labels

assigned to @zen

Retire the current Tails shifts calendar in favor of the "TPA rotations calendar" in Nextcloud

perhaps we should have just a separate calendar for this in TPO's nextcloud? then when we merge the shifts we delete it?

otherwise it's going to add noise to our calendar (and vice-versa)...

otherwise

changed the description

marked this issue as related to #41721 (closed)

changed milestone to %TPA-RFC-73: Tails merge (2024)

changed the description

added Doing label and removed Next label

marked the checklist item Create a new calendar for Tails shifts in Tor's Nextcloud as completed

marked the checklist item Move shift info from the old calendar to the new one as completed

Update documentation

I just did that for the Tails side: https://gitlab.tails.boum.org/tails/tails/-/commit/05524920d68ae0c552c1c8e4375241918f9138a9

For the Tor side, i see that the Tor rotation calendar is not mentioned in TPA-RFC-2: support or other policies, so I think we don't need to explicitly mention the new Tails shifts calendar, assuming we inform the Tails Team and the rest of TPA about the change.

Now I wonder whether we should update TPA-RFC-2: support to mention the existence of "Tails sysadmin shifts", and I was tempted to create a MR until I checked TPA-RFC-1: policy, which says I'd need to create a new RFC to update the old one. If that's the way, I wonder if I should copy text over from TPA-RFC-2 to the new RFC, or provide diffs in the new RFC, which seem more appropriate to track changes. I'd like to confirm what's the expected/best approach before proceeding.

marked the checklist item Inform Tails Team of the change as completed

Hi @zen, FYI the old calendar is also linked from https://gitlab.tails.boum.org/tails/summit/-/wikis/Teams#sysadmins.

marked the checklist item Delete the old Tails shifts calendar as completed

marked the checklist item Update documentation as completed

closed