incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c..@apache.org
Subject svn commit: r539937 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Sun, 20 May 2007 20:59:08 GMT
Author: clr
Date: Sun May 20 13:59:08 2007
New Revision: 539937

URL: http://svn.apache.org/viewvc?view=rev&rev=539937
Log:
INCUBATOR-55 Material removed from Policy is added to guides/graduation.html

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=539937&r1=539936&r2=539937
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Sun May 20 13:59:08 2007
@@ -34,8 +34,9 @@
             <section id="abstract">
                 <title>Abstract</title>
                 <p>
-                    This document helps podlings understand the process of 
-                    graduation and offers some views about how to approach it. 
+                    The intent of this document is to help podlings 
+                    understand the process of 
+                    graduation and offer some views about how to approach it. 
                     It also links to the Incubator 
                     <a href="http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator">exit
policies</a>.
                     It is not an inflexible standard but represents a
@@ -144,7 +145,7 @@
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC (IPMC)</a>, 
 this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
-and evolve during the graduation process. As gradation approaches, this original preference
+and evolve during the graduation process. As graduation approaches, this original preference
 should be reviewed based on where the project is now.
                    </p>
                    <p>
@@ -224,7 +225,7 @@
                     The resolution should be proposed on the general
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
-                    should be started by a mentor proposing that the
+                    should be started by a member of the PPMC proposing that the
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
recommends the resolution to the board.
                 </p>
             </section>
@@ -292,7 +293,7 @@
             <section id='notes-status'>
                 <title>On The Status File</title>
                 <p>
-                The status file records and summarizes incubation related 
+                The status file records and summarizes incubation-related 
                 information on the podling.  
                 The <a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC</a>
                 is responsible for keeping this file current.
@@ -334,12 +335,12 @@
 closed ones.
 				</p> 
 				<p>
-As a project grows, it need to renew itself by accepting new committers.
+As a project grows, it needs to renew itself by accepting new committers.
 A project needs to learn how it can recruit new developers and committers into the community.
-Accepting new committers usually increases the diversity the project.
+Accepting new committers usually increases the diversity of the project.
 So, this process is very beneficial. <a href='#notes-community'>Community building</a>

 requires energy which could have been spent on code development 
-but this spending is an important investment for the future of the project.
+but this cost is an important investment for the future of the project.
 				</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 
@@ -349,15 +350,19 @@
 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

-forms of communications, care needs to taken since out-of-band communications have lead
+forms of communications, care needs to be taken since out-of-band communications have led
 to difficulties in the past. 
+The reason is that communications on other than the public mail aliases
+exclude parts of the community. Even publicly advertised IRC chats can be
+exclusionary due to time zone constraints or conflicting time commitments
+by community members who might want to participate.
 				</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 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.
+Back channel communication tend to be divisive, excluding some members of the group.
 This tends to have a corrosive effect on the collective spirit of the community. 
 Mistrust builds when opinions backed by blocks of developers arise fully formed on 
 list.
@@ -373,14 +378,14 @@
 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 
+the list. Regular reminders should be posted to remind people that other 
 secondary forms of communication exist.
 				</p><p>
 There are a limited number of topics such as security issues and discussions about people

 which are best handled in private. As much business of the project as possible should take
 place on public lists but the private list is available for those matters of a sensitive
nature.
-Good netiquette requires that permission from the poster should be sort before 
-making public posts made to a private list. 
+Good netiquette requires that permission from the poster should be sought before 
+making public, posts made to a private list. 
 Try to avoid cross-posting between public and private forums.
 Take care not to post a reply to a private post to a public forum without permission.
 				</p><p>
@@ -445,14 +450,16 @@
 committers may need to devote more time to community building and less to development.
                 	</p>
                 	<p>
-The community mailing list is open to all Apache committers. This is the right list for 
+The 
+<a href="mailto:community@apache.org">community mailing list</a> 
+is open to all Apache committers. This is the right list for 
 questions about community and on community building.
 Subscriptions should be from an Apache email address.
                 	</p>
-                	<section id='notes-profile'><title>Rising The Profile</title>
+                	<section id='notes-profile'><title>Raising The Profile</title>
 					<p>
-Sometimes, a podling is just not well enough known. There are simply not enough users
-to allow new developers to be recruited. Overcoming this means finding ways to rise 
+Sometimes, a podling is just not well-enough known. There are simply not enough users
+to allow new developers to be recruited. Overcoming this means finding ways to raise 
 the profile of the podling. Some ideas:
 					</p>
 					<ul>
@@ -494,8 +501,8 @@
 					</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 politely and positively with misunderstands 
-and by replying to threads which have been answer well by a user to confirm that they are
right. 
+to deal politely and positively with misunderstandings 
+and by replying to threads which have been answered well by a user to confirm that they are
right. 
 Avoid engaging in flame wars on user lists. Ignore trolls.
 					</p><p>
 Try to encourage users to become developers. When they give a good answer that isn't covered
@@ -513,7 +520,7 @@
 						</p>
 						<p>
 Promptly reviewing patches is important. The way that patches are applied is also important.
-Provide credit in the commit message and when close with JIRA. It's also good to encourage

+Provide credit in the commit message and when closing the JIRA. It's also good to encourage

 developers by suggesting new related work they may like to volunteer for.
 						</p>
 					</section>
@@ -766,7 +773,7 @@
 	                <title>Security</title>
 	                <p>
 	                    Each project needs to be able to manage security. By
-	                    their nature, these issue need to be dealt with in
+	                    their nature, these issues need to be dealt with in
 	                    private. These issues may either be dealt with on a
 	                    separate list or by the private list. Which list is
 	                    suitable for security issues should be noted.

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=539937&r1=539936&r2=539937
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Sun May 20 13:59:08 2007
@@ -230,7 +230,7 @@
  </a>
  <ul>
 <li><a href='#notes-profile'>
-Rising The Profile
+Raising The Profile
  </a>
 </li>
 <li><a href='#notes-recruitment'>
@@ -282,8 +282,9 @@
 </h3>
 <div class="section-content">
 <p>
-                    This document helps podlings understand the process of 
-                    graduation and offers some views about how to approach it. 
+                    The intent of this document is to help podlings 
+                    understand the process of 
+                    graduation and offer some views about how to approach it. 
                     It also links to the Incubator 
                     <a href="http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator">exit
policies</a>.
                     It is not an inflexible standard but represents a
@@ -402,7 +403,7 @@
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC (IPMC)</a>, 
 this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
-and evolve during the graduation process. As gradation approaches, this original preference
+and evolve during the graduation process. As graduation approaches, this original preference
 should be reviewed based on where the project is now.
                    </p>
 <p>
@@ -488,7 +489,7 @@
                     The resolution should be proposed on the general
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
-                    should be started by a mentor proposing that the
+                    should be started by a member of the PPMC proposing that the
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
recommends the resolution to the board.
                 </p>
 </div>
@@ -571,7 +572,7 @@
 </h3>
 <div class="section-content">
 <p>
-                The status file records and summarizes incubation related 
+                The status file records and summarizes incubation-related 
                 information on the podling.  
                 The <a href="ppmc.html#Incubator+ASF+Board+Reports">PPMC</a>
                 is responsible for keeping this file current.
@@ -618,12 +619,12 @@
 closed ones.
 				</p>
 <p>
-As a project grows, it need to renew itself by accepting new committers.
+As a project grows, it needs to renew itself by accepting new committers.
 A project needs to learn how it can recruit new developers and committers into the community.
-Accepting new committers usually increases the diversity the project.
+Accepting new committers usually increases the diversity of the project.
 So, this process is very beneficial. <a href="#notes-community">Community building</a>

 requires energy which could have been spent on code development 
-but this spending is an important investment for the future of the project.
+but this cost is an important investment for the future of the project.
 				</p>
 <p>
 The openness of the community is not only measured by the number of contributors. 
@@ -635,8 +636,12 @@
 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

-forms of communications, care needs to taken since out-of-band communications have lead
+forms of communications, care needs to be taken since out-of-band communications have led
 to difficulties in the past. 
+The reason is that communications on other than the public mail aliases
+exclude parts of the community. Even publicly advertised IRC chats can be
+exclusionary due to time zone constraints or conflicting time commitments
+by community members who might want to participate.
 				</p>
 <p>
 Apache project mailing lists are public, well indexed and well archived. This allows anyone

@@ -645,7 +650,7 @@
 				</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.
+Back channel communication tend to be divisive, excluding some members of the group.
 This tends to have a corrosive effect on the collective spirit of the community. 
 Mistrust builds when opinions backed by blocks of developers arise fully formed on 
 list.
@@ -663,15 +668,15 @@
 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 
+the list. Regular reminders should be posted to remind people that other 
 secondary forms of communication exist.
 				</p>
 <p>
 There are a limited number of topics such as security issues and discussions about people

 which are best handled in private. As much business of the project as possible should take
 place on public lists but the private list is available for those matters of a sensitive
nature.
-Good netiquette requires that permission from the poster should be sort before 
-making public posts made to a private list. 
+Good netiquette requires that permission from the poster should be sought before 
+making public, posts made to a private list. 
 Try to avoid cross-posting between public and private forums.
 Take care not to post a reply to a private post to a public forum without permission.
 				</p>
@@ -748,17 +753,19 @@
 committers may need to devote more time to community building and less to development.
                 	</p>
 <p>
-The community mailing list is open to all Apache committers. This is the right list for 
+The 
+<a href="mailto:community@apache.org">community mailing list</a> 
+is open to all Apache committers. This is the right list for 
 questions about community and on community building.
 Subscriptions should be from an Apache email address.
                 	</p>
 <h5> 
-   <a name="notes-profile">Rising The Profile</a> 
+   <a name="notes-profile">Raising The Profile</a> 
 </h5> 
 <div class="section-content">
 <p>
-Sometimes, a podling is just not well enough known. There are simply not enough users
-to allow new developers to be recruited. Overcoming this means finding ways to rise 
+Sometimes, a podling is just not well-enough known. There are simply not enough users
+to allow new developers to be recruited. Overcoming this means finding ways to raise 
 the profile of the podling. Some ideas:
 					</p>
 <ul>
@@ -804,8 +811,8 @@
 <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 politely and positively with misunderstands 
-and by replying to threads which have been answer well by a user to confirm that they are
right. 
+to deal politely and positively with misunderstandings 
+and by replying to threads which have been answered well by a user to confirm that they are
right. 
 Avoid engaging in flame wars on user lists. Ignore trolls.
 					</p>
 <p>
@@ -827,7 +834,7 @@
 						</p>
 <p>
 Promptly reviewing patches is important. The way that patches are applied is also important.
-Provide credit in the commit message and when close with JIRA. It's also good to encourage

+Provide credit in the commit message and when closing the JIRA. It's also good to encourage

 developers by suggesting new related work they may like to volunteer for.
 						</p>
 </div>
@@ -1096,7 +1103,7 @@
 <div class="section-content">
 <p>
 	                    Each project needs to be able to manage security. By
-	                    their nature, these issue need to be dealt with in
+	                    their nature, these issues need to be dealt with in
 	                    private. These issues may either be dealt with on a
 	                    separate list or by the private list. Which list is
 	                    suitable for security issues should be noted.



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


Mime
View raw message