review and expand the service/sysadmin distinction

No critical change, but some wording review, splitting in sections and
more links

tsa/doc/admins.creole

@@ -2,30 +2,48 @@
 
 = torproject.org Admins =
 
-The admin team at the Tor project maintains our infrastructure and services.
+The '''admin team''' at the Tor project maintains our infrastructure and
+services.
 
-Within the admin team we have sysadmins and services admins. While the
-distinction between the two might seem blurry, the rule of thumb is that
-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.
+Within the '''admin team''' we have '''system admins''' (or '''sysadmins'''
+or '''TSA''' or '''TPA''') and '''services admins'''. While the distinction
+between the two might seem blurry, the rule of thumb is that 
+'''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.
+Then it's up to the '''service admins''' to deploy and maintain their
+[[services|https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure]]
+(onionoo, atlas, blog, etc) on top of those machines.
 
-For example, "the blog is returning 503 errors" is a service admin thing, i.e. the
-blog service is experiencing a problem. Instead, "the blog doesn't ping" is a sysadmin thing,
-i.e. the machine running the blog service has an issue.
+For example, ''"the blog is returning 503 errors"'' is probably the
+responsability service admin, i.e. the blog service is experiencing a
+problem. Instead, ''"the blog doesn't ping"'' or ''"i cannot open a
+TCP connexion"'' is a sysadmin thing, i.e. the machine running the
+blog service has an issue.
 
-Other tasks that the sysadmins take on are along the lines of "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".
+== More examples ==
 
-The service admins instead are responsible of things like "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".
+Sysadmin tasks:
 
-A list of user facing services and their maintainers can be found at our
-[[infrastructure wiki|https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure]].
+ * installing a Debian package
+ * deploy a firewall rule
+ * add a new user (or a group, or a user to a group, etc)
 
-A list of development machines can be found [[here|https://db.torproject.org/machines.cgi]].
+Service admin tasks:
+
+ * the donation site is not handling credit cards correctly
+ * a video on media.torproject.org is returning 403 because its permissions are wrong
+ * the check.tp.o web service crashed
+
+== Other references ==
+
+A list of user facing services and their maintainers can be found at
+our [[infrastructure
+wiki|https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure]]. Each
+service should have documentation on how it's installed and
+maintained.
+
+A list of development machines can be found
+[[here|https://db.torproject.org/machines.cgi]]. Documentation on
+sysadmin stuff is in *this* wiki, in [[tsa/howto]].