incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c..@apache.org
Subject svn commit: r537711 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Mon, 14 May 2007 05:29:46 GMT
Author: clr
Date: Sun May 13 22:29:43 2007
New Revision: 537711

URL: http://svn.apache.org/viewvc?view=rev&rev=537711
Log:
INCUBATOR-64 minor typographical updates. Patch submitted by Martijn Dashorst

Modified:
    incubator/public/trunk/site-author/guides/graduation.xml
    incubator/public/trunk/site-publish/guides/graduation.html

Modified: incubator/public/trunk/site-author/guides/graduation.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/graduation.xml?view=diff&rev=537711&r1=537710&r2=537711
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Sun May 13 22:29:43 2007
@@ -27,8 +27,7 @@
                 <title>Status - DRAFT</title>
                 <p>
                     This document is under
-                    <a href='#help-wanted'>development</a>
-                    . At the moment, this is just an initial outline.
+                    <a href='#help-wanted'>development</a>.
                 </p>
             </section>
             <section id='TOC'><title>Contents</title><toc/></section>
@@ -73,7 +72,7 @@
                     <section id='checklist'>
                 <title>Graduation Check List</title>
                 <p>
-                    A short checklist giving an overview. Not a
+                    The following is a short checklist giving an overview, not a
                     substitute for reading the content below.
                 </p>
                 <ol>
@@ -208,13 +207,13 @@
                     original proposal may well prove acceptable. The
                     board resolution is the ultimate definition of the
                     scope of an Apache project. So, it is important that
-                    it effects the vision for the project as appear on
+                    it reflects the vision for the project as it appears on
                     the eve of graduation.
                 </p>
                 <p>
                     A good resolution is neither too narrow nor too
                     broad. If the project's scope is too narrow, then
-                    it's activities will be unnecessarily constrained.
+                    its activities will be unnecessarily constrained.
                     If a project's scope is too broad then it may lack
                     focus and suffer from governance issues.
                 </p>
@@ -274,7 +273,7 @@
                  </p>
                  <p>
 Podlings do not need to actually publish a release to demonstrate that
-they understand how to do so but creating a release that is approved
+they understand how to accomplish such a feat. However, creating a release that is approved
 by the <a href='incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29'>
 incubator project management committee</a> is 
 usually the simplest way to do this. 
@@ -305,7 +304,7 @@
             <section id='notes-community'>
                 <title>On Community</title>
                 <p>
-Apache projects are self-sustain and self-governing communities.
+Apache projects are self-sustaining and self-governing communities.
 Long term success and health requires that these communities understand how to:
                 </p>
                 <ul>
@@ -325,13 +324,13 @@
 				<p>
 Graduation tests whether (in the opinion of the 
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>)
-a podling has learnt enough and is responsible enough to sustain itself as such a community.
+a podling has learned enough and is responsible enough to sustain itself as such a community.
 				</p>
 				<section id='notes-open-and-diverse'><title>An Open And Diverse Community</title>
 				<p>
-A major criteria for graduation is to have developed an open and diverse
+A major criterion for graduation is to have developed an open and diverse
 <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community.
-Time has demonstrated that these kinds of community are more robust and productive than more
+Time has demonstrated that these kinds of communities are more robust and productive than
more
 closed ones.
 				</p> 
 				<p>
@@ -344,9 +343,9 @@
 				</p><p>
 The openness of the community is not only measured by the number of contributors. 
 Open and respectful discussions on the mailing lists are vital. Ways to resolve technical
conflict 
-without destroying personal relationships must be learn.
+without destroying personal relationships must be learned.
 				</p><p>
-Mailing lists are the lifeblood of Apache communities. They are the primary mode of discourse
+Mailing lists are the life blood of Apache communities. They are the primary mode of discourse
 and constitute a public and historic record of the project. Other forms of communication

 (P2P, F2F, personal emails and so on) are secondary. There are well founded fears about 
 use of these media for project communication. Though many projects successfully blend other

@@ -355,7 +354,7 @@
 				</p><p>
 Apache project mailing lists are public, well indexed and well archived. This allows anyone

 to monitor (both in real time and by browsing the archives) what's happening. Opinions expressed
-are public and poor behaviour risks a poster's reputation. 
+are public and poor behavior risks a poster's reputation. 
 				</p><p>
 Private communications tend to be more candid but also more likely to be ill-judged.
 Back channel communication tend to be divisive: excluding some members of the group.
@@ -371,7 +370,7 @@
 topic arises on list. Using public mailing lists to develop designs allows the 
 chance encounter of ideas which often results in innovation.
 				</p><p>
-If alternative forums are used by a project, it is important to try to minimise the 
+If alternative forums are used by a project, it is important to try to minimize the 
 chances of problems arising. All matters of substance need to be 
 moved back to the mailing lists. Public records should be kept and posted back to
 the list. Regular reminders should be posted to remind people that these other 
@@ -495,7 +494,7 @@
 					</p><p>
 Try to encourage expert users to answer questions. This may mean intentionally
 allowing a time gap before answering user questions. Encourage users to post by taking the
time
-to deal politly and positively with misunderstands 
+to deal politely and positively with misunderstands 
 and by replying to threads which have been answer well by a user to confirm that they are
right. 
 Avoid engaging in flame wars on user lists. Ignore trolls.
 					</p><p>
@@ -524,14 +523,14 @@
                 <p>
 This is the transfer of virtual resources from the care of the 
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
-to the care of either the new or existing top level project taking charge of the graudating
+to the care of either the new or existing top level project taking charge of the graduating
 community.		
 				</p>
 				<section id='existing-project-hand-over'><title>Graduating As Subproject</title>
 					<p>
 This is the simple case. The 
 <a href='/incubation/Roles_and_Responsibilities.html#Chair+of+the+Incubator+PMC'>IPMC
Chair</a>
-and the Chair of the project accepting the graduating community organise the handover
+and the Chair of the project accepting the graduating community organize the handover
 between themselves.
 					</p>
 				</section>
@@ -543,7 +542,7 @@
 members of the board will inform the appropriate chairs and 
 <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMCs</a>.
Occasionally, this will 
 be missed: if more than 72 hours has passed since the board meeting, it may be worth 
-someone posting a polite reminder to their favourite director.
+someone posting a polite reminder to their favorite director.
 					</p>
 					<p>
 The board resolution will appoint a Chair for the new project. The Chair will also be appointed
@@ -552,7 +551,7 @@
 act on behalf of Apache.  
 					</p>
 					<p>
-Once appointed, the new Chair need to:
+Once appointed, the new Chair needs to:
 					</p>
 					<ul>
 						<li>
@@ -562,7 +561,7 @@
 Subscribe to the infrastructure mailing list
 						</li>
 						<li>
-Ensure that they have been added to the pmc chairs group in svnauth
+Ensure that they have been added to the PMC chairs group in svnauth
 						</li>
 						<li>
 Review appropriate documentation:
@@ -642,7 +641,7 @@
 	need to be transferred from the Incubator to a project's new home.
 	                </p>
 	                <p>
-	 Check list:
+	 Checklist:
 	                </p>
 	                <ol>
 	                    <li>Source
@@ -658,6 +657,10 @@
 Post an announcement containing instructions for developers 
 describing how to <code>svn switch</code> their workspaces
                             </li>
+							<li>
+Update site, wikis, <code>pom.xml</code> and other resources to point to the
new repository 
+location.
+							</li>
                             </ol>
 	                    </li>
 	                    <li>
@@ -680,6 +683,10 @@
 	                                <li>
 Post an announcement to user and development lists
 	                                </li>
+									<li>
+When using Maven: update <code>pom.xml</code> for the location of the website,
as well as 
+the place where the site plugin will deploy the web site (when applicable).
+									</li>
 	                            </ol></li>
 	                            <li>Update the Incubator site
 	                                <ol>
@@ -726,13 +733,24 @@
 	                        <ol>
 	                            <li>
 	<a href='http://www.apache.org/dev/reporting-issues.html#mail'>Request</a>
-	that podlings lists are transferred to their new home. Any new mailing lists should
+	that podlings lists be transferred to their new home. Any new mailing lists should
 	be requested at the same time.
 	                            </li>
 	                            <li>
 When this has been executed by infrastructure, post an announcement to user
 and development lists
 	                            </li>
+								<li>
+When using Maven: update <code>pom.xml</code> for the new mailing list address(es).
Also update any
+documents on your website that show how to subscribe to the lists and/or find archives.
+								</li>
+								<li>
+Send notice to <a href="http://nabble.com">nabble.com</a> (if they archive your

+incubator mailing list) that the address has changed, and possibly the location 
+of your project (if it is listed as being part of the incubator). Repeat for other
+known mailing list archivers.
+								</li>
+								
 	                        </ol>
 	                    </li>
 	                    <li>Issue Tracking

Modified: incubator/public/trunk/site-publish/guides/graduation.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/graduation.html?view=diff&rev=537711&r1=537710&r2=537711
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Sun May 13 22:29:43 2007
@@ -109,8 +109,7 @@
 <div class="section-content">
 <p>
                     This document is under
-                    <a href="#help-wanted">development</a>
-                    . At the moment, this is just an initial outline.
+                    <a href="#help-wanted">development</a>.
                 </p>
 </div>
 <h3>
@@ -327,7 +326,7 @@
 </h2>
 <div class="section-content">
 <p>
-                    A short checklist giving an overview. Not a
+                    The following is a short checklist giving an overview, not a
                     substitute for reading the content below.
                 </p>
 <ol>
@@ -470,13 +469,13 @@
                     original proposal may well prove acceptable. The
                     board resolution is the ultimate definition of the
                     scope of an Apache project. So, it is important that
-                    it effects the vision for the project as appear on
+                    it reflects the vision for the project as it appears on
                     the eve of graduation.
                 </p>
 <p>
                     A good resolution is neither too narrow nor too
                     broad. If the project's scope is too narrow, then
-                    it's activities will be unnecessarily constrained.
+                    its activities will be unnecessarily constrained.
                     If a project's scope is too broad then it may lack
                     focus and suffer from governance issues.
                 </p>
@@ -549,7 +548,7 @@
                  </p>
 <p>
 Podlings do not need to actually publish a release to demonstrate that
-they understand how to do so but creating a release that is approved
+they understand how to accomplish such a feat. However, creating a release that is approved
 by the <a href="incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29">
 incubator project management committee</a> is 
 usually the simplest way to do this. 
@@ -586,7 +585,7 @@
 </h3>
 <div class="section-content">
 <p>
-Apache projects are self-sustain and self-governing communities.
+Apache projects are self-sustaining and self-governing communities.
 Long term success and health requires that these communities understand how to:
                 </p>
 <ul>
@@ -606,16 +605,16 @@
 <p>
 Graduation tests whether (in the opinion of the 
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>)
-a podling has learnt enough and is responsible enough to sustain itself as such a community.
+a podling has learned enough and is responsible enough to sustain itself as such a community.
 				</p>
 <h4>
    <a name="notes-open-and-diverse">An Open And Diverse Community</a>
 </h4>
 <div class="section-content">
 <p>
-A major criteria for graduation is to have developed an open and diverse
+A major criterion for graduation is to have developed an open and diverse
 <a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community.
-Time has demonstrated that these kinds of community are more robust and productive than more
+Time has demonstrated that these kinds of communities are more robust and productive than
more
 closed ones.
 				</p>
 <p>
@@ -629,10 +628,10 @@
 <p>
 The openness of the community is not only measured by the number of contributors. 
 Open and respectful discussions on the mailing lists are vital. Ways to resolve technical
conflict 
-without destroying personal relationships must be learn.
+without destroying personal relationships must be learned.
 				</p>
 <p>
-Mailing lists are the lifeblood of Apache communities. They are the primary mode of discourse
+Mailing lists are the life blood of Apache communities. They are the primary mode of discourse
 and constitute a public and historic record of the project. Other forms of communication

 (P2P, F2F, personal emails and so on) are secondary. There are well founded fears about 
 use of these media for project communication. Though many projects successfully blend other

@@ -642,7 +641,7 @@
 <p>
 Apache project mailing lists are public, well indexed and well archived. This allows anyone

 to monitor (both in real time and by browsing the archives) what's happening. Opinions expressed
-are public and poor behaviour risks a poster's reputation. 
+are public and poor behavior risks a poster's reputation. 
 				</p>
 <p>
 Private communications tend to be more candid but also more likely to be ill-judged.
@@ -661,7 +660,7 @@
 chance encounter of ideas which often results in innovation.
 				</p>
 <p>
-If alternative forums are used by a project, it is important to try to minimise the 
+If alternative forums are used by a project, it is important to try to minimize the 
 chances of problems arising. All matters of substance need to be 
 moved back to the mailing lists. Public records should be kept and posted back to
 the list. Regular reminders should be posted to remind people that these other 
@@ -805,7 +804,7 @@
 <p>
 Try to encourage expert users to answer questions. This may mean intentionally
 allowing a time gap before answering user questions. Encourage users to post by taking the
time
-to deal politly and positively with misunderstands 
+to deal politely and positively with misunderstands 
 and by replying to threads which have been answer well by a user to confirm that they are
right. 
 Avoid engaging in flame wars on user lists. Ignore trolls.
 					</p>
@@ -841,7 +840,7 @@
 <p>
 This is the transfer of virtual resources from the care of the 
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
-to the care of either the new or existing top level project taking charge of the graudating
+to the care of either the new or existing top level project taking charge of the graduating
 community.		
 				</p>
 <h4>
@@ -851,7 +850,7 @@
 <p>
 This is the simple case. The 
 <a href="/incubation/Roles_and_Responsibilities.html#Chair+of+the+Incubator+PMC">IPMC
Chair</a>
-and the Chair of the project accepting the graduating community organise the handover
+and the Chair of the project accepting the graduating community organize the handover
 between themselves.
 					</p>
 </div>
@@ -866,7 +865,7 @@
 members of the board will inform the appropriate chairs and 
 <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMCs</a>.
Occasionally, this will 
 be missed: if more than 72 hours has passed since the board meeting, it may be worth 
-someone posting a polite reminder to their favourite director.
+someone posting a polite reminder to their favorite director.
 					</p>
 <p>
 The board resolution will appoint a Chair for the new project. The Chair will also be appointed
@@ -875,7 +874,7 @@
 act on behalf of Apache.  
 					</p>
 <p>
-Once appointed, the new Chair need to:
+Once appointed, the new Chair needs to:
 					</p>
 <ul>
 						<li>
@@ -885,7 +884,7 @@
 Subscribe to the infrastructure mailing list
 						</li>
 						<li>
-Ensure that they have been added to the pmc chairs group in svnauth
+Ensure that they have been added to the PMC chairs group in svnauth
 						</li>
 						<li>
 Review appropriate documentation:
@@ -970,7 +969,7 @@
 	need to be transferred from the Incubator to a project's new home.
 	                </p>
 <p>
-	 Check list:
+	 Checklist:
 	                </p>
 <ol>
 	                    <li>Source
@@ -986,6 +985,10 @@
 Post an announcement containing instructions for developers 
 describing how to <code>svn switch</code> their workspaces
                             </li>
+							<li>
+Update site, wikis, <code>pom.xml</code> and other resources to point to the
new repository 
+location.
+							</li>
                             </ol>
 	                    </li>
 	                    <li>
@@ -1008,6 +1011,10 @@
 	                                <li>
 Post an announcement to user and development lists
 	                                </li>
+									<li>
+When using Maven: update <code>pom.xml</code> for the location of the website,
as well as 
+the place where the site plugin will deploy the web site (when applicable).
+									</li>
 	                            </ol></li>
 	                            <li>Update the Incubator site
 	                                <ol>
@@ -1054,13 +1061,24 @@
 	                        <ol>
 	                            <li>
 	<a href="http://www.apache.org/dev/reporting-issues.html#mail">Request</a>
-	that podlings lists are transferred to their new home. Any new mailing lists should
+	that podlings lists be transferred to their new home. Any new mailing lists should
 	be requested at the same time.
 	                            </li>
 	                            <li>
 When this has been executed by infrastructure, post an announcement to user
 and development lists
 	                            </li>
+								<li>
+When using Maven: update <code>pom.xml</code> for the new mailing list address(es).
Also update any
+documents on your website that show how to subscribe to the lists and/or find archives.
+								</li>
+								<li>
+Send notice to <a href="http://nabble.com">nabble.com</a> (if they archive your

+incubator mailing list) that the address has changed, and possibly the location 
+of your project (if it is listed as being part of the incubator). Repeat for other
+known mailing list archivers.
+								</li>
+								
 	                        </ol>
 	                    </li>
 	                    <li>Issue Tracking



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message