"In the Tor Project system Administrator's team (colloquially known as TPA), we've recently changed how we take decisions, which means you'll get clearer communications from us about upcoming changes or targeted questions about a proposal."
"Context: What is the issue that we're seeing that is motivating this decision or change? Decision: What is the change that we're proposing and/or doing? Consequences: What becomes easier or more difficult to do because of this change? More Information (optional): What else should we know? For larger projects, consider including a timeline and cost estimate, along with the impact on affected users (perhaps including existing Personas). Generally, this includes a short evaluation of alternatives considered. Metadata: status, decision date, decision makers, consulted, informed users, and link to a discussion forum"
"We had traditionally been using a "RFC" ("Request For Comments") process and have recently switched to "ADR" ("Architecture Decision Record")."
TPA replaced the RFC decision process with ADRs to produce clearer communications and targeted questions about proposals. ADR includes a simpler template, a simpler process, and separate communication guidelines. The TPA ADR template uses five headings: Context, Decision, Consequences, More Information (optional), and Metadata with fields like status, decision date, decision makers, consulted, informed users, and discussion links. The prior RFC template had seventeen headings and produced longer documents. The ADR format shortens records so they are easier to read and digest at a glance. The process currently applies only to TPA.
Read at Anarc
Unable to calculate read time
Collection
[
|
...
]