coar 98/01/17 22:48:02
Modified: . guidelines.html
Log:
Clean up some HTML, make minor editorial changes, and add a forward
reference to the Commit-Then-Review discussion to the section
about code review.
Revision Changes Path
1.3 +28 -23 apache-devsite/guidelines.html
Index: guidelines.html
===================================================================
RCS file: /export/home/cvs/apache-devsite/guidelines.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- guidelines.html 1998/01/12 02:15:37 1.2
+++ guidelines.html 1998/01/18 06:48:00 1.3
@@ -49,7 +49,8 @@
A member is considered inactive by their own declaration or by not
contributing in any form to the project for over six months. An
inactive member can become active again by reversing whichever
condition
- made them inactive (i.e., by reversing their earlier declaration or
+ made them inactive (<EM>i.e.</EM>, by reversing their earlier
+ declaration or
by once again contributing toward the project's work). Membership
can be revoked by a unanimous vote of all the active members other
than the member in question.</DD><P>
@@ -63,7 +64,7 @@
<DT><STRONG>mailing list</STRONG></DT>
<DD>The Apache developers' primary mailing list for discussion of issues
- and changes related to the project (<i>new-httpd@apache.org</i>).
+ and changes related to the project (<EM>new-httpd@apache.org</EM>).
Subscription to the list is open, but only subscribers
can post directly to the list.</DD><P>
@@ -75,17 +76,17 @@
<DT><STRONG>CVS</STRONG></DT>
<DD>All of the Apache products are maintained in shared information
- repositories using <a href="devnotes.html">CVS on
- <i>dev.apache.org</i>.</a> Only some of the Apache developers have
+ repositories using <A HREF="devnotes.html">CVS on
+ <EM>dev.apache.org</EM></A>. Only some of the Apache developers have
write access to these repositories; everyone has read access via
- <a href="anoncvs.txt">anonymous CVS</a>. Developers who want write
+ <A HREF="anoncvs.txt">anonymous CVS</A>. Developers who want write
access need to ask for it on the mailing list and, if approved, need
- to ask the admin of <i>dev.apache.org</i> for a user account.</DD>
+ to ask the admin of <EM>dev.apache.org</EM> for a user account.</DD>
</DL>
<HR SIZE=6>
-<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
+<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
STATUS</H2>
<P>
@@ -109,7 +110,7 @@
but not all of them will require a formal vote.
</P>
-<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
+<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
Voting</H2>
<P>
@@ -163,7 +164,7 @@
at least <STRONG>3 binding +1</STRONG> votes and <STRONG>no vetos</STRONG>.
An action item requiring <em>simple approval</em> must receive
at least <STRONG>3 binding +1</STRONG> votes and more <STRONG>+1</STRONG>
-votes than <STRONG>-1</STRONG> votes (i.e., a majority with a minimum
+votes than <STRONG>-1</STRONG> votes (<EM>i.e.</EM>, a majority with a
minimum
quorum of three positive votes).
</P>
@@ -173,7 +174,7 @@
or added directly to the STATUS file entry for that action item.
</P>
-<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
+<H2><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
Types of Action Items</H2>
<DL>
@@ -184,9 +185,11 @@
<DT><STRONG>Code Changes</STRONG></DT>
<DD>Code changes require peer review and testing over a wide range
of server platforms. Therefore, all code changes must pass through
- a formal "patch vote", as described <a href="#patchvote">below</A>.
+ a formal "patch vote", as described <A HREF="#patchvote">below</A>.
All those participating in a patch vote must be willing and able
- to test the patched system.</DD>
+ to test the patched system. <STRONG>However, see the section on
+ "<A HREF="#ctr">To Commit, or Not to Commit?</A>"
+ below, which modifies this paragraph.</STRONG></DD>
<DT><STRONG>Documentation Changes</STRONG></DT>
<DD>Documentation changes are only voted on after (or during) the change.
@@ -218,18 +221,18 @@
spending time on less adequate solutions.
</DL>
-<H2><IMG SRC="images/apache_feather_bullet.gif" alt="o ">
-To Commit, or Not to Commit?</H2>
+<H2><A NAME="ctr"><IMG SRC="images/apache_feather_bullet.gif" ALT="o ">
+To Commit, or Not to Commit?</A></H2>
<P>
-We are exploring a new system to help speed development,
-"commit-then-review". With a commit-then-review, we trust that
+We are exploring a new process to help speed development,
+"commit-then-review". With a commit-then-review process, we trust that
committers have a high degree of confidence in their committed patches
---- higher than the typical [PATCH] post to new-httpd.
+--- higher than the typical [PATCH] post to the mailing list.
<UL>
-<LI>Advance notice (eg: "I'll be working on flurgl.c") will be given
-<LI>The CVS tree should be expected to compile at all times; If it
+<LI>Advance notice (<EM>e.g.</EM>, "I'll be working on flurgl.c") will be
given
+<LI>The CVS tree should be expected to compile at all times; if it
is possible that the code will result in some platforms not
compiling, notice of this should be announced.
<LI>Experimental new features must be discussed before implemented
@@ -238,13 +241,14 @@
<LI>Related changes should be posted at once, or very closely together;
no half-baked projects in the code.
-<LI>Any changes:</BR>
+<LI>Any changes:
+ <BR>
<UL>
<LI>which affect semantics of arguments to directives
<LI>which would have to be implemented differently on other architectures
<LI>which significantly add to the runtime size of the program
</UL>
- need to be discussed on new-httpd before it gets committed.
+ need to be discussed on the mailing list before it gets committed.
<LI>A patch must be reversed if the equivalent of a "veto" comes from
another developer with commit access.
@@ -283,7 +287,8 @@
<H3>Alternate Patches</H3>
<P>Once uploaded, changes to the contents of a patchfile are limited
-to the header information (i.e., everything other than the patch itself).
+to the header information (<EM>i.e.</EM>, everything other than the
+patch itself).
For example, the Changelog entry can be changed, but not the output
of the <CODE>diff</CODE> command(s).
@@ -309,7 +314,7 @@
whether or not the release is made public. Unlike the other votes,
a minority opinion cannot stop a public release.</P>
-<P>If it is to be released publically, everyone on the mailing
+<P>If it is to be released publicly, everyone on the mailing
list should make the effort to download it and try it out.
should not be publically released until 24 hours after it has been created
and announced to the group.</P>
