More details in the review process and the install process.

Reference: /n/patches.lsub.org/patch/revfix
Date: Fri Apr 13 18:16:25 CES 2012
Signed-off-by: nemo@lsub.org

--- /PROCESS	Fri Apr 13 18:16:12 2012
+++ /PROCESS	Fri Apr 13 18:16:13 2012
@@ -1,60 +1,78 @@
-Contributers:
-
-If you'd like to contribute to NIX the following process has been
+The NIX following process has been
 created to simplify distributed development.  
 
-To be able to contribute you need to do three things:
-
-1.  Subscribe to the nix-dev mailing list
-http://groups.google.com/group/nix-dev (all development
-correspondance, including codereviews, goes here).
+HOW TO INSTALL:
+--------------
 
-2.  Download the nix distribution
+1a. Download the nix distribution
 (for example:
 	9fs sources.lsub.org
 	cp /n/sources.lsub.org/nix.tgz .
 	...unpack it...
 )
 
-3.  Run it.
+or
+
+1b. Prepare an already downloaded nix (perhaps from googlecode) to
+work with the process.
+
+(for example:
+	9fs sources.lsub.org
+	cp /n/sources.lsub.org/nix/rc/bin/patch/* /rc/bin/patch
+)
+
+2. Run it.
 (for example, after tar zx <nix.tgz, 
 	9vx.OSX -r nix -u glenda
 )
 
-4.  Submit patches using the following process
+HOW TO UPDATE YOUR COPY:
+-----------------------
 
-In nix, run:
+run this:
+	% patch/pull
+	...you'll see patches applied...
 
-patch/create patchname your@mail files-changed-or-removed...
 
-You should see  a mail in nix-dev in a while reporting the new patch.
-All patch reviewers will:
+HOW TO CONTRIBUTE AND REVIEW:
+---------------------------
+1.  Subscribe to the nix-dev mailing list
+http://groups.google.com/group/nix-dev (all development
+correspondance, including codereviews, goes here).
+
+2. Install a copy as explained before.
 
-patch/apply patchname
+3. In nix, run:
 
-...try it...
+	patch/create patchname your@mail files-changed-or-removed...
 
-patch/undo patchname
+You should see  a mail in nix-dev in a while reporting the new patch.
+At this point, patch reviewers would:
 
-and discuss it by mail, following up to the initial mail reporting the new
-patch.
+	patch/apply patchname
 
-Perhaps you'd make more changes to address the issues discussed and,
-again:
+to try the patch, and, when done, run
 
-patch/create patchname your@mail files-changed-or-removed...
+	patch/undo patchname
 
-Here, it's important that you use exactly the same patchname.
+to restore the previous state of affairs.
+
+Reviewing happens by following up to the mail reporting the patch
+creation.
 
-The process continues until the patch has been LGTM'd.
+4. You might want to make changes after reviewing. To do so, you woud:
 
+	patch/create patchname your@mail files-changed-or-removed...
+
+Here, it's important that you use exactly the same patchname.
+The process continues until the patch has been LGTM'd in the mailing list.
 At that point, a maintainer of the nix distribution will
 
-patch/Apply patchname
+	patch/Apply patchname
 
 and, from that point in time, everyone running
 
-patch/pull
+	patch/pull
 
 will get your patch applied.