How and when should the sysadmin team adopt a service
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.