[tor-bugs] #33108 [Internal Services/Services Admin Team]: How and when should the sysadmin team adopt a service

[Tor Bug Tracker & Wiki]

#33108: How and when should the sysadmin team adopt a service
-------------------------------------------------+-------------------------
 Reporter:  hiro                                 |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Services Admin     |        Version:
  Team                                           |
 Severity:  Normal                               |     Resolution:
 Keywords:                                       |  Actual Points:
Parent ID:  #31243                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by anarcat):

 i'll copy paste what you said in the parent ticket because I think it's
 important:

 > 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.

 I'll also mention this bit we discussed in Stockholm:

     We end up with having to keep hosts and services running long after
 the initial people who wanted it left. We also run some things directly as
 torproject-admin. We should have some list of requirements for things we
 (and also others) run on our infra. This list would include that sw needs
 to have proper releases and installation instructions and procedures, a
 bug tracker, some means to contact upstream, and it needs to run in the
 lastest Debian stable (and when there is a new Debian stable, it needs to
 run on that within a month or three.) There needs to be some commitment of
 maintainership, not only by individuals but by the project/corp, meaning a
 promise of recurring money to keep this service working. It's never just
 about setting up. We really really want at least two people who know and
 maintain each service. Also, this policy should apply not only to incoming
 services, but it should apply to all the things we run and we should
 regularly evaluate whether services meet them.

 Extracted from
 https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/Notes/SysadminTeamRoadmapping

 So maybe this is just a matter of splitting that up in a bullet list and
 adding that to the policy.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33108#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online