aboutsummaryrefslogtreecommitdiff
path: root/proposals/001-process.txt
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2009-05-05 15:48:23 +0200
committerSebastian Hahn <sebastian@torproject.org>2009-05-05 17:05:45 +0200
commit2f4ceaf88abb238aa50c176e2a228ba425802633 (patch)
tree7d30eb6c3c2bd09cb09d8fe7180f3a8608ebbc16 /proposals/001-process.txt
parent09c6ef487a20a1553afb58e891f40daacf17367e (diff)
downloadtorspec-2f4ceaf88abb238aa50c176e2a228ba425802633.tar.gz
torspec-2f4ceaf88abb238aa50c176e2a228ba425802633.zip
SVN-specific metadata should no longer be part of a proposal
Update the proposal creation instructions to remove the Version and Last-Modified fields.
Diffstat (limited to 'proposals/001-process.txt')
-rw-r--r--proposals/001-process.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/proposals/001-process.txt b/proposals/001-process.txt
index 3a767b5..5c12d01 100644
--- a/proposals/001-process.txt
+++ b/proposals/001-process.txt
@@ -47,7 +47,7 @@ How to change the specs now:
Like an RFC, every proposal gets a number. Unlike RFCs, proposals can
change over time and keep the same number, until they are finally
accepted or rejected. The history for each proposal
- will be stored in the Tor Subversion repository.
+ will be stored in the Tor repository.
Once a proposal is in the repository, we should discuss and improve it
until we've reached consensus that it's a good idea, and that it's
@@ -82,9 +82,7 @@ How new proposals get added:
What should go in a proposal:
Every proposal should have a header containing these fields:
- Filename, Title, Version, Last-Modified, Author, Created, Status.
- The Version and Last-Modified fields should use the SVN Revision and Date
- tags respectively.
+ Filename, Title, Author, Created, Status.
These fields are optional but recommended:
Target, Implemented-In.