Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
44a0fe52
Verified
Commit
44a0fe52
authored
4 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
fix table of contents to follow policy
parent
99e45689
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tsa/policy/tpa-rfc-2-support.mdwn
+21
-9
21 additions, 9 deletions
tsa/policy/tpa-rfc-2-support.mdwn
with
21 additions
and
9 deletions
tsa/policy/tpa-rfc-2-support.mdwn
+
21
−
9
View file @
44a0fe52
...
...
@@ -3,8 +3,14 @@
Summary: we define three different support levels for services that the sysamins
support
[[!toc levels=2]]
# Background
# Proposal
## Support levels
We consider there are three "support levels" for problems that come up
with services:
...
...
@@ -33,10 +39,7 @@ latter becomes EOL. We do *not* support Debian LTS. It is the
responsability of service admins to upgrade their services to keep up
with the Debian release schedule.
# Support levels
Code red
--------
### Code red
A "code red" is a critical condition that requires immediate
action. It's what we consider an "emergency". Our SLA for those is
...
...
@@ -66,8 +69,7 @@ So, for example, those are *not* code reds for TPA:
* encrypted mailing lists failures
* gitolite refuses connexions
Code yellow
-----------
### Code yellow
A "[code yellow](https://devops.com/code-yellow-when-operations-isnt-perfect/)" is a situation where we are overwhelmed but there
isn't exactly an immediate emergency to deal with. A good introduction
...
...
@@ -90,8 +92,7 @@ Examples of a code yellow include:
* upgrade metrics.tpo to buster in the hope of fixing broken graphs
([ticket 32998](https://bugs.torproject.org/32998))
Routine
-------
### Routine
Routine tasks are normal requests that are not an emergency and can be
processed as part of the normal workflow.
...
...
@@ -106,7 +107,7 @@ Example of routine tasks include:
* security upgrades
* server reboots
# How and when should the sysadmin team adopt a service
#
# How and when should the sysadmin team adopt a service
Over the years we have operated with a "soft" distinction between sysadmins and
services admins as defined in: https://help.torproject.org/tsa/doc/admins/
...
...
@@ -132,3 +133,14 @@ When a service is adopted by the sysadmin team, the sysadmins will make an estim
of costs and resources required to maintain the service over time.
There needs to be some commitment by individuals Tor project contributors and also
by the project that the service will receive funding to keep it working.
# Deadline
TBD.
# Status
This proposal is currently in the `draft` state.
# References
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment