Document the distinction between sys admin and service admin
Our sysadmins do not maintain every service that we offer. Rather, they maintain the underlying computers -- make sure they get package updates, make sure they stay on the network, etc. Then it's up to the service admins to keep their services (onionoo, atlas, blog, etc) working as intended.
But this is a confusing and sometimes blurry distinction.
I think it would be useful to try to document this distinction on a page at https://help.torproject.org/tsa/.
Maybe one useful way forward would be to include some examples on either side of the line?
For example, "the blog is returning 503 errors" is a service admin thing, whereas "the blog doesn't ping" is a sysadmin thing. Other things on the sysadmin side are "I need this deb installed" and "there's a firewall rule blocking my packets to that other Tor machine" and "I need this userid added to that group". Other things on the service admin side are "the donation machine is not handling credit cards correctly", "a video on media.torproject.org is returning 403 because its permissions are set wrong", and "the check.tp.o webserver crashed".
Now, I think this is complicated more because some of the services are ones that the sysadmins decided they could take care of -- like the main websites served by the www rotation of servers (if this is true).
See https://db.torproject.org/machines.cgi for a list of computers, and I bet there's a page on trac with a list of services and maintainers for them, but I don't know where to find it.
weasel, qbi, is anything written about this topic already?