summaryrefslogtreecommitdiff
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
commit9989cbc6999cef508d0a2a141b8066011789eaa0 (patch)
treedb482c32826eae22a481baf35352e9c30e47947a
parent4f2718d00393626842824b8b31a54c42f7e91c25 (diff)
downloadtor-9989cbc6999cef508d0a2a141b8066011789eaa0.tar.gz
tor-9989cbc6999cef508d0a2a141b8066011789eaa0.zip
r12373@Kushana: nickm | 2007-03-02 13:11:11 -0500
credit PEP as source of Tor process svn:r9712
-rw-r--r--doc/spec/proposals/001-process.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt
index c624dfdbc0..6500e1fe0b 100644
--- a/doc/spec/proposals/001-process.txt
+++ b/doc/spec/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