[tor-bugs] #24497 [Webpages/Website]: Improve documentation for tor relay operators

[Tor Bug Tracker & Wiki]

#24497: Improve documentation for tor relay operators
------------------------------+------------------------
 Reporter:  arthuredelstein   |          Owner:  (none)
     Type:  defect            |         Status:  new
 Priority:  Medium            |      Milestone:
Component:  Webpages/Website  |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:  ux-team           |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
------------------------------+------------------------

Comment (by cypherpunks):

 (context: Alison sent an email on this topic, this was my reply - so it is
 documented here)
 -----------

 I'll paste this email to #24497 once trac works again.


 thanks for your email and pushing this forward.

 Unfortunately trac appears to have some troubles currently
 ("Service Unavailable" every now and then).

 Since no one objected so far (since 2017-12-19) I'll proceed with what I
 proposed on #24497.
 (please speak up of you disagree with anything proposed on #24497)

 In addition:

 - lets not depend on: (which is currently the case)
 https://www.torproject.org/docs/debian.html.en
 I assume the new content will replace - not extend - it.

 - What is actually used to build/run community.tpo? (some known
 platform/cms?)
 (I'm asking to find out if it would support that sources.list "generator")
 And does your timeline (blog post in first week of 2018) mean
 community.tpo is online by then?

 Just a short info on what I'll take care of - from the todo list (and
 complete before 2018-01-04
 likely earlier):
 >     add OS comparison table
 >     add DNS on exit relays
 >     add setting up outage notifications
 >     add
 https://trac.torproject.org/projects/tor/wiki/OperatorsTips/DebianUbuntuUpdates


 >     add Puppet to configuration management [we already have an Ansible
 role; is it necessary to have both?]

 irl wanted to have more than one configuration management and I agree with
 him but only if it is maintained,
 for at least 2 more years.

 Ideally some tpo person would review these external contributions, but I
 doubt that will happen
 before you plan to publish.



 >     clarify meaning of Tor vs tor (near the top), and check this doc for
 consistency

 I used "tor" where I was referring to the program and Tor everywhere else.

 >     make page read-only; accept changes via ticket
 Who will take care of implementing changes after you turned into a read-
 only page?
 (I'll certainly be someone that proposes updates)



 Don't feel you have to reply to this email, lets keep the discussion on
 #24497.

 -------
 This email got two replies (one from Arthur and Alison). I'll let them
 decide themselves if they want to paste their replies here as well.

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