You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@james.apache.org by er...@apache.org on 2012/04/19 09:15:45 UTC

svn commit: r1327847 - in /james/site/trunk/www: contribute.html download.html guidelines.html index.html license.html mail.html newsarchive.html project-info.html team-list.html

Author: eric
Date: Thu Apr 19 07:15:44 2012
New Revision: 1327847

URL: http://svn.apache.org/viewvc?rev=1327847&view=rev
Log:
web page format + information on documentation

Modified:
    james/site/trunk/www/contribute.html
    james/site/trunk/www/download.html
    james/site/trunk/www/guidelines.html
    james/site/trunk/www/index.html
    james/site/trunk/www/license.html
    james/site/trunk/www/mail.html
    james/site/trunk/www/newsarchive.html
    james/site/trunk/www/project-info.html
    james/site/trunk/www/team-list.html

Modified: james/site/trunk/www/contribute.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/contribute.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/contribute.html (original)
+++ james/site/trunk/www/contribute.html Thu Apr 19 07:15:44 2012
@@ -18,12 +18,12 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
     <title>
-      Contributors How To</title>
+    Contributors How To</title>
     <style type="text/css" media="all">
       @import url("./css/james.css");
       @import url("./css/maven-base.css");
@@ -37,8 +37,8 @@
     <script type="text/javascript" src="./js/jquery/js/jquery-ui-1.8.5.custom.min.js"></script>
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-      <meta name="author" content="Danny Angus" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+      <meta name="author" content="James Project Web Team" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -78,7 +78,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -88,8 +88,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>
@@ -203,118 +201,210 @@
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License. -->
-   
-       <div class="section"><h2>Introduction<a name="Introduction"></a></h2>
-       <p>
-           <b>Anyone can contribute</b><br />
-           That's right, we always want to hear from people with contributions to the code, 
-           the documentation, the website, and bug reports.<br /> 
-           The rest of this document outlines the way to go about these to maximum effect.<br />
-       </p>
-       <p>
-           If you are new to this you may be interested in some of these resources.<br />
-           <a class="externalLink" href="http://jakarta.apache.org/site/guidelines.html">A good, full, summary of links to guidelines</a><br />
-           Subscribe to the relevant mailing lists (link on the left).<br />
-           <a class="externalLink" href="http://jakarta.apache.org/site/contributing.html">Craig R. McClanahan's advice how to get involved</a><br />
-       </p>
-       
-       </div>
-
-        <div class="section"><h2>Code Patches<a name="Code_Patches"></a></h2>
-        <p>
-            Patches should be submitted to the developers mailing list.<br />
-            <b>Always</b> use diff -u to generate patches, so we can apply them using 'patch'.<br />
+
+  
+
+    <div class="section"><h2>Introduction<a name="Introduction"></a></h2>
+      <p>
+        <b>Anyone can contribute</b>
+        <br />
+        That's right, we always want to hear from people with
+        contributions to the code,
+        the documentation, the website, and bug reports.
+        <br />
+        The rest of this document outlines the way to go about these to
+        maximum effect.
+        <br />
+      </p>
+      <p>
+        If you are new to this you may be interested in some of these
+        resources.
+        <br />
+        <a class="externalLink" href="http://jakarta.apache.org/site/guidelines.html">A good, full, summary of links to guidelines</a>
+        <br />
+        Subscribe to the relevant mailing lists (link on the left).
+        <br />
+        <a class="externalLink" href="http://jakarta.apache.org/site/contributing.html">Craig R. McClanahan's advice how to get involved</a>
+        <br />
+      </p>
+    </div>
+
+    <div class="section"><h2>Code Patches<a name="Code_Patches"></a></h2>
+      <p>
+        Patches should be submitted to the developers mailing list.
+        <br />
+        <b>Always</b>
+        use diff -u to generate patches, so we can apply them using
+        'patch'.
+        <br />
+<!-- // Update this for SVN
         Make sure you are patching the latest cvs (the HEAD).
-        (You might want to try 'cvs diff -u -w -b -rHEAD' against the checked out module where
-        you have implemented the patch.<br />
-            <br />Make sure the patch only contains what is intended, your checkout could be outdated.<br />
-            Make your patch from the jakarta-james directory and make sure it conforms
-            to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
-            files, but please only one issue at a time.<br />
-            Prefix the mail subject with [PATCH]<br />
-            Briefly outline the reason for your patch,
-            the solution your patch implements, why a patch is
-            needed and why your code will solve the problem. Note any bug numbers your patch addresses.<br />
-            Submit the patch as an attachment to the mail, this
-        mail should preferably be in either BASE64 or QuotedPrintable format, to prevent line wrapping.<br />
-            </p>
-
-        <p>
-            The reason for these rules is so that commiters can easily see what you are trying to achieve,
-            it is their resonsibility to manage the code and review submissions, 
-            if you make it easy for them to see what you are doing your patch is more likely to 
-            be commited quickly (or at all).<br />
-        </p>
-        </div>
-    
-        <div class="section"><h2>Adding New Code<a name="Adding_New_Code"></a></h2>
-        <p>
-            Like the principles for patch submission, mark your mail [PATCH] and ensure 
-            your submission conforms to the code standards. Provide a Brief outline of 
-            your intentions, as above, so that your code can be reviewed easily, and a 
-            note of any relevant bug numbers.<br />
-            New files must contain a reference to the Apache licence, copy the header from an existing file.<br />
-            It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the jakarta-james directory so we can un-tar your files into the right place.
-        </p>
-        </div>
-    
-        <div class="section"><h2>Reporting and Fixing Bugs<a name="Reporting_and_Fixing_Bugs"></a></h2>
-        <p>
-            Many improvements come as a direct result of bug 
-            reports, and contributed fixes, often by the same person. It is sometimes said that Apache 
-            projects evolve because users become so fed-up waiting for bugs to be addressed that they 
-            fix them themselves. :)<br />
-            If you report a bug, <a class="externalLink" href="http://issues.apache.org/jira">here</a> we'd appreciate it if you could send a mail to the users or developers 
-            mailing lists, so that we can discuss it with you, bugzilla isn't a great way for mediating 
-            communication.<br />
-            If you want to fix a bug, please contribute your changes according to the guidelines above, 
-            in the Code Patches section. It is much simpler to deal with submissions if they all come 
-            through the same channel. If you still really want to attach patches to bug submissions, please do send us a mail tagged [PATCH] too, so that we notice your patch.
-        </p>
-        </div>
-    
-        <div class="section"><h2>Documentation<a name="Documentation"></a></h2>
-        <p>
-            While we are glad to accept contributions to documentation 
-            from anyone, in almost any format, because its much better than none, please consider these 
-            guidelines to help us to assimilate your contribution.<br />
-            To edit an existing document try to edit the xml version in src/xdocs (check it out from cvs) 
-            and if you can, submit a patch as for Code Patches.<br />
-            If you want to contribute new files please try to use the simple xml format we use.<br />
-            If this means nothing to you please try to contribute HTML or plain text documents without 
-            any styling, so that we can get at the words and easily convert them into our xml format.<br />
-            If all this seems like unnecessary nonsense, send us whatever you like, we'd still be
-             happy to receive good documentation.
-         </p>
-         </div>
-         
-         <div class="section"><h2>Coding Standards<a name="Coding_Standards"></a></h2>
-
-         <p>
-            Submissions to the James project must follow the coding conventions
-            outlined in this document. James developers
-            are asked to follow coding conventions already present in the code.
-            (For example, if the existing code has the bracket on
-            the same line as the if statement, then all subsequent code
-            should also follow that convention.) Anything not
-            explicitly mentioned in this document should adhere to the
-            official
-            <a class="externalLink" href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Sun
-            Java Coding Conventions</a>.
-         </p>
-        
-         <p>
-            <b>Developers who commit code that does not follow
-            the coding conventions outlined in this document will be
-            responsible for fixing their own code.</b>
-         </p>
-        
-         <p>
-        1. Spaces between parentheses are optional. The preference is to exclude
-        extra spaces. Both of these conventions are acceptable:
-         </p>
-        
-         <p>
+        (You might
+        want to try 'cvs diff -u -w -b -rHEAD' against the checked out
+        module where
+        you have implemented the patch.
+        <br /> -->
+         <br />
+        Make sure the patch only contains what is intended, your
+        checkout could be outdated.
+        <br />
+        Make your patch from the jakarta-james directory and make sure
+        it conforms
+        to the code standards, otherwise it may be ignored. It is OK to make a
+        single patch covering several
+        files, but please only one issue at a time.
+        <br />
+        Prefix the mail subject with [PATCH]
+        <br />
+        Briefly outline the reason for your patch,
+        the solution your patch implements, why a patch is
+        needed and why your code will solve the problem. Note any bug numbers your
+        patch addresses.
+        <br />
+        Submit the patch as an attachment to the mail, this
+        mail should
+        preferably be in either BASE64 or QuotedPrintable format, to
+        prevent line wrapping.
+        <br />
+      </p>
+
+      <p>
+        The reason for these rules is so that commiters can easily see
+        what you are trying to achieve,
+        it is their resonsibility to manage the code and review submissions,
+        if you make it easy for them to see what you are doing your
+        patch is more likely to
+        be commited quickly (or at all).
+        <br />
+      </p>
+    </div>
+
+    <div class="section"><h2>Adding New Code<a name="Adding_New_Code"></a></h2>
+      <p>
+        Like the principles for patch submission, mark your mail [PATCH]
+        and ensure
+        your submission conforms to the code standards. Provide a Brief outline
+        of
+        your intentions, as above, so that your code can be reviewed easily, and
+        a
+        note of any relevant bug numbers.
+        <br />
+        New files must contain a reference to the Apache licence, copy
+        the header from an existing file.
+        <br />
+        It also helps if you send your files in an archive (tar, zip)
+        which preserves directories, make it from the jakarta-james
+        directory so we can un-tar your files into the right place.
+      </p>
+    </div>
+
+    <div class="section"><h2>Reporting and Fixing Bugs<a name="Reporting_and_Fixing_Bugs"></a></h2>
+      <p>
+        Many improvements come as a direct result of bug
+        reports, and contributed fixes, often by the same person. It is sometimes
+        said that Apache
+        projects evolve because users become so fed-up waiting for bugs to be
+        addressed that they
+        fix them themselves. :)
+        <br />
+        If you report a bug,
+        <a class="externalLink" href="http://issues.apache.org/jira">here</a>
+        we'd appreciate it if you could send a mail to the users or
+        developers
+        mailing lists, so that we can discuss it with you, bugzilla isn't a great
+        way for mediating
+        communication.
+        <br />
+        If you want to fix a bug, please contribute your changes
+        according to the guidelines above,
+        in the Code Patches section. It is much simpler to deal with
+        submissions if they all come
+        through the same channel. If you still really want to attach patches to bug
+        submissions, please do send us a mail tagged [PATCH] too, so
+        that we notice your patch.
+      </p>
+    </div>
+
+    <div class="section"><h2>Documentation<a name="Documentation"></a></h2>
+      <p>
+        While we are glad to accept contributions to documentation
+        from anyone, in almost any format, because its much better than none,
+        please consider these
+        guidelines to help us to assimilate your contribution.
+      </p>
+      <p>
+        To edit an existing document try to edit the xml version in src/site/xdocs
+        (check it out from SVN)
+        and if you can, submit a patch as for Code Patches.
+      </p>
+      <p>
+        If you want to contribute new files please try to use the simple xml
+        format we use.
+      </p>
+      <p>
+        If this means nothing to you please try to contribute HTML or plain
+        text documents without
+        any styling, so that we can get at the words and easily convert them
+        into our XML format.
+      </p>
+      <p>
+        If all this seems like unnecessary nonsense, send us whatever you
+        like, we'd still be
+        happy to receive good documentation.
+      </p>
+      <p>
+        Each of the Apache James projects has its own documentation
+        maintained
+        with the automated build. Once a build is done, the documentation can be
+        further committed in the
+        <a class="externalLink" href="https://svn.apache.org/repos/asf/james/site/trunk">
+          site module
+        </a>
+        which will be automatically published via svnpubsub
+        to
+        <a class="externalLink" href="http://james.apache.org">Apache James web site</a>
+        .
+      </p>
+      <p>
+        Further to this documentation, the
+        <a class="externalLink" href="http://wiki.apache.org/james/">
+          Apache James wiki
+        </a>
+        is available to any and is useful to share any
+        useful documentation.
+        .
+      </p>
+    </div>
+
+    <div class="section"><h2>Coding Standards<a name="Coding_Standards"></a></h2>
+      <p>
+        Submissions to the James project must follow the coding
+        conventions
+        outlined in this document. James developers
+        are asked to follow coding conventions already present in the code.
+        (For example, if the existing code has the bracket on
+        the same line as the if statement, then all subsequent code
+        should also follow that convention.) Anything not
+        explicitly mentioned in this document should adhere to the
+        official
+        <a class="externalLink" href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Sun
+          Java Coding Conventions
+        </a>
+        .
+      </p>
+      <p>
+        <b>Developers who commit code that does not follow
+          the coding conventions outlined in this document will be
+          responsible for fixing their own code.
+        </b>
+      </p>
+      <p>
+        1. Spaces between parentheses are optional. The preference is
+        to exclude
+        extra spaces. Both of these conventions are
+        acceptable:
+      </p>
+      <p>
         </p><div class="source"><pre>
   
   if (foo)
@@ -323,52 +413,66 @@
   
   if ( foo )
         </pre></div>
-        
-        
-        <p>
-        2. Four spaces. <b>NO tabs</b>. Period. The James
-        mailing list receives commit messages that are almost impossible
+      
+      <p>
+        2. Four spaces.
+        <b>NO tabs</b>
+        . Period. The James
+        mailing list receives commit messages that
+        are almost impossible
         to read if tabs are used.
-        </p>
-        
-        <p>
+      </p>
+      <p>
         In Emacs-speak, this translates to the following command:
-        
+
         (setq-default tab-width 4 indent-tabs-mode nil)
-        </p>
-        
-        <p>
-        3. Use Unix linefeeds for all .java source code files. Only platform-specific
-        files (e.g. .bat files for Windows) should contain non-Unix linefeeds.
-        </p>
-        
-        <p>
-        4. Javadoc <b>must</b> exist on all methods. Contributing
-        a missing javadoc for any method, class, variable, etc., will be GREATLY
-        appreciated as this will help to improve the James project.
-        </p>
-        
-        <p>
-        5. The standard Apache boilerplace <b>MUST</b> be placed
+      </p>
+      <p>
+        3. Use Unix linefeeds for all .java source code files. Only
+        platform-specific
+        files (e.g. .bat files for Windows) should
+        contain non-Unix linefeeds.
+      </p>
+      <p>
+        4. Javadoc
+        <b>must</b>
+        exist on all methods. Contributing
+        a missing javadoc for any
+        method, class, variable, etc., will be GREATLY
+        appreciated as
+        this will help to improve the James project.
+      </p>
+      <p>
+        5. The standard Apache boilerplace
+        <b>MUST</b>
+        be placed
         at the top of every file.
-        </p>
-        
-        <p>
-        6. <b>pom.xml</b> files shall follow the same ordering as seen in the reference
-        of the <a class="externalLink" href="http://maven.apache.org/ref/3.0.3/maven-model/maven.html">Maven Model</a>,
+      </p>
+      <p>
+        6.
+        <b>pom.xml</b>
+        files shall follow the same ordering as seen in the reference
+        of
+        the
+        <a class="externalLink" href="http://maven.apache.org/ref/3.0.3/maven-model/maven.html">Maven Model</a>
+        ,
         split multiple attributes each on a new line.
-        </p>
-        
-        <p>
-          <b>Eclipse IDE</b><br />
-          Eclipse users can import those two files to enfore the code formating :
-          <a href="downloads/formatting.xml">formatting.xml</a> and
-          <a href="downloads/codetemplates.xml">codetemplates.xml</a>.
-        </p>
-        </div>
-    
-        
-   
+      </p>
+      <p>
+        <b>Eclipse IDE</b>
+        <br />
+        Eclipse users can import those two files to enfore the code
+        formating :
+        <a href="downloads/formatting.xml">formatting.xml</a>
+        and
+        <a href="downloads/codetemplates.xml">codetemplates.xml</a>
+        .
+      </p>
+    </div>
+
+  
+
+
       </div>
     </div>
     <div class="clear">

Modified: james/site/trunk/www/download.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/download.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/download.html (original)
+++ james/site/trunk/www/download.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -38,7 +38,7 @@
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="Apache James Mail Server Project" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -136,7 +136,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -146,8 +146,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>
@@ -308,8 +306,8 @@ is found <a class="externalLink" href="h
       <li><a href="#Apache_Crypto_Mailets">Apache James Crypto Mailets</a></li>
       <li><a href="#Apache_James_Protocols">Apache James Protocols</a></li>
       <li><a href="#Apache_MPT">Apache James MPT</a></li>
-      <li>Apache James IMAP is available from the James Maven repositories (*)</li>
-      <li>Apache James Mailbox is available from the James Maven repositories (*)</li>
+      <li>Apache James IMAP 0.3 is available from the James Maven repositories (*)</li>
+      <li>Apache James Mailbox 0.4 is available from the James Maven repositories (*)</li>
       <li>Apache MailetDoc Plugin for Maven is available from the standard Maven repositories (*)</li>
       <li>Apache James Hupa is available from the James Maven repositories (*)</li>
     </ul>
@@ -424,9 +422,9 @@ is found <a class="externalLink" href="h
         <li>Binary (Unix TAR): <a href="[preferred]/james/apache-james/3.0beta4/apache-james-3.0-beta4-app.tar.gz">apache-james-3.0-beta4-app.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-james/3.0beta4/apache-james-3.0-beta4-app.tar.gz.asc">PGP</a>]</li>
       
         <li>Binary (ZIP Format): <a href="[preferred]/james/apache-james/3.0beta4/apache-james-3.0-beta4-app.zip">apache-james-3.0-beta4-app.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-james/3.0beta4/apache-james-3.0-beta4-app.zip.asc">PGP</a>]</li>
-      
-          <li>Source (Unix TAR): <a href="[preferred]/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.tar.gz">apache-james-3.0-beta4-source-release.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.tar.gz.asc">PGP</a>]</li>
-      
+<!-- <li>Source (Unix TAR): <a
+              href="[preferred]/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.tar.gz">apache-james-3.0-beta4-source-release.tar.gz</a> [<a
+              href="http://www.apache.org/dist/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.tar.gz.asc">PGP</a>]</li> -->      
           <li>Source (ZIP Format): <a href="[preferred]/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.zip">apache-james-3.0-beta4-source-release.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-james/3.0beta4/apache-james-3.0-beta4-source-release.zip.asc">PGP</a>]</li>
       
       </ul>
@@ -534,19 +532,13 @@ is found <a class="externalLink" href="h
     <p>Apache JSieve 0.5 is the latest stable version:</p>
     <ul>
     
-    <li>Binary (Unix TAR): <a href="[preferred]/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.tar.gz">apache-jsieve-0.5-bin.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.tar.gz.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.tar.gz.md5">MD5</a>]</li>
-    
-    <li>Binary (ZIP Format): <a href="[preferred]/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.zip">apache-jsieve-0.5-bin.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.zip.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-bin.zip.md5">MD5</a>]</li>
-    
-    <li>Source (Unix TAR): <a href="[preferred]/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.tar.gz">apache-jsieve-0.5-src.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.tar.gz.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.tar.gz.md5">MD5</a>]</li>
-    
-    <li>Source (ZIP Format): <a href="[preferred]/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.zip">apache-jsieve-0.5-src.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.zip.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-james-jsieve-0.5-src.zip.md5">MD5</a>]</li>
+    <li>Binary (Unix TAR): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.tar.gz">apache-jsieve-all-0.5-bin.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.tar.gz.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.tar.gz.asc.md5">MD5</a>]</li>
     
-    <li><abbr title="Java ARchive">JAR</abbr> library only: <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-0.5.jar">apache-jsieve-0.5.jar</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5.jar.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5.jar.md5">MD5</a>]</li>
+    <li>Binary (ZIP Format): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.zip">apache-jsieve-all-0.5-bin.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.zip.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-bin.zip.asc.md5">MD5</a>]</li>
     
-    <li>Javadocs only (for IDEs): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-0.5-javadoc.jar">apache-jsieve-0.5-javadoc.jar</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5-javadoc.jar.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5-javadoc.jar.md5">MD5</a>]</li>
+    <li>Source (Unix TAR): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.tar.gz.tar.gz">apache-jsieve-all-0.5-src.tar.gz</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.tar.gz.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.tar.gz.asc.md5">MD5</a>]</li>
     
-    <li>Source <abbr title="Java ARchive">JAR</abbr> only (for IDEs): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-0.5-sources.jar">apache-jsieve-0.5-sources.jar</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5-sources.jar.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-0.5-sources.jar.md5">MD5</a>]</li>
+    <li>Source (ZIP Format): <a href="[preferred]/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.zip">apache-jsieve-all-0.5-src.zip</a> [<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.zip.asc">PGP</a>][<a class="externalLink" href="http://www.apache.org/dist/james/apache-jsieve/0.5/apache-jsieve-all-0.5-src.zip.asc.md5">MD5</a>]</li>
     
     </ul>
   

Modified: james/site/trunk/www/guidelines.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/guidelines.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/guidelines.html (original)
+++ james/site/trunk/www/guidelines.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -38,7 +38,7 @@
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="James Project Web Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -78,7 +78,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -88,8 +88,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>
@@ -203,220 +201,377 @@
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License. -->
-  
-    <div class="section"><h2>Apache James Project Guidelines<a name="Apache_James_Project_Guidelines"></a></h2>
-
-<p>
-    This document defines the guidelines for the Apache James Project. It includes definitions of how conflict is resolved by voting, who is able to vote, and the procedures to follow for proposing and making changes to the Apache James products.
-
-</p>
-<p>
-     The objective here is to avoid unnecessary conflict over changes and continue to produce a quality system in a timely manner. Not all conflict can be avoided, but at least we can agree on the procedures for conflict to be resolved.
-
-</p>
-    </div>
-    <div class="section"><h2>People, Places, and Things<a name="People_Places_and_Things"></a></h2>
-
-    <div class="section"><h3>Apache James Project Management Committee<a name="Apache_James_Project_Management_Committee"></a></h3>
-<p>
-        The group of volunteers who are responsible for managing the Apache James Project. This includes deciding what is distributed as products of the Apache James Project, maintaining the Project's shared resources, speaking on behalf of the Project, resolving license disputes regarding Apache James products, nominating new PMC members or committers, and establishing these guidelines.
-
-</p>
-<p>
-         Membership in the Apache James PMC is by invitation only and must be approved by consensus of the active Apache James PMC members. A PMC 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 by once again contributing toward the project's work). Membership can be revoked by a unanimous vote of all the active PMC members other than the member in question.
 
-</p>
-    </div>
-    <div class="section"><h3>Apache James Committers<a name="Apache_James_Committers"></a></h3>
-<p>
-        The group of volunteers who are responsible for the technical aspects of the Apache James Project. This group has write access to the appropriate source repositories and these volunteers may cast non-binding votes on any technical discussion.
-</p>
-<p>
-         Membership as a Committer is by invitation only and must be approved by consensus of the active Apache James PMC members. A Committer 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 by once again contributing toward the project's work). Membership can be revoked by a unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
-
-</p>
-    </div>
-    <div class="section"><h3>mailing list<a name="mailing_list"></a></h3>
-<p>
-        The Apache committers' primary mailing list for discussion of issues and changes related to the project (server-dev@james.apache.org). Subscription to the list is open, but only subscribers can post directly to the list.
+  
 
-</p>
-    </div>
-    <div class="section"><h3>private list<a name="private_list"></a></h3>
-<p>
-        The Apache James Project's private mailing list for discussion of issues that are inappropriate for public discussion, such as legal, personal, or security issues prior to a published fix. Subscription to the list is only open to Apache James PMC members and Apache Software Foundation Members.
+    <div class="section"><h2>Apache James Project Guidelines<a name="Apache_James_Project_Guidelines"></a></h2>
+      <p>
+        This document defines the guidelines for the Apache James Project. It
+        includes definitions of how conflict is resolved by voting, who
+        is able to vote, and the procedures to follow for proposing and
+        making changes to the Apache James products.
+      </p>
+      <p>
+        The objective here is to avoid unnecessary conflict over changes and
+        continue to produce a quality system in a timely manner. Not all
+        conflict can be avoided, but at least we can agree on the
+        procedures for conflict to be resolved.
 
-</p>
+      </p>
     </div>
-    <div class="section"><h3>SVN<a name="SVN"></a></h3>
-<p>
-        All of the Apache James products are maintained in shared information repositories using SVN on svn.apache.org. The Apache committers have write access to these repositories; everyone has read access via anonymous SVN.
 
-</p>
-    </div>
+    <div class="section"><h2>People, Places, and Things<a name="People_Places_and_Things"></a></h2>
+      <div class="section"><h3>Apache James Project Management Committee<a name="Apache_James_Project_Management_Committee"></a></h3>
+        <p>
+          The group of volunteers who are responsible for managing the Apache
+          James Project. This includes deciding what is distributed as
+          products of the Apache James Project, maintaining the
+          Project's shared resources, speaking on behalf of the Project,
+          resolving license disputes regarding Apache James products,
+          nominating new PMC members or committers, and establishing
+          these guidelines.
+        </p>
+        <p>
+          Membership in the Apache James PMC is by invitation only and must be approved
+          by consensus of the active Apache James PMC members. A PMC
+          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 by once again
+          contributing toward the project's work). Membership can be
+          revoked by a unanimous vote of all the active PMC members
+          other than the member in question.
+
+        </p>
+      </div>
+      <div class="section"><h3>Apache James Committers<a name="Apache_James_Committers"></a></h3>
+        <p>
+          The group of volunteers who are responsible for the technical aspects
+          of the Apache James Project. This group has write access to
+          the appropriate source repositories and these volunteers may
+          cast non-binding votes on any technical discussion.
+        </p>
+        <p>
+          Membership as a Committer is by invitation only and must be approved by
+          consensus of the active Apache James PMC members. A Committer
+          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 by once again contributing toward
+          the project's work). Membership can be revoked by a unanimous
+          vote of all the active PMC members (except the member in
+          question if they are a PMC member).
+
+        </p>
+      </div>
+      <div class="section"><h3>Mailing list<a name="Mailing_list"></a></h3>
+        <p>
+          The Apache committers' primary mailing list for discussion of issues
+          and changes related to the project
+          (server-dev@james.apache.org). Subscription to the list is
+          open, but only subscribers can post directly to the list.
+        </p>
+      </div>
+      <div class="section"><h3>Private list<a name="Private_list"></a></h3>
+        <p>
+          The Apache James Project's private mailing list for discussion of
+          issues that are inappropriate for public discussion, such as
+          legal, personal, or security issues prior to a published fix.
+          Subscription to the list is only open to Apache James PMC
+          members and Apache Software Foundation Members.
+        </p>
+      </div>
+      <div class="section"><h3>SVN<a name="SVN"></a></h3>
+        <p>
+          All of the Apache James products are maintained in shared information
+          repositories using SVN on svn.apache.org. The Apache
+          committers have write access to these repositories; everyone
+          has read access via anonymous SVN.
+        </p>
+      </div>
+    </div>
+
+    <div class="section"><h2>Status<a name="Status"></a></h2>
+      <p>
+        Each of the Apache Project's active source code repositories contain a
+        file called &quot;STATUS&quot; which is used to keep track of the agenda
+        and plans for work within that repository. The STATUS file
+        includes information about release plans, a summary of code
+        changes committed since the last release, a list of proposed
+        changes that are under discussion, brief notes about items that
+        individual committers are working on or want discussion about,
+        and anything else that might be useful to help the group track
+        progress. The active STATUS files are automatically posted to
+        the mailing list each week.
+      </p>
+      <p>
+        Many issues will be encountered by the project, each resulting in zero
+        or more proposed action items. Issues should be raised on the
+        mailing list as soon as they are identified. Action items must
+        be raised on the mailing list and added to the relevant STATUS
+        file. All action items may be voted on, but not all of them will
+        require a formal vote.
+      </p>
     </div>
-    <div class="section"><h2>STATUS<a name="STATUS"></a></h2>
-
-<p>
-     Each of the Apache Project's active source code repositories contain a file called &quot;STATUS&quot; which is used to keep track of the agenda and plans for work within that repository. The STATUS file includes information about release plans, a summary of code changes committed since the last release, a list of proposed changes that are under discussion, brief notes about items that individual committers are working on or want discussion about, and anything else that might be useful to help the group track progress. The active STATUS files are automatically posted to the mailing list each week.
 
-</p>
-<p>
-     Many issues will be encountered by the project, each resulting in zero or more proposed action items. Issues should be raised on the mailing list as soon as they are identified. Action items must be raised on the mailing list and added to the relevant STATUS file. All action items may be voted on, but not all of them will require a formal vote.
-
-</p>
-    </div>
     <div class="section"><h2>Voting<a name="Voting"></a></h2>
-
-<p>
-     Any of the Apache James Committers may vote on any issue or action item. However, the only binding votes are those cast by active members of the Apache James PMC; if the vote is about a change to source code or documentation, the primary author of what is being changed may also cast a binding vote on that issue. All other votes are non-binding. All committers are encouraged to participate in decisions, but the decision itself is made by those who have been long-time contributors to the project. In other words, the Apache Project is a minimum-threshold meritocracy.
-
-</p>
-<p>
-     The act of voting carries certain obligations -- voting members are not only stating their opinion, they are agreeing to help do the work of the Apache Project. Since we are all volunteers, members often become inactive for periods of time in order to take care of their &quot;real jobs&quot; or devote more time to other projects. It is therefore unlikely that the entire group membership will vote on every issue. To account for this, all voting decisions are based on a minimum quorum.
-
-</p>
-<p>
-     Each vote can be made in one of three flavors:
-</p>
-<p>
-    <b>+1</b><br />
-        Yes, agree, or the action should be performed. On some issues, this vote is only binding if the voter has tested the action on their own system(s).
-</p>
-<p>
-    <b>+-0</b><br />
-        Abstain, no opinion, or I am happy to let the other group members decide this issue. An abstention may have detrimental effects if too many people abstain.
-</p>
-<p>
-    <b>-1</b><br />
-        No. On issues where consensus is required, this vote counts as a veto. All vetos must include an explanation of why the veto is appropriate. A veto with no explanation is void. No veto can be overruled. If you disagree with the veto, you should lobby the person who cast the veto. Voters intending to veto an action item should make their opinions known to the group immediately, so that the problem can be remedied as early as possible.
-
-</p>
-<p>
-     An action item requiring consensus approval must receive at least 3 binding +1 votes and no vetos. An action item requiring majority approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes (i.e., a majority with a minimum quorum of three positive votes). All other action items are considered to have lazy approval until someone votes -1, after which point they are decided by either consensus or a majority vote, depending upon the type of action item.
-
-</p>
-<p>
-     Votes are tallied within the STATUS file, adjacent to the action item under vote. All votes must be either sent to the mailing list or added directly to the STATUS file entry for that action item.
-</p>
-
-<p>
-     Votes are to remain open for 72 hours after which the developer who put forth the vote should tabulate the result and send this to the mailing list.  A developer should be sensitive to holidays that could dampen participation in the vote.
-</p>
-
+      <p>
+        Any of the Apache James Committers may vote on any issue or action
+        item. However, the only binding votes are those cast by active
+        members of the Apache James PMC; if the vote is about a change
+        to source code or documentation, the primary author of what is
+        being changed may also cast a binding vote on that issue. All
+        other votes are non-binding. All committers are encouraged to
+        participate in decisions, but the decision itself is made by
+        those who have been long-time contributors to the project. In
+        other words, the Apache Project is a minimum-threshold
+        meritocracy.
+      </p>
+      <p>
+        The act of voting carries certain obligations -- voting members are not
+        only stating their opinion, they are agreeing to help do the
+        work of the Apache Project. Since we are all volunteers, members
+        often become inactive for periods of time in order to take care
+        of their &quot;real jobs&quot; or devote more time to other projects. It
+        is therefore unlikely that the entire group membership will vote
+        on every issue. To account for this, all voting decisions are
+        based on a minimum quorum.
+      </p>
+      <p>
+        Each vote can be made in one of three flavors:
+      </p>
+      <p>
+        <b>+1</b>
+        <br />
+        Yes, agree, or the action should be performed. On some issues,
+        this vote is only binding if the voter has tested the action on
+        their own system(s).
+      </p>
+      <p>
+        <b>+-0</b>
+        <br />
+        Abstain, no opinion, or I am happy to let the other group
+        members decide this issue. An abstention may have detrimental
+        effects if too many people abstain.
+      </p>
+      <p>
+        <b>-1</b>
+        <br />
+        No. On issues where consensus is required, this vote counts as a
+        veto. All vetos must include an explanation of why the veto is
+        appropriate. A veto with no explanation is void. No veto can be
+        overruled. If you disagree with the veto, you should lobby the
+        person who cast the veto. Voters intending to veto an action
+        item should make their opinions known to the group immediately,
+        so that the problem can be remedied as early as possible.
+      </p>
+      <p>
+        An action item requiring consensus approval must receive at least 3
+        binding +1 votes and no vetos. An action item requiring majority
+        approval must receive at least 3 binding +1 votes and more +1
+        votes than -1 votes (i.e., a majority with a minimum quorum of
+        three positive votes). All other action items are considered to
+        have lazy approval until someone votes -1, after which point
+        they are decided by either consensus or a majority vote,
+        depending upon the type of action item.
+      </p>
+      <p>
+        Votes are tallied within the STATUS file, adjacent to the action item
+        under vote. All votes must be either sent to the mailing list or
+        added directly to the STATUS file entry for that action item.
+      </p>
+      <p>
+        Votes are to remain open for 72 hours after which the developer who put
+        forth the vote should tabulate the result and send this to the
+        mailing list. A developer should be sensitive to holidays that
+        could dampen participation in the vote.
+      </p>
     </div>
-    <div class="section"><h2>Types of Action Items<a name="Types_of_Action_Items"></a></h2>
 
-    <div class="section"><h3>Long Term Plans<a name="Long_Term_Plans"></a></h3>
-<p>
-        Long term plans are simply announcements that group members are working on particular issues related to the Apache software. These are not voted on, but group members who do not agree with a particular plan, or think an alternate plan would be better, are obligated to inform the group of their feelings. In general, it is always better to hear about alternate plans prior to spending time on less adequate solutions.
-</p>
-    </div>
-    <div class="section"><h3>Short Term Plans<a name="Short_Term_Plans"></a></h3>
-<p>
-        Short term plans are announcements that a developer is working on a particular set of documentation or code files, with the implication that other committers should avoid them or try to coordinate their changes. This is a good way to proactively avoid conflict and possible duplication of work.
-</p>
-    </div>
-    <div class="section"><h3>Release Plan<a name="Release_Plan"></a></h3>
-<p>
-        A release plan is used to keep all the committers aware of when a release is desired, who will be the release manager, when the repository will be frozen in order to create the release, and assorted other trivia to keep us from tripping over ourselves during the final moments. Lazy majority decides each issue in the release plan.
-</p>
-    </div>
-    <div class="section"><h3>Release Testing<a name="Release_Testing"></a></h3>
-<p>
-        After a new release is built, colloquially termed a tarball, it must be tested before being released to the public. Majority approval is required before the tarball can be publically released.
-</p>
-    </div>
-    <div class="section"><h3>Showstoppers<a name="Showstoppers"></a></h3>
-<p>
-        Showstoppers are issues that require a fix be in place before the next public release. They are listed in the STATUS file in order to focus special attention on the problem. An issue becomes a showstopper when it is listed as such in STATUS and remains so by lazy consensus.
-</p>
-    </div>
-    <div class="section"><h3>Product Changes<a name="Product_Changes"></a></h3>
-<p>
-        Changes to the Apache James products, including code and documentation, will appear as action items under several categories corresponding to the change status:
-
-</p>
-    </div>
-    <div class="section"><h3>Concept/Plan<a name="ConceptPlan"></a></h3>
-<p>
-            An idea or plan for a change. These are usually only listed in STATUS when the change is substantial, significantly impacts the API, or is likely to be controversial. Votes are being requested early so as to uncover conflicts before too much work is done.
-</p>
-    </div>
-    <div class="section"><h3>Proposed Patch<a name="Proposed_Patch"></a></h3>
-<p>
-            A specific set of changes to the current product in the form of input to the patch command (a diff output).
-</p>
+    <div class="section"><h2>Types of Action Items<a name="Types_of_Action_Items"></a></h2>
+      <div class="section"><h3>Long Term Plans<a name="Long_Term_Plans"></a></h3>
+        <p>
+          Long term plans are simply announcements that group members are working
+          on particular issues related to the Apache software. These are
+          not voted on, but group members who do not agree with a
+          particular plan, or think an alternate plan would be better,
+          are obligated to inform the group of their feelings. In
+          general, it is always better to hear about alternate plans
+          prior to spending time on less adequate solutions.
+        </p>
+      </div>
+      <div class="section"><h3>Short Term Plans<a name="Short_Term_Plans"></a></h3>
+        <p>
+          Short term plans are announcements that a developer is working on a
+          particular set of documentation or code files, with the
+          implication that other committers should avoid them or try to
+          coordinate their changes. This is a good way to proactively
+          avoid conflict and possible duplication of work.
+        </p>
+      </div>
+      <div class="section"><h3>Release Plan<a name="Release_Plan"></a></h3>
+        <p>
+          A release plan is used to keep all the committers aware of when a
+          release is desired, who will be the release manager, when the
+          repository will be frozen in order to create the release, and
+          assorted other trivia to keep us from tripping over ourselves
+          during the final moments. Lazy majority decides each issue in
+          the release plan.
+        </p>
+      </div>
+      <div class="section"><h3>Release Testing<a name="Release_Testing"></a></h3>
+        <p>
+          After a new release is built, colloquially termed a tarball, it must be
+          tested before being released to the public. Majority approval
+          is required before the tarball can be publically released.
+        </p>
+      </div>
+      <div class="section"><h3>Showstoppers<a name="Showstoppers"></a></h3>
+        <p>
+          Showstoppers are issues that require a fix be in place before the next public
+          release. They are listed in the STATUS file in order to focus
+          special attention on the problem. An issue becomes a
+          showstopper when it is listed as such in STATUS and remains so
+          by lazy consensus.
+        </p>
+      </div>
+      <div class="section"><h3>Product Changes<a name="Product_Changes"></a></h3>
+        <p>
+          Changes to the Apache James products, including code and documentation,
+          will appear as action items under several categories
+          corresponding to the change status:
+        </p>
+      </div>
+      <div class="section"><h3>Concept/Plan<a name="ConceptPlan"></a></h3>
+        <p>
+          An idea or plan for a change. These are usually only listed in STATUS
+          when the change is substantial, significantly impacts the API,
+          or is likely to be controversial. Votes are being requested
+          early so as to uncover conflicts before too much work is done.
+        </p>
+      </div>
+      <div class="section"><h3>Proposed Patch<a name="Proposed_Patch"></a></h3>
+        <p>
+          A specific set of changes to the current product in the form of
+          input to the patch command (a diff output).
+        </p>
+      </div>
+      <div class="section"><h3>Committed Change<a name="Committed_Change"></a></h3>
+        <p>
+          A one-line summary of a change that has been committed to the
+          repository since the last public release.
+        </p>
+        <p>
+          All product changes to the currently active repository are subject to
+          lazy consensus. All product changes to a prior-branch (old
+          version) repository require consensus before the change is
+          committed.
+        </p>
+      </div>
     </div>
-    <div class="section"><h3>Committed Change<a name="Committed_Change"></a></h3>
-<p>
-            A one-line summary of a change that has been committed to the repository since the last public release.
-</p>
-<p>
 
-        All product changes to the currently active repository are subject to lazy consensus. All product changes to a prior-branch (old version) repository require consensus before the change is committed.
-</p>
-
-    </div>
-    </div>
     <div class="section"><h2>When to Commit a Change<a name="When_to_Commit_a_Change"></a></h2>
-
-<p>
-     Ideas must be review-then-commit; patches can be commit-then-review. With a commit-then-review process, we trust that the developer doing the commit has a high degree of confidence in the change. Doubtful changes, new features, and large-scale overhauls need to be discussed before being committed to a repository. Any change that affects the semantics of arguments to configurable directives, significantly adds to the runtime size of the program, or changes the semantics of an existing API function must receive consensus approval on the mailing list before being committed.
-
-</p>
- <p>
-     Each developer is responsible for notifying the mailing list and adding an action item to STATUS when they have an idea for a new feature or major change to propose for the product. The distributed nature of the Apache project requires an advance notice of 48 hours in order to properly review a major change -- consensus approval of either the concept or a specific patch is required before the change can be committed. Note that a member might veto the concept (with an adequate explanation), but later rescind that veto if a specific patch satisfies their objections. No advance notice is required to commit singular bug fixes.
-
-</p>
- <p>
-     Related changes should be committed as a group, or very closely together. Half-completed projects should not be committed unless doing so is necessary to pass the baton to another developer who has agreed to complete the project in short order. All code changes must be successfully compiled on the developer's platform before being committed.
-
-</p>
- <p>
-     The current source code tree should be capable of complete compilation at all times. However, it is sometimes impossible for a developer on one platform to avoid breaking some other platform when a change is committed, particularly when completing the change requires access to a special development tool on that other platform. If it is anticipated that a given change will break some other platform, the committer must indicate that in the commit log.
-
-</p>
- <p>
-     The committer is responsible for the quality of any third-party code or documentation they commit to the repository. All software committed to the repository must be covered by the Apache LICENSE or contain a copyright and license that allows redistribution under the same conditions as the Apache LICENSE.
-
-</p>
- <p>
-     A committed change must be reversed if it is vetoed by one of the voting members and the veto conditions cannot be immediately satisfied by the equivalent of a &quot;bug fix&quot; commit. The veto must be rescinded before the change can be included in any public release.
-
-</p>
+      <p>
+        Ideas must be review-then-commit; patches can be commit-then-review. With
+        a commit-then-review process, we trust that the developer doing
+        the commit has a high degree of confidence in the change.
+        Doubtful changes, new features, and large-scale overhauls need
+        to be discussed before being committed to a repository. Any
+        change that affects the semantics of arguments to configurable
+        directives, significantly adds to the runtime size of the
+        program, or changes the semantics of an existing API function
+        must receive consensus approval on the mailing list before being
+        committed.
+      </p>
+      <p>
+        Each developer is responsible for notifying the mailing list and adding
+        an action item to STATUS when they have an idea for a new
+        feature or major change to propose for the product. The
+        distributed nature of the Apache project requires an advance
+        notice of 48 hours in order to properly review a major change --
+        consensus approval of either the concept or a specific patch is
+        required before the change can be committed. Note that a member
+        might veto the concept (with an adequate explanation), but later
+        rescind that veto if a specific patch satisfies their
+        objections. No advance notice is required to commit singular bug
+        fixes.
+      </p>
+      <p>
+        Related changes should be committed as a group, or very closely together.
+        Half-completed projects should not be committed unless doing so
+        is necessary to pass the baton to another developer who has
+        agreed to complete the project in short order. All code changes
+        must be successfully compiled on the developer's platform before
+        being committed.
+      </p>
+      <p>
+        The current source code tree should be capable of complete compilation
+        at all times. However, it is sometimes impossible for a
+        developer on one platform to avoid breaking some other platform
+        when a change is committed, particularly when completing the
+        change requires access to a special development tool on that
+        other platform. If it is anticipated that a given change will
+        break some other platform, the committer must indicate that in
+        the commit log.
+      </p>
+      <p>
+        The committer is responsible for the quality of any third-party code or
+        documentation they commit to the repository. All software
+        committed to the repository must be covered by the Apache
+        LICENSE or contain a copyright and license that allows
+        redistribution under the same conditions as the Apache LICENSE.
+      </p>
+      <p>
+        A committed change must be reversed if it is vetoed by one of the
+        voting members and the veto conditions cannot be immediately
+        satisfied by the equivalent of a &quot;bug fix&quot; commit. The veto must
+        be rescinded before the change can be included in any public
+        release.
+      </p>
     </div>
-    <div class="section"><h2>Patch Format<a name="Patch_Format"></a></h2>
-
- <p>
-     When a specific change to the software is proposed for discussion or voting on the mailing list, it should be presented in the form of input to the patch command. When sent to the mailing list, the message should contain a Subject beginning with [PATCH] and a distinctive one-line summary corresponding to the action item for that patch. Afterwords, the patch summary in the STATUS file should be updated to point to the Message-ID of that message.
-
-</p>
- <p>
-     The patch should be created by using the diff -u command from the original software file(s) to the modified software file(s). E.g.,
-</p>
-<p>
 
+    <div class="section"><h2>Patch Format<a name="Patch_Format"></a></h2>
+      <p>
+        When a specific change to the software is proposed for discussion or
+        voting on the mailing list, it should be presented in the form
+        of input to the patch command. When sent to the mailing list,
+        the message should contain a Subject beginning with [PATCH] and
+        a distinctive one-line summary corresponding to the action item
+        for that patch. Afterwords, the patch summary in the STATUS file
+        should be updated to point to the Message-ID of that message.
+      </p>
+      <p>
+        The patch should be created by using the diff -u command from the
+        original software file(s) to the modified software file(s).
+        E.g.,
+      </p>
+      <div class="source"><pre>
         diff -u James.java.orig James.java &gt;&gt; patchfile.txt
-
-</p>
- <p>
-     All patches necessary to address an action item should be concatenated within a single patch message. If later modification of the patch proves necessary, the entire new patch should be posted and not just the difference between two patches. The STATUS file entry should then be updated to point to the new patch message.
-
-</p>
- <p>
-     The completed patchfile should produce no errors or prompts when the command,
-</p>
-<p>
-
+      </pre></div>
+      <p>
+        All patches necessary to address an action item should be concatenated
+        within a single patch message. If later modification of the
+        patch proves necessary, the entire new patch should be posted
+        and not just the difference between two patches. The STATUS file
+        entry should then be updated to point to the new patch message.
+
+      </p>
+      <p>
+        The completed patchfile should produce no errors or prompts when the
+        command,
+      </p>
+      <div class="source"><pre>
         patch -s &lt; patchfile
-</p>
-<p>
-
-    is issued in the target repository.
-</p>
+      </pre></div>
+      <p>
+        is issued in the target repository.
+      </p>
     </div>
+    
   
+
 
       </div>
     </div>

Modified: james/site/trunk/www/index.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/index.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/index.html (original)
+++ james/site/trunk/www/index.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 18, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -38,7 +38,7 @@
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="James Project Web Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120418" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -78,7 +78,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-18</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -88,8 +88,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>

Modified: james/site/trunk/www/license.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/license.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/license.html (original)
+++ james/site/trunk/www/license.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -36,7 +36,7 @@
     <script type="text/javascript" src="./js/jquery/js/jquery-ui-1.8.5.custom.min.js"></script>
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -76,7 +76,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -86,8 +86,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>

Modified: james/site/trunk/www/mail.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/mail.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/mail.html (original)
+++ james/site/trunk/www/mail.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 18, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -38,7 +38,7 @@
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="James Project Web Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120418" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -78,7 +78,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-18</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -88,8 +88,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>

Modified: james/site/trunk/www/newsarchive.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/newsarchive.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/newsarchive.html (original)
+++ james/site/trunk/www/newsarchive.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 18, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -38,7 +38,7 @@
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
       <meta name="author" content="James Project Web Team" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120418" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -78,7 +78,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-18</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -88,8 +88,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>

Modified: james/site/trunk/www/project-info.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/project-info.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/project-info.html (original)
+++ james/site/trunk/www/project-info.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -36,7 +36,7 @@
     <script type="text/javascript" src="./js/jquery/js/jquery-ui-1.8.5.custom.min.js"></script>
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -76,7 +76,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -86,8 +86,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>

Modified: james/site/trunk/www/team-list.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/team-list.html?rev=1327847&r1=1327846&r2=1327847&view=diff
==============================================================================
--- james/site/trunk/www/team-list.html (original)
+++ james/site/trunk/www/team-list.html Thu Apr 19 07:15:44 2012
@@ -18,7 +18,7 @@
   under the License.    
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia at Apr 16, 2012 -->
+<!-- Generated by Apache Maven Doxia at Apr 19, 2012 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -36,7 +36,7 @@
     <script type="text/javascript" src="./js/jquery/js/jquery-ui-1.8.5.custom.min.js"></script>
     <script type="text/javascript" src="./js/fancybox/jquery.fancybox-1.3.4.js"></script>
     <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <meta name="Date-Revision-yyyymmdd" content="20120416" />
+    <meta name="Date-Revision-yyyymmdd" content="20120419" />
     <meta http-equiv="Content-Language" content="en" />
                                                     
 <link title="DOAP" rel="meta" type="application/rdf+xml" href="http://james.apache.org//doap_james-project.rdf"/>
@@ -76,7 +76,7 @@
             
                 
                 <div class="xleft">
-        <span id="publishDate">Last Published: 2012-04-16</span>
+        <span id="publishDate">Last Published: 2012-04-19</span>
                       </div>
             <div class="xright">                    <a href="index.html" title="Home">Home</a>
             |
@@ -86,8 +86,6 @@
             |
                         <a href="protocols/index.html" title="Protocols">Protocols</a>
             |
-                        <a href="imap/index.html" title="IMAP">IMAP</a>
-            |
                         <a href="mailet/index.html" title="Mailets">Mailets</a>
             |
                         <a href="mailbox/index.html" title="Mailbox">Mailbox</a>