aboutsummaryrefslogtreecommitdiff
path: root/proposals/001-process.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-03-02 20:00:30 +0000
committerNick Mathewson <nickm@torproject.org>2007-03-02 20:00:30 +0000
commit0ae35cc6618adf800174da58121ee812f6b4d1c6 (patch)
tree8bac9bff8a39a2cb167bdf07b77dafc66ff069ce /proposals/001-process.txt
parent5fa805451f08155e92c4293e71847d2f9298aed1 (diff)
downloadtorspec-0ae35cc6618adf800174da58121ee812f6b4d1c6.tar.gz
torspec-0ae35cc6618adf800174da58121ee812f6b4d1c6.zip
r12373@Kushana: nickm | 2007-03-02 13:11:11 -0500
credit PEP as source of Tor process svn:r9712
Diffstat (limited to 'proposals/001-process.txt')
-rw-r--r--proposals/001-process.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/proposals/001-process.txt b/proposals/001-process.txt
index c624dfd..6500e1f 100644
--- a/proposals/001-process.txt
+++ b/proposals/001-process.txt
@@ -56,6 +56,10 @@ How to change the specs now:
remain the canonical documentation for the Tor protocol: no proposal is
ever the canonical documentation for an implemented feature.
+ (This process is pretty similar to the Python Enhancement Process, with
+ the major exception that Tor proposals get re-integrated into the specs
+ after implementation, whereas PEPs _become_ the new spec.)
+
{It's still okay to make small changes directly to the spec if the code
can be
written more or less immediately, or cosmetic changes if no code change is