[tor-bugs] #30881 [Internal Services/Tor Sysadmin Team]: answer the opsreportcard questionnaire, AKA the "limoncelli test"
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Jul 24 20:58:30 UTC 2019
#30881: answer the opsreportcard questionnaire, AKA the "limoncelli test"
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: anarcat
Type: task | Status:
| assigned
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by anarcat):
= 4. Do you have a "policy and procedure" wiki?
http://opsreportcard.com/section/4
Yes, in [https://help.torproject.org/tsa/ help.tpo]. It might become a
GitLab wiki in the future, but that's kind of an implementation detail at
this point. It's good enough for now, but it *is* lacking some
documentation. In particular:
* #30880 - backup / restore procedures
* emergency procedures (disk, machine replacement, intrusion, etc) - see
https://help.torproject.org/tsa/howto/incident-response/ for now
Consider separating the documentation in four categories:
1. tutorials - simple, brainless step-by-step instructions requiring no
or little technical background
2. howtos - more in-depth procedure that may require interpretation
3. reference - how things are built, explaining the complex aspects of
the setup without going into "how to do things", policy decisions and so
on
4. discussion - *why* things are setup this way and *how else* they could
have been built
That separation comes from [https://www.divio.com/blog/documentation/ what
nobody tells you about documentation].
= 5. Do you have a password safe?
http://opsreportcard.com/section/5
Yes, we do.
= 6. Is your team's code kept in a source code control system?
http://opsreportcard.com/section/6
Mostly. There are some ad-hoc scripts here and there, but everything is
being committed into git and/or Puppet as much as possible.
= 7. Does your team use a bug-tracking system for their own code?
Yes, this bug tracker.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30881#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list