qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rob...@apache.org
Subject svn commit: r1135272 [3/6] - in /qpid/site/docs: ./ includes/ template/
Date Mon, 13 Jun 2011 20:48:07 GMT
Modified: qpid/site/docs/people.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/people.html?rev=1135272&r1=1135271&r2=1135272&view=diff
==============================================================================
--- qpid/site/docs/people.html (original)
+++ qpid/site/docs/people.html Mon Jun 13 20:48:06 2011
@@ -19,7 +19,6 @@
  - under the License.
  -
 -->
-
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -29,195 +28,104 @@
 
   <body>
     <div class="container">
-      <div class="header">
-        <div class="logo">
-          <h1>Apache Qpid&#8482;</h1>
-          <h2>Open Source AMQP Messaging</h2>
-        </div>
-      </div>  <!-- end of header --> 
-
-      <div class="menu_box">
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Apache Qpid</h3>
-	  <ul>
-	    <li><a href="index.html">Home</a></li>
-	    <li><a href="download.cgi">Download</a></li>
-	    <li><a href="getting_started.html">Getting Started</a></li>
-	    <li><a href="http://www.apache.org/licenses/">License</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/faq.html">FAQ</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body --> 
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Documentation</h3>
-	  <ul>
-	    <li><a href="documentation.html#doc-release">0.10 Release</a></li>
-	    <li><a href="documentation.html#doc-trunk">Trunk</a></li>
-	    <li><a href="documentation.html#doc-archives">Archive</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Community</h3>
-	  <ul>
-	    <li><a href="getting_involved.html">Getting Involved</a></li>
-	    <li><a href="source_repository.html">Source Repository</a></li>
-	    <li><a href="mailing_lists.html">Mailing Lists</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/">Wiki</a></li>
-	    <li><a href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</a></li>
-	    <li><a href="people.html">People</a></li>
-	    <li><a href="acknowledgements.html">Acknowledgements</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Developers</h3>
-	  <ul>
-	    <li><a href="https://cwiki.apache.org/qpid/building.html">Building Qpid</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/developer-pages.html">Developer
Pages</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About AMQP</h3>
-	  <ul>
-	    <li><a href="amqp.html">What is AMQP?</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About Apache</h3>
-	  <ul>
-	    <li><a href="http://www.apache.org">Home</a></li>
-	    <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
-	    <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-	    <li><a href="http://www.apache.org/security/">Security</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-      </div> <!-- end of menu_box -->
+      <!-- begin header -->
+      <!--#include virtual="/includes/header.include" -->
+      <!-- end header -->
+
+      <!-- begin menu -->
+      <!--#include virtual="/includes/menu.include" -->
+      <!-- end menu -->
 
+      <!-- begin content -->
       <div class="main_text_area">
-	<div class="main_text_area_top"></div>
-<!--
- -
- - Licensed to the Apache Software Foundation (ASF) under one
- - or more contributor license agreements.  See the NOTICE file
- - distributed with this work for additional information
- - regarding copyright ownership.  The ASF licenses this file
- - to you under the Apache License, Version 2.0 (the
- - "License"); you may not use this file except in compliance
- - with the License.  You may obtain a copy of the License at
- -
- -   http://www.apache.org/licenses/LICENSE-2.0
- -
- - Unless required by applicable law or agreed to in writing,
- - software distributed under the License is distributed on an
- - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- - KIND, either express or implied.  See the License for the
- - specific language governing permissions and limitations
- - under the License.
- -
--->
-<div class="main_text_area_body">
-  <h1>People</h1>
+        <div class="main_text_area_top"></div>
 
-  <p>This page lists some of the people who have contributed to Qpid.</p>
-
-  <h2>Committers</h2>
-  <p>The people listed below have made significant contributions to
-  Qpid by working long and hard to make quality software for the rest
-  of the world to use.</p>
-
-  <p>In addition to providing us contribuions, or being commmitters
-  some of the following people are also members of the Project
-  Management Committee (PMC). Refer to the How the ASF works for
-  details on meritocracy.</p>
-
-  <p>If you would like to contribute to Qpid please look at the Get
-  Involved page to see how you can contribute.</p>
-
-  <ul>
-    <li>Aidan Skinner</li>
-    <li>Alan Conway</li>
-    <li>Andrea Gazzarini</li>
-    <li>Andrew Kennedy</li>
-    <li>Andrew Stitcher</li>
-    <li>Arnaud Simon</li>
-    <li>Carl Trieloff</li>
-    <li>Chuck Rolke</li>
-    <li>Cliff Jansen</li>
-    <li>Gordon Sim</li>
-    <li>Jim Meyering</li>
-    <li>John O'Hara</li>
-    <li>Jonathan Robie</li>
-    <li>Justin Ross</li>
-    <li>Ken Giusti</li>
-    <li>Kim van der Riet</li>
-    <li>Lahiru Gunathilake</li>
-    <li>Manuel Teira</li>
-    <li>Marnie McCormack</li>
-    <li>Martin Ritchie</li>
-    <li>Michael Goulish</li>
-    <li>Nuno Santos</li>
-    <li>Paul Fremantle</li>
-    <li>Rafael Schloming</li>
-    <li>Rajith Attapattu</li>
-    <li>Robbie Gemmell</li>
-    <li>Robert Godfrey</li>
-    <li>Robert Greig</li>
-    <li>Rupert Smith</li>
-    <li>Steve Huston</li>
-    <li>Ted Ross</li>
-    <li>Yoav Shapira</li>
-  </ul>
-
-  <h2>Contributors</h2>
-
-
-  <p>Many thanks to the following people for providing contributions:</p>
-
-  <ul>
-    <li>Colin Crist</li>
-    <li>Bhupendra Bhardwaj</li>
-    <li>Kevin Smith</li>
-    <li>Steve Vinoski</li>
-    <li>Steven Shaw</li>
-    <li>Tomas Restrepo</li>
-  </ul>
-
-  <h2>Mentors</h2>
-
-  <p>And many thanks to our project's mentors:</p>
-
-  <ul>
-    <li>Cliff Schmidt</li>
-    <li>Craig Russell</li>
-    <li>Paul Fremantle</li>
-    <li>Yoav Shapira</li>
-    <li>Scott Deboy</li>
-  </ul>
-</div>
+        <div class="main_text_area_body">
+          <h1>People</h1>
+        
+          <p>This page lists some of the people who have contributed to Qpid.</p>
+        
+          <h2>Committers</h2>
+          <p>The people listed below have made significant contributions to
+          Qpid by working long and hard to make quality software for the rest
+          of the world to use.</p>
+        
+          <p>In addition to providing us contribuions, or being commmitters
+          some of the following people are also members of the Project
+          Management Committee (PMC). Refer to the How the ASF works for
+          details on meritocracy.</p>
+        
+          <p>If you would like to contribute to Qpid please look at the Get
+          Involved page to see how you can contribute.</p>
+        
+          <ul>
+            <li>Aidan Skinner</li>
+            <li>Alan Conway</li>
+            <li>Andrea Gazzarini</li>
+            <li>Andrew Kennedy</li>
+            <li>Andrew Stitcher</li>
+            <li>Arnaud Simon</li>
+            <li>Carl Trieloff</li>
+            <li>Chuck Rolke</li>
+            <li>Cliff Jansen</li>
+            <li>Gordon Sim</li>
+            <li>Jim Meyering</li>
+            <li>John O'Hara</li>
+            <li>Jonathan Robie</li>
+            <li>Justin Ross</li>
+            <li>Ken Giusti</li>
+            <li>Kim van der Riet</li>
+            <li>Lahiru Gunathilake</li>
+            <li>Manuel Teira</li>
+            <li>Marnie McCormack</li>
+            <li>Martin Ritchie</li>
+            <li>Michael Goulish</li>
+            <li>Nuno Santos</li>
+            <li>Paul Fremantle</li>
+            <li>Rafael Schloming</li>
+            <li>Rajith Attapattu</li>
+            <li>Robbie Gemmell</li>
+            <li>Robert Godfrey</li>
+            <li>Robert Greig</li>
+            <li>Rupert Smith</li>
+            <li>Steve Huston</li>
+            <li>Ted Ross</li>
+            <li>Yoav Shapira</li>
+          </ul>
+        
+          <h2>Contributors</h2>
+        
+        
+          <p>Many thanks to the following people for providing contributions:</p>
+        
+          <ul>
+            <li>Colin Crist</li>
+            <li>Bhupendra Bhardwaj</li>
+            <li>Kevin Smith</li>
+            <li>Steve Vinoski</li>
+            <li>Steven Shaw</li>
+            <li>Tomas Restrepo</li>
+          </ul>
+        
+          <h2>Mentors</h2>
+        
+          <p>And many thanks to our project's mentors:</p>
+        
+          <ul>
+            <li>Cliff Schmidt</li>
+            <li>Craig Russell</li>
+            <li>Paul Fremantle</li>
+            <li>Yoav Shapira</li>
+            <li>Scott Deboy</li>
+          </ul>
+        </div>
+        <div class="main_text_area_bottom"></div>
       </div>
+      <!-- end content -->
 
-      <div class="footer">
-        <p>
-          &#xA9; 2004-2011 The Apache Software Foundation.<br />
-          Apache Qpid, Qpid, Apache, the Apache feather logo, and the Apache Qpid project
logo are trademarks of The Apache Software Foundation.<br />
-          All other marks mentioned may be trademarks or registered trademarks of their respective
owners.
-        </p>
-      </div>
+      <!-- begin footer -->
+      <!--#include virtual="/includes/footer.include" -->
+      <!-- end footer -->
 
     </div>
   </body>

Propchange: qpid/site/docs/people.html
------------------------------------------------------------------------------
    svn:executable = *

Modified: qpid/site/docs/qpid_integrated_with.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/qpid_integrated_with.html?rev=1135272&r1=1135271&r2=1135272&view=diff
==============================================================================
--- qpid/site/docs/qpid_integrated_with.html (original)
+++ qpid/site/docs/qpid_integrated_with.html Mon Jun 13 20:48:06 2011
@@ -19,7 +19,6 @@
  - under the License.
  -
 -->
-
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -29,136 +28,45 @@
 
   <body>
     <div class="container">
-      <div class="header">
-        <div class="logo">
-          <h1>Apache Qpid&#8482;</h1>
-          <h2>Open Source AMQP Messaging</h2>
-        </div>
-      </div>  <!-- end of header --> 
-
-      <div class="menu_box">
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Apache Qpid</h3>
-	  <ul>
-	    <li><a href="index.html">Home</a></li>
-	    <li><a href="download.cgi">Download</a></li>
-	    <li><a href="getting_started.html">Getting Started</a></li>
-	    <li><a href="http://www.apache.org/licenses/">License</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/faq.html">FAQ</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body --> 
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Documentation</h3>
-	  <ul>
-	    <li><a href="documentation.html#doc-release">0.10 Release</a></li>
-	    <li><a href="documentation.html#doc-trunk">Trunk</a></li>
-	    <li><a href="documentation.html#doc-archives">Archive</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Community</h3>
-	  <ul>
-	    <li><a href="getting_involved.html">Getting Involved</a></li>
-	    <li><a href="source_repository.html">Source Repository</a></li>
-	    <li><a href="mailing_lists.html">Mailing Lists</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/">Wiki</a></li>
-	    <li><a href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</a></li>
-	    <li><a href="people.html">People</a></li>
-	    <li><a href="acknowledgements.html">Acknowledgements</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Developers</h3>
-	  <ul>
-	    <li><a href="https://cwiki.apache.org/qpid/building.html">Building Qpid</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/developer-pages.html">Developer
Pages</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About AMQP</h3>
-	  <ul>
-	    <li><a href="amqp.html">What is AMQP?</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About Apache</h3>
-	  <ul>
-	    <li><a href="http://www.apache.org">Home</a></li>
-	    <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
-	    <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-	    <li><a href="http://www.apache.org/security/">Security</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-      </div> <!-- end of menu_box -->
+      <!-- begin header -->
+      <!--#include virtual="/includes/header.include" -->
+      <!-- end header -->
+
+      <!-- begin menu -->
+      <!--#include virtual="/includes/menu.include" -->
+      <!-- end menu -->
 
+      <!-- begin content -->
       <div class="main_text_area">
-	<div class="main_text_area_top"></div>
-<!--
- -
- - Licensed to the Apache Software Foundation (ASF) under one
- - or more contributor license agreements.  See the NOTICE file
- - distributed with this work for additional information
- - regarding copyright ownership.  The ASF licenses this file
- - to you under the Apache License, Version 2.0 (the
- - "License"); you may not use this file except in compliance
- - with the License.  You may obtain a copy of the License at
- -
- -   http://www.apache.org/licenses/LICENSE-2.0
- -
- - Unless required by applicable law or agreed to in writing,
- - software distributed under the License is distributed on an
- - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- - KIND, either express or implied.  See the License for the
- - specific language governing permissions and limitations
- - under the License.
- -
--->
-<div class="main_text_area_body">
+        <div class="main_text_area_top"></div>
 
-  <h1><a name="QpidIntegrations-AMQPintegrations"></a>AMQP integrations
</h1>
-
-  <ul>
-    <li><a href="http://qpid.apache.org/archives/wiki/hermesjms.html" title="HermesJMS">HermesJMS</a>
      - The integration of Hermes JMS with Qpid</li>
-    <li>Twisted AMQP      - <a href="https://launchpad.net/txamqp" class="external-link"
rel="nofollow">https://launchpad.net/txamqp</a></li>
-    <li>Apache Camel      - <a href="http://activemq.apache.org/camel/amqp.html"
class="external-link" rel="nofollow">http://activemq.apache.org/camel/amqp.html</a></li>
-    <li>Apache Axis2 Java - <a href="http://wso2.org/library/3663" class="external-link"
rel="nofollow">http://wso2.org/library/3663</a></li>
-
-    <li>Apache Axis2 C    - <a href="http://ws.apache.org/axis2/c/docs/axis2c_manual.html#amqptrans"
class="external-link" rel="nofollow">http://ws.apache.org/axis2/c/docs/axis2c_manual.html#amqptrans</a></li>
-    <li>Apache Synapse</li>
-    <li>libvirt           - <a href="http://libvirt.org/" class="external-link"
rel="nofollow">http://libvirt.org/</a> Provides QMF access to visualization</li>
-    <li>Ovirt             - <a href="http://ovirt.org/" class="external-link" rel="nofollow">http://ovirt.org/</a>
QMFC - used to build management tools</li>
-
-    <li>Python web plugin - Plug-in for AMQP support from web browser</li>
-    <li>Red Hat MRG       - <a href="http://redhat.com/mrg" class="external-link"
rel="nofollow">http://redhat.com/mrg</a> Distro of Qpid with added management console
and persistence</li>
-    <li>Condor            - <a href="http://www.cs.wisc.edu/condor/" class="external-link"
rel="nofollow">http://www.cs.wisc.edu/condor/</a> QMF Agents and AMQP job routing</li>
-  </ul>
-</div>
+        <div class="main_text_area_body">
+        
+          <h1><a name="QpidIntegrations-AMQPintegrations"></a>AMQP integrations
</h1>
+        
+          <ul>
+            <li><a href="http://qpid.apache.org/archives/wiki/hermesjms.html" title="HermesJMS">HermesJMS</a>
      - The integration of Hermes JMS with Qpid</li>
+            <li>Twisted AMQP      - <a href="https://launchpad.net/txamqp" class="external-link"
rel="nofollow">https://launchpad.net/txamqp</a></li>
+            <li>Apache Camel      - <a href="http://activemq.apache.org/camel/amqp.html"
class="external-link" rel="nofollow">http://activemq.apache.org/camel/amqp.html</a></li>
+            <li>Apache Axis2 Java - <a href="http://wso2.org/library/3663" class="external-link"
rel="nofollow">http://wso2.org/library/3663</a></li>
+        
+            <li>Apache Axis2 C    - <a href="http://ws.apache.org/axis2/c/docs/axis2c_manual.html#amqptrans"
class="external-link" rel="nofollow">http://ws.apache.org/axis2/c/docs/axis2c_manual.html#amqptrans</a></li>
+            <li>Apache Synapse</li>
+            <li>libvirt           - <a href="http://libvirt.org/" class="external-link"
rel="nofollow">http://libvirt.org/</a> Provides QMF access to visualization</li>
+            <li>Ovirt             - <a href="http://ovirt.org/" class="external-link"
rel="nofollow">http://ovirt.org/</a> QMFC - used to build management tools</li>
+        
+            <li>Python web plugin - Plug-in for AMQP support from web browser</li>
+            <li>Red Hat MRG       - <a href="http://redhat.com/mrg" class="external-link"
rel="nofollow">http://redhat.com/mrg</a> Distro of Qpid with added management console
and persistence</li>
+            <li>Condor            - <a href="http://www.cs.wisc.edu/condor/" class="external-link"
rel="nofollow">http://www.cs.wisc.edu/condor/</a> QMF Agents and AMQP job routing</li>
+          </ul>
+        </div>
+        <div class="main_text_area_bottom"></div>
       </div>
+      <!-- end content -->
 
-      <div class="footer">
-        <p>
-          &#xA9; 2004-2011 The Apache Software Foundation.<br />
-          Apache Qpid, Qpid, Apache, the Apache feather logo, and the Apache Qpid project
logo are trademarks of The Apache Software Foundation.<br />
-          All other marks mentioned may be trademarks or registered trademarks of their respective
owners.
-        </p>
-      </div>
+      <!-- begin footer -->
+      <!--#include virtual="/includes/footer.include" -->
+      <!-- end footer -->
 
     </div>
   </body>

Propchange: qpid/site/docs/qpid_integrated_with.html
------------------------------------------------------------------------------
    svn:executable = *

Modified: qpid/site/docs/qpid_project_etiquette_guide.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/qpid_project_etiquette_guide.html?rev=1135272&r1=1135271&r2=1135272&view=diff
==============================================================================
--- qpid/site/docs/qpid_project_etiquette_guide.html (original)
+++ qpid/site/docs/qpid_project_etiquette_guide.html Mon Jun 13 20:48:06 2011
@@ -19,7 +19,6 @@
  - under the License.
  -
 -->
-
 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -29,200 +28,109 @@
 
   <body>
     <div class="container">
-      <div class="header">
-        <div class="logo">
-          <h1>Apache Qpid&#8482;</h1>
-          <h2>Open Source AMQP Messaging</h2>
-        </div>
-      </div>  <!-- end of header --> 
-
-      <div class="menu_box">
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Apache Qpid</h3>
-	  <ul>
-	    <li><a href="index.html">Home</a></li>
-	    <li><a href="download.cgi">Download</a></li>
-	    <li><a href="getting_started.html">Getting Started</a></li>
-	    <li><a href="http://www.apache.org/licenses/">License</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/faq.html">FAQ</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body --> 
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Documentation</h3>
-	  <ul>
-	    <li><a href="documentation.html#doc-release">0.10 Release</a></li>
-	    <li><a href="documentation.html#doc-trunk">Trunk</a></li>
-	    <li><a href="documentation.html#doc-archives">Archive</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Community</h3>
-	  <ul>
-	    <li><a href="getting_involved.html">Getting Involved</a></li>
-	    <li><a href="source_repository.html">Source Repository</a></li>
-	    <li><a href="mailing_lists.html">Mailing Lists</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/">Wiki</a></li>
-	    <li><a href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</a></li>
-	    <li><a href="people.html">People</a></li>
-	    <li><a href="acknowledgements.html">Acknowledgements</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>Developers</h3>
-	  <ul>
-	    <li><a href="https://cwiki.apache.org/qpid/building.html">Building Qpid</a></li>
-	    <li><a href="https://cwiki.apache.org/qpid/developer-pages.html">Developer
Pages</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About AMQP</h3>
-	  <ul>
-	    <li><a href="amqp.html">What is AMQP?</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-
-	<div class="menu_box_top"></div>
-	<div class="menu_box_body">
-	  <h3>About Apache</h3>
-	  <ul>
-	    <li><a href="http://www.apache.org">Home</a></li>
-	    <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
-	    <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-	    <li><a href="http://www.apache.org/security/">Security</a></li>
-	  </ul>
-	</div> <!-- end of menu_box_body -->
-	<div class="menu_box_bottom"></div>
-      </div> <!-- end of menu_box -->
+      <!-- begin header -->
+      <!--#include virtual="/includes/header.include" -->
+      <!-- end header -->
+
+      <!-- begin menu -->
+      <!--#include virtual="/includes/menu.include" -->
+      <!-- end menu -->
 
+      <!-- begin content -->
       <div class="main_text_area">
-	<div class="main_text_area_top"></div>
-<!--
- -
- - Licensed to the Apache Software Foundation (ASF) under one
- - or more contributor license agreements.  See the NOTICE file
- - distributed with this work for additional information
- - regarding copyright ownership.  The ASF licenses this file
- - to you under the Apache License, Version 2.0 (the
- - "License"); you may not use this file except in compliance
- - with the License.  You may obtain a copy of the License at
- -
- -   http://www.apache.org/licenses/LICENSE-2.0
- -
- - Unless required by applicable law or agreed to in writing,
- - software distributed under the License is distributed on an
- - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- - KIND, either express or implied.  See the License for the
- - specific language governing permissions and limitations
- - under the License.
- -
--->
-<div class="main_text_area_body">
-
-<h1>Qpid Project Etiquette Guide</h1>
-
-<h2><a name="QpidProjectEtiquetteGuide-Purpose"></a>Purpose</h2>
-
-<p>This guide, written by Rafael Schloming, gives both Qpid committers and submitters
a useful introduction to project etiquette, shedding light on how we do things &amp; why.
Following this etiquette makes the path to righteousness less long and winding !</p>
-
-<h2><a name="QpidProjectEtiquetteGuide-Maintainers"></a>Maintainers</h2>
-
-<p>The Qpid project consists of a number of major components spread across almost as
many different languages. Thus it is rare for qpid committers to be experts in every single
area of the project.</p>
-
-<p>As such it is expected that qpid committers make some effort to reach out to their
teammates before directly modifying components that are outside their chosen areas. </p>
-
-<p>You should use the dev list to reach out to Qpid developers and comment on any JIRAs
you're progressing.</p>
-
-<h2><a name="QpidProjectEtiquetteGuide-PatchSubmission"></a>Patch Submission</h2>
-
-<p>As a committer it can be difficult to decide whether/how to provide feedback when
someone submits a patch. Often it is tempting to just fix up the patch and avoid the slower
and sometimes awkward process of telling someone that they got some part of it wrong. </p>
-
-<p>However, it is necessary to ensure that those who submit patches get to learn what
they need to know in order to become a valued qpid committer.</p>
-
-<p>In that spirit, here are a few guidelines for contributing patch submissions and
how we handle them:</p>
-
-<ul>
-	<li>Submitters should produce the final patch(s) as applied to the tree. Producing
a patch that needs little or no rework is a key skill for a qpid committer.</li>
-
-	<li>Maintainers may make requests for 'trivial' updates to the patch. Such requests
are vital to ensuring that contributers	get familiar with subtle yet important aspects of
the code, stylistic conventions, etc.</li>
-
-	<li>Make sure the submitter is familiar with project etiquette so they understand
why we make seemingly trivial requests. We'll ask new contributers to read this etiquette
info for that reason !</li>
-
-	<li>A one-time patch from someone passing through may need nothing more than a polite
thank you regardless of the content. If a submitter does aim for committership, best to make
it plain you're planning to stay around on the project.</li>
-
-	<li>Break up unrelated changes. It wouldn't be considered correct for a committer
to glom together too many unrelated changes within a single commit, and so we won't commit
this kind of patch from submitters.</li>
-
-	<li>You need a JIRA for any patch to be attached to, which should accurately describe
the change.</li>
-</ul>
-
-
-<h2><a name="QpidProjectEtiquetteGuide-BigIdeas"></a>Big Ideas</h2>
-
-<p>Every so often someone has a Big Idea that they get excited about and want to go
do. They generally mail the list about it to give people the opportunity to comment, and then
when nobody says anything they go off and do it.</p>
-
-<p>Fast forward six months later they commit/merge/enable/publish the result of their
Big Idea, and suddenly everyone understands the full implications, and not everyone is happy.
</p>
-
-<h3><a name="QpidProjectEtiquetteGuide-Guidelines"></a>Guidelines</h3>
-
-<p>So, here are a few guidelines for making sure this doesn't happen, starting with
how to write a good proposal for a Big Idea:</p>
-
-<ul>
-	<li>Make sure your proposal is recognizable as a proposal. An easy way to avoid ambiguity
is to start a new thread for your proposal and stick &quot;proposal&quot; somewhere
in the subject.</li>
-
-	<li>Understand who and what your proposal effects, and make this clear. If you think
X's implementation of Y doesn't deserve to live and you're going to rewrite the whole thing
from scratch then make this very clear so X can object sooner rather than later.</li>
-
-	<li>Make sure you call out loudly that you intend to kill feature A, even if you think
no-one on earth should care.</li>
-
-	<li>Even if you're going to write an Atari emulator, and you're 100% sure that it
won't overlap with anything in the rest of the project, make sure you understand how and why
it relates to the rest of the project in general, and make that clear.</li>
-
-	<li>Be concrete. Often a proposal of the form &quot;hey, I did a little of this,
here is a proof-of-concept, I'd like to do it for real now&quot; is far more effective
than a proposal of the form &quot;hey, I have this vague idea about this, I'm going to
vaguely suggest it would be good if someone did it&quot;.</li>
-
-	<li>Talk about the long term implications of your proposal. If it's code then someone
needs to maintain it, and committers will expect this to be you. Make clear your intentions.</li>
-
-	<li>Never assume silence implies complicity, more likely it means people didn't understand
the implications of your proposal, or didn't have time to figure out why they didn't like
it. Ask again !</li>
-
-	<li>The bigger your idea is, the more time and effort you should spend on the proposal,
and ensuring that you get positive responses and deal with the comments and feedback provided
in your actual implementation.</li>
-</ul>
-
-
-<h3><a name="QpidProjectEtiquetteGuide-Talkearly%2Ctalkoften"></a>Talk
early, talk often</h3>
-
-<p>No matter how incredibly excellent your proposal is, there is going to need to be
some discussion before the result of your Big Idea is blessed. Here are some things you can
do to help that discussion go smoothly:</p>
-
-<ul>
-	<li>Make frequent progress reports. Every hour/day/week/month you spend working without
telling people what you're doing is an hour/day/week/month of your time that you risk wasting.</li>
-
-	<li>Define milestones and make them visible to the rest of the project. Just like
a concrete proof-of-concept can help a proposal, it helps to give people a concrete look at
what you're doing while it's in progress. This can go a long way towards avoiding surprises.</li>
-</ul>
-
-<h3><a name="QpidProjectEtiquetteGuide-Andfinally....."></a>And finally
.....</h3>
-
-<p>When the time does come to commit/merge/enable/publish your Big Idea, it really
shouldn't be a surprise to anyone if you've followed the steps up until now, but make sure
you let people know in advance by making note in your final few progress reports of when you
expect to be finished, and sending a note to the dev list a day or so before you flip the
big switch.</p>
-
-</div>
+        <div class="main_text_area_top"></div>
 
+        <div class="main_text_area_body">
+        
+        <h1>Qpid Project Etiquette Guide</h1>
+        
+        <h2><a name="QpidProjectEtiquetteGuide-Purpose"></a>Purpose</h2>
+        
+        <p>This guide, written by Rafael Schloming, gives both Qpid committers and
submitters a useful introduction to project etiquette, shedding light on how we do things
&amp; why. Following this etiquette makes the path to righteousness less long and winding
!</p>
+        
+        <h2><a name="QpidProjectEtiquetteGuide-Maintainers"></a>Maintainers</h2>
+        
+        <p>The Qpid project consists of a number of major components spread across
almost as many different languages. Thus it is rare for qpid committers to be experts in every
single area of the project.</p>
+        
+        <p>As such it is expected that qpid committers make some effort to reach out
to their teammates before directly modifying components that are outside their chosen areas.
</p>
+        
+        <p>You should use the dev list to reach out to Qpid developers and comment
on any JIRAs you're progressing.</p>
+        
+        <h2><a name="QpidProjectEtiquetteGuide-PatchSubmission"></a>Patch
Submission</h2>
+        
+        <p>As a committer it can be difficult to decide whether/how to provide feedback
when someone submits a patch. Often it is tempting to just fix up the patch and avoid the
slower and sometimes awkward process of telling someone that they got some part of it wrong.
</p>
+        
+        <p>However, it is necessary to ensure that those who submit patches get to
learn what they need to know in order to become a valued qpid committer.</p>
+        
+        <p>In that spirit, here are a few guidelines for contributing patch submissions
and how we handle them:</p>
+        
+        <ul>
+        	<li>Submitters should produce the final patch(s) as applied to the tree. Producing
a patch that needs little or no rework is a key skill for a qpid committer.</li>
+        
+        	<li>Maintainers may make requests for 'trivial' updates to the patch. Such
requests are vital to ensuring that contributers	get familiar with subtle yet important aspects
of the code, stylistic conventions, etc.</li>
+        
+        	<li>Make sure the submitter is familiar with project etiquette so they understand
why we make seemingly trivial requests. We'll ask new contributers to read this etiquette
info for that reason !</li>
+        
+        	<li>A one-time patch from someone passing through may need nothing more than
a polite thank you regardless of the content. If a submitter does aim for committership, best
to make it plain you're planning to stay around on the project.</li>
+        
+        	<li>Break up unrelated changes. It wouldn't be considered correct for a committer
to glom together too many unrelated changes within a single commit, and so we won't commit
this kind of patch from submitters.</li>
+        
+        	<li>You need a JIRA for any patch to be attached to, which should accurately
describe the change.</li>
+        </ul>
+        
+        
+        <h2><a name="QpidProjectEtiquetteGuide-BigIdeas"></a>Big Ideas</h2>
+        
+        <p>Every so often someone has a Big Idea that they get excited about and want
to go do. They generally mail the list about it to give people the opportunity to comment,
and then when nobody says anything they go off and do it.</p>
+        
+        <p>Fast forward six months later they commit/merge/enable/publish the result
of their Big Idea, and suddenly everyone understands the full implications, and not everyone
is happy. </p>
+        
+        <h3><a name="QpidProjectEtiquetteGuide-Guidelines"></a>Guidelines</h3>
+        
+        <p>So, here are a few guidelines for making sure this doesn't happen, starting
with how to write a good proposal for a Big Idea:</p>
+        
+        <ul>
+        	<li>Make sure your proposal is recognizable as a proposal. An easy way to
avoid ambiguity is to start a new thread for your proposal and stick &quot;proposal&quot;
somewhere in the subject.</li>
+        
+        	<li>Understand who and what your proposal effects, and make this clear. If
you think X's implementation of Y doesn't deserve to live and you're going to rewrite the
whole thing from scratch then make this very clear so X can object sooner rather than later.</li>
+        
+        	<li>Make sure you call out loudly that you intend to kill feature A, even
if you think no-one on earth should care.</li>
+        
+        	<li>Even if you're going to write an Atari emulator, and you're 100% sure
that it won't overlap with anything in the rest of the project, make sure you understand how
and why it relates to the rest of the project in general, and make that clear.</li>
+        
+        	<li>Be concrete. Often a proposal of the form &quot;hey, I did a little
of this, here is a proof-of-concept, I'd like to do it for real now&quot; is far more
effective than a proposal of the form &quot;hey, I have this vague idea about this, I'm
going to vaguely suggest it would be good if someone did it&quot;.</li>
+        
+        	<li>Talk about the long term implications of your proposal. If it's code then
someone needs to maintain it, and committers will expect this to be you. Make clear your intentions.</li>
+        
+        	<li>Never assume silence implies complicity, more likely it means people didn't
understand the implications of your proposal, or didn't have time to figure out why they didn't
like it. Ask again !</li>
+        
+        	<li>The bigger your idea is, the more time and effort you should spend on
the proposal, and ensuring that you get positive responses and deal with the comments and
feedback provided in your actual implementation.</li>
+        </ul>
+        
+        
+        <h3><a name="QpidProjectEtiquetteGuide-Talkearly%2Ctalkoften"></a>Talk
early, talk often</h3>
+        
+        <p>No matter how incredibly excellent your proposal is, there is going to need
to be some discussion before the result of your Big Idea is blessed. Here are some things
you can do to help that discussion go smoothly:</p>
+        
+        <ul>
+        	<li>Make frequent progress reports. Every hour/day/week/month you spend working
without telling people what you're doing is an hour/day/week/month of your time that you risk
wasting.</li>
+        
+        	<li>Define milestones and make them visible to the rest of the project. Just
like a concrete proof-of-concept can help a proposal, it helps to give people a concrete look
at what you're doing while it's in progress. This can go a long way towards avoiding surprises.</li>
+        </ul>
+        
+        <h3><a name="QpidProjectEtiquetteGuide-Andfinally....."></a>And
finally .....</h3>
+        
+        <p>When the time does come to commit/merge/enable/publish your Big Idea, it
really shouldn't be a surprise to anyone if you've followed the steps up until now, but make
sure you let people know in advance by making note in your final few progress reports of when
you expect to be finished, and sending a note to the dev list a day or so before you flip
the big switch.</p>
+        
+        </div>
+        
+        <div class="main_text_area_bottom"></div>
       </div>
+      <!-- end content -->
 
-      <div class="footer">
-        <p>
-          &#xA9; 2004-2011 The Apache Software Foundation.<br />
-          Apache Qpid, Qpid, Apache, the Apache feather logo, and the Apache Qpid project
logo are trademarks of The Apache Software Foundation.<br />
-          All other marks mentioned may be trademarks or registered trademarks of their respective
owners.
-        </p>
-      </div>
+      <!-- begin footer -->
+      <!--#include virtual="/includes/footer.include" -->
+      <!-- end footer -->
 
     </div>
   </body>

Propchange: qpid/site/docs/qpid_project_etiquette_guide.html
------------------------------------------------------------------------------
    svn:executable = *



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message