aboutsummaryrefslogtreecommitdiff
path: root/proposals/001-process.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-07-14 20:44:44 +0000
committerNick Mathewson <nickm@torproject.org>2008-07-14 20:44:44 +0000
commit2ba4cf2b5bc4dacd712409dbc8f31ce22a4b4ab2 (patch)
treebc74dca89a6c38ae635c4e440f6193089a53d5f7 /proposals/001-process.txt
parent5562fe4baac88416e0eb29a6863ff47fec86094a (diff)
downloadtorspec-2ba4cf2b5bc4dacd712409dbc8f31ce22a4b4ab2.tar.gz
torspec-2ba4cf2b5bc4dacd712409dbc8f31ce22a4b4ab2.zip
For some open and accepted proposals, note their target versions.
svn:r15904
Diffstat (limited to 'proposals/001-process.txt')
-rw-r--r--proposals/001-process.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/proposals/001-process.txt b/proposals/001-process.txt
index e23f7c9..3a767b5 100644
--- a/proposals/001-process.txt
+++ b/proposals/001-process.txt
@@ -86,6 +86,13 @@ What should go in a proposal:
The Version and Last-Modified fields should use the SVN Revision and Date
tags respectively.
+ These fields are optional but recommended:
+ Target, Implemented-In.
+ The Target field should describe which version the proposal is hoped to be
+ implemented in (if it's Open or Accepted). The Implemented-In field
+ should describe which version the proposal was implemented in (if it's
+ Finished or Closed).
+
The body of the proposal should start with an Overview section explaining
what the proposal's about, what it does, and about what state it's in.