[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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



#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       |    Version:
  Admin Team                                     |
     Severity:  Normal                           |   Keywords:
Actual Points:                                   |  Parent ID:  #31243
       Points:                                   |   Reviewer:
      Sponsor:                                   |
-------------------------------------------------+-------------------------
 Over the years we have operated with a "soft" distinction between sysadmin
 and services admin as defined in:
 https://help.torproject.org/tsa/doc/admins/

 The first problem I see with this distinction is that Tor doesn't have a
 service admin team. There are a few people that end up being responsible
 for a service, for a while. There also used to be a service admin (hiro),
 that is now also a sysadmin and develops the websites among other things.

 It is clear that not all the services that Tor as an organization needs
 can be the responsibility of one person. At the same time it is not ideal
 that people requesting a service support it for a while and then abandon
 it, at which point either becomes the responsibility of someone in the
 sysadmin team.

 The second problem I see with this distinction is that the difference
 between sysadmins and service admin come from a time when Tor had only
 volunteers running its infrastructure and it wasn't expected much more of
 them than just keep the hardware running. This has changed now that Tor
 has grown and needs different services.

 Even though the distinction between what is supported by the sysadmin team
 and what the service admin collective supports is less hard it cannot be
 expected that every orphaned service, or every new service that the org
 need is automatically adopted by the sysadmin team.

 This is an attempt to discuss and formalize how and when a service is
 adopted by the sysadmin team.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33108>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs