Skip to content
GitLab
  • Explore
  • Sign in
  • The Tor Project
  • TPA
  • TPA teamTPA team
  • Wiki
  • Policy
  • tpa rfc 2 support

tpa rfc 2 support · Changes

Page history
TPA-RFC-12: reformulate the triage policy authored Sep 14, 2021 by anarcat's avatar anarcat
We had nothing about the star of the weeks, which was informally
specified. This clarifies that it's responsible for routine tasks, but
also takes care of clarifying the ticket workflow in the gitlab policy.

Closes: #40382
Hide whitespace changes
Inline Side-by-side
policy/tpa-rfc-2-support.md
View page @ e45afcf3
......@@ -205,6 +205,25 @@ Example of routine tasks include:
* security upgrades
* server reboots
### Triage
One member of TPA is assigned the "Star of the weeks" every other
week. The Star is responsible for triage, which occurs in GitLab, as
per the [TPA-RFC-5: GitLab migration](policy/tpa-rfc-5-gitlab) policy.
But the Star also handles routine tasks and interruptions. In that
sense, it acts as a "[interruption shield](https://queue.acm.org/detail.cfm?id=1922541)" by taking care of
small, distracting tasks to let others focus on more long-term
projects.
In that sense, the Star takes care of the above [routine tasks](#routine)
like server reboots, security upgrades and spam runs. It is also
expected to keep an eye on the monitoring system and organise
[incident response](howto/incident-response) when a more serious issue occurs. It is *NOT*
responsible for fixing *all* the issues and it is expected the Star
will assign work or ask for help in an emergency or if it is
overwhelmed.
## Supported services
Services supported by TPA must fulfill the following criteria:
......
Clone repository

Quick links

  • Support
  • User documentation
  • Sysadmin how-to's
  • Service list
  • Machine list
  • Policies
  • Meetings
  • Roadmaps