Define the work of the Mirrors Team and reconsider who should do it

Originally created by @sajolida on #16930 (Redmine)

• Context
• Primary responsibilities
• Who could do this
  • Non-technical requirements
  • Technical skills
• To Do

Context

If we keep this team, we should formalize its responsibilities. And if we want another, existing team to take over, they'll want to know what the job is about anyway.

Thanks to Rethink how we monitor and maintain our mirror ... (#19334 - closed), the volume and nature of the work has changed:

• Much less incoming email to process: only once a week.
• Most of the work is not time-sensitive anymore.

Primary responsibilities

Ensure our mirror pool adequately serves the needs of its stakeholders: our users and release managers. Their needs are described in more details on #19334 (closed).

Practically speaking, this means:

• Process offers of new mirrors (check compliance with our requirements, test, add to mirrors.json… or gently decline).
• Identify broken web servers (via weekly email report). If Mirrorbits did not spot the problem: disable them in mirrors.json, reach out to mirror operator (this is the only time-sensitive part of the job); re-enable once fixed.
• Identify slow mirrors (via weekly email report), remove them from mirrors.json, and ask mirror operator to stop pulling via rsync.
• Identify general health problems (not clear how; #19540 (closed) is meant to solve this).

Who could do this

Non-technical requirements

• Needs to be done by folks with significant and reliable commitment, i.e. Core Workers.
• It's so little work that it should not impact significantly any CW's capacity… and is probably not worth discussing for ages
• 1 person is enough:
  • Time-sensitive work is required only in rare cases, and we would be very unlucky if that happened precisely when the maintainer is AFK for an extended period.
  • They can of course ask advice or support to other Tails folk when needed :)

Technical skills

• editing JSON on GitLab
• bonus: a good understanding of how the mirror pool is used (currently only FT and UX have this, but presumably others could learn)

To Do

• Update https://gitlab.tails.boum.org/tails/summit/-/wikis/Teams
• Remove previous members from Mirrors team (access, credentials)
  • Remove intrigeri
  • Remove emmapeel
• Fix documentation in mirrors.git to get rid of mentions to the dispatcher code.
• Update sysadmins role description and doc to add mirrors maintenance
• Inform about the deprecation of the Mirrors Team in favor of Sysadmins.
• Archive tails/mirror-pool-dispatcher>
• Go through the whole setup once and flag next steps
• Consider disabling mirrors that have been flagged as slow recently
• Consider moving documentation to more appropriate places
• Consider ditching mirrors.git (DNS config).
• Consider ways to minimize the need for manual intervention