From: Sebastian Hahn Date: Tue, 5 May 2009 13:48:23 +0000 (+0200) Subject: SVN-specific metadata should no longer be part of a proposal X-Git-Tag: tor-0.2.2.1-alpha~160 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d0cb5e5b0bfa55ac7e3ec4f28cdea309aaeefd51;p=thirdparty%2Ftor.git SVN-specific metadata should no longer be part of a proposal Update the proposal creation instructions to remove the Version and Last-Modified fields. --- diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt index 3a767b5fa4..5c12d01648 100644 --- a/doc/spec/proposals/001-process.txt +++ b/doc/spec/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.