A unified diff of the changes Ian made to reflect people's feedback on
draft 3 of his proposed disputes resolution document is MIME-attached.

The changes appear to be:

+ changes to the list of parties of whom the document claims to be
  representative;
+ stylistic alterations to the paragraph on authoritative documentation

-- 
G. Branden Robinson                |     If God had intended for man to go
Debian GNU/Linux                   |     about naked, we would have been
[EMAIL PROTECTED]                 |     born that way.
http://people.debian.org/~branden/ |
--- iwj_draft3  2002-11-06 12:08:06.000000000 -0500
+++ iwj_draft4  2002-11-06 12:07:59.000000000 -0500
@@ -1,8 +1,6 @@
                    DISPUTES BETWEEN DEVELOPERS
 
-A *DRAFT* joint recommendation of the the Technical Committee, the
-Project Leader and the Bug Tracking System Administrators.
-
+A *DRAFT* recommendation by the Technical Committee. 
 
 1. Motivation
 
@@ -84,13 +82,13 @@
 please try to make your message helpful and friendly.  Probably they
 didn't know about the rule in question, or understand it differently.
 
-If you can, refer the other Developer to some documentation saying
-when they should and should not do something, do so.  If such
-documentation does not exist, consider writing it - it is difficult for
-nonexistent documentation to be authoritative, and a misunderstanding
-that arises once in the absence of a documented procedure is likely to
-arise again.  The Debian Developers' Reference is usually an excellent
-place to document common practice.
+If you can, refer the other Developer to some documentation explaining
+what the right process is.  If such documentation does not exist,
+consider writing it - it is difficult for nonexistent documentation to
+be authoritative, and a misunderstanding that arises once in the
+absence of a documented procedure is likely to arise again.  The
+Debian Developers' Reference is usually an excellent place to document
+common practice.
 
 If the other Developer disagrees, you should seek guidance from the
 wider Project, so that everyone has the same ideas of how things are

Attachment: pgp0jqxHTu3Nz.pgp
Description: PGP signature

Reply via email to