[tor-bugs] #31243 [Internal Services/Tor Sysadmin Team]: TPA-RFC-2: define how users get support, what's an emergency and what is supported
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jan 30 15:38:58 UTC 2020
#31243: TPA-RFC-2: define how users get support, what's an emergency and what is
supported
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: anarcat
Type: task | Status:
| needs_revision
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: tparfc | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by hiro):
I think the draft is actually good as a start. I just would like to add
that as the sysadmin team is currently small and there might be specific
situations where a code RED might require more time than expected and as a
organization we need to do an effort in understanding that.
Another observation I have is that we could add to this a procedure
regarding when and if the sysadmin team decide to adopt a service.
E.g. gitlab. If we shutdown tor git at some point that would be where all
our code lives and that worries me a bit because I think that would become
a complex first tier service.
In this procedure we might take into account that if a team request a
service they have to be also responsible for it. I.e. dedicating time and
resources to maintain the service. Sometimes if the service is important
for the organization we should require that at least a few people from the
org step up and take that service as a collective responsibility.
These are just a few observations.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31243#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list