incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r439034 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Thu, 31 Aug 2006 19:54:26 GMT
Author: rdonkin
Date: Thu Aug 31 12:54:25 2006
New Revision: 439034

URL: http://svn.apache.org/viewvc?rev=439034&view=rev
Log:
More editing. Tightened Prose.

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

Modified: incubator/public/trunk/site-author/guides/proposal.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/proposal.xml?rev=439034&r1=439033&r2=439034&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Thu Aug 31 12:54:25 2006
@@ -43,12 +43,12 @@
 <a href='/incubation/Process_Description'>process</a> decided by a vote. 
 The proposal is the document upon which the 
 <a href='/incubation/Roles_and_Responsibilities.html#Sponsor'>Sponsor</a> votes.

-So, though it's nether necessary nor sufficient to have a good proposal,
+So, though it's neither necessary nor sufficient to have a good proposal,
 a good proposal increases the chances of a positive result.
            </p>
            <p>
-The proposal is (in some ways) a manifesto. Much of the information contained 
-should be reused in the <a href='website.html'>podling website</a>. A good proposal
+The proposal is (in some ways) a manifesto. Much of the information
+will be reused in the <a href='website.html'>Podling website</a>. A good proposal
 should shape the future evolution of the project.
            </p>
         </section>
@@ -72,8 +72,8 @@
     <section id="formulating"><title>Formulating A Proposal</title>
         <section id='preparation'><title>Preparation</title>
       <p>
-Start with research. The <a href='entry.html'>incubator entry guide</a> is a
good place to start this
-process. Read the <a href='http://www.apache.org'>Apache</a> 
+Start with research. The <a href='entry.html'>incubator entry guide</a> is a
good place to start. 
+Read the <a href='http://www.apache.org'>Apache</a> 
 <a href='http://www.apache.org/foundation'>documentation</a>.
        </p>
        <p>
@@ -89,28 +89,30 @@
        <p>
 Before starting on the formal proposal, recruit a 
 <a href='/incubation/Roles_and_Responsibilities.html#Champion'>Champion</a>.
The Champion understands 
-Apache works and should be able to help navigate the process.
+Apache and should be able to help navigate the process.
        </p>
        <p>
-Review <a href='http://wiki.apache.org/incubator/'>recent proposals</a> and how
they have been received.
+Review <a href='http://wiki.apache.org/incubator/'>recent proposals</a> and how
they have been 
+<a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">received</a>.
        </p>
        <p>
 The incoming community needs to work together before presenting this
 proposal to the incubator. Think about and discuss future goals and the reasons for coming
to Apache.
+Feel free to ask questions <a href='lists.html#general+at+incubator.apache.org'>on
list</a>.
        </p>
     </section>   
        <section id='presentation'><title>Presentation</title>
             <p>
 Once the preparatory work is done, the proposal should be presented to the
-incubator.  This is done by posting the proposal
-in plain text in a email whose subject is prefixed with <code>[PROPOSAL]</code>.
+incubator.  Post the proposal in plain text in a email whose subject is prefixed 
+with <code>[PROPOSAL]</code>.
         </p>
             <p>
 If there is interest in the proposal, expect a lively debate to begin. 
 Approval is an open and 
 <a href='http://www.apache.org/foundation/voting.html'>democratic</a> 
 <a href='entry.html#understanding'>process</a>.
-So this discussion is an important part of opinion formation. A proposal
+Discussion is an important part of opinion formation. A proposal
 will require development if it is to gain the maximum level of support from the
 <a href='/incubation/whoweare.html'>electorate</a>.
         </p>
@@ -119,15 +121,15 @@
             <p>
 Expect to work on improving the template on list after presenting it. The
 <a href='http://wiki.apache.org/incubator/'>wiki</a> is an good 
-development tool. Consider creating a wiki page containing the proposal 
-content and supplying a link. Those who are interested should add themselves 
+development tool. Consider creating a wiki page containing the evolving proposal 
+content. Those who are interested should add themselves 
 to the watch list for the page so they can receive change notifications.
        </p>
             <p>
 Developing the proposal on the wiki allows easy collaboration. This has disadvantages
 as well as advantages. The wiki is just a tool to assist the easy development of the 
 final proposal (the one that will be voted upon). Not every change improves a proposal
-and there is no requirement that every change is accepted. Note that the incubator 
+and there is no requirement that every change is accepted by the proposers. Note that the
incubator 
 asks all participants to abide by appropriate <a href='participation.html'>netiquette</a>.
         </p>
             <p>
@@ -151,12 +153,10 @@
       <title>Proposal Template</title>
       <p>
 The aim of presenting a template with examples and comments is educational.
-Proposals are not required to adopt this format. Best practice evolves.
-      </p>
-      <p>
+Proposals are not required to adopt this format. 
 Every proposal is different. There may be sections which don't seem to be
 useful. It's fine to miss them out and to add new ones that the proposal seems
-to need. Innovation is acceptable.
+to need. Best practice evolves. Innovation is acceptable.
       </p>
       <p>
 The format is less important than the content. 
@@ -183,7 +183,7 @@
 The abstract should be suitable for reuse in
 the board resolution used to create the official project upon graduation,
 as the first paragraph on the podling <a href='website.html'>web site</a> 
-and as the DOAP description.
+and in the <a href='http://projects.apache.org/create.html'>DOAP</a> document.
 </p>
 <pre>
 Examples:
@@ -219,12 +219,12 @@
 <p>
 Provides context for those unfamiliar with the problem space and history. 
 </p><p>
-Explain the meaning of any terms whose meaning may be confused (for example, 
-if there is not a single widely adopted definition).
+Explain terms whose meanings may be misunderstood  (for example, 
+where there is not a single widely adopted definition).
 <p>
 </p>
 This content should be capable of being safely ignored by domain experts.
-It should probably find an eventual home on the podlng website.
+It should probably find an eventual home on the Podling website.
 </p>
 <pre>
 Example (Heraldry):
@@ -241,8 +241,7 @@
         <blockquote>
 <p>
 Explains why this project needs to exist and why should it be adopted by Apache.
-More discursive material is should be included in this section rather than in
-the <a href='#template-proposal'>proposal</a>.
+This is the right place for discursive material.
 </p>
 <pre>
 Example (Beehive):
@@ -259,7 +258,7 @@
         	<blockquote>
 <p>
 A complex proposal (involving multiple existing code bases, for example)
-may cause concerns that the proposal may not be practical. A good way
+may cause concerns about its practicality. A good way
 to address these concerns is to create a plan that demonstrates the proposal
 is feasible and has been carefully thought through.
 </p>
@@ -285,16 +284,16 @@
 <p>
 This section (and the contained topics) describes
 the candidate's current status and development practices.
-This should be an honest accessment balancing these against Apache's 
+This should be an honest assessment balancing these against Apache's 
 <a href='http://www.apache.org/foundation/'>principles</a> and 
 <a href='http://www.apache.org/foundation/how-it-works.html#management'>development
ideals</a>. 
 </p><p>
 For some proposals, this is a chance to demonstrate understanding 
 of the issues that will need to addressed before graduation.
-For others, this is a chance to highlight the close match with Apache.
-Proposals without an inital codebase should just simply state that.
+For others, this is a chance to highlight the close match with Apache that already exists.
+Proposals without an initial codebase should just simply state that.
 </p><p>
-Some proposals name this section <em>criteria</em> though the term is a little
misleading.
+Some proposals name this section <em>criteria</em> (though the term is a little
misleading).
 </p>
         	</blockquote>
         <section id='template-meritocracy'><title>Meritocracy</title>
@@ -309,7 +308,7 @@
 		</p>
 		<p>
 This process of renewal is vital to the long term health of Apache projects.  
-This is the right place to demonstrate that this is understood 
+This is the right place to demonstrate that this process is understood 
 by the proposers.
         </p>
         <pre>
@@ -369,7 +368,7 @@
 		<p>
 It is useful to provide a brief introduction to the developers on the 
 <a href='#template-initial-committers'>initial committers</a> list.
-This is best done here (and not in that section). This may be used to discuss 
+This is best done here (and not in that section). This section may be used to discuss 
 the diversity of the core development team.
         </p>
  <pre>
@@ -390,7 +389,7 @@
         	<blockquote>
         <p>
 Describe why Apache is a good match for the proposal.
-An opertunity to highlight links with Apache 
+An opportunity to highlight links with Apache 
 <a href='http://projects.apache.org'>projects</a>
 and <a href='http://www.apache.org/foundation/how-it-works.html'>development philosophy</a>.
         </p>
@@ -422,7 +421,7 @@
 A public commitment to future development. 
 			</p><p>
 Recruiting a diverse development community and strong user base takes time. 
-Apache needs to be confident that those already working on the product are still committed.
+Apache needs to be confident that the proposers are committed.
             </p>
 <pre>
 Example (Yoko):
@@ -448,7 +447,7 @@
 Successfully opening up a closed project means an investment of energy by all involved. 
 It requires a willingness to learn and to give back to the community. If the proposal is
based
 around a closed project and comes with very little understand of the open source space,
-then acknowledge this and demonstrate these qualities.
+then acknowledge this and demonstrate a willingness to learn.
 		</p>
  <pre>
 Example (Cayenne):
@@ -466,7 +465,7 @@
             <blockquote>
                 <p>
 Healthy projects need a mix of developers. Open development requires a commitment 
-to encouraging a diverse mixture. There is also an art to working as part of 
+to encouraging a diverse mixture. This includes the art of working as part of 
 a geographically scattered group in a distributed environment. 
                 </p>
                 <p>
@@ -510,20 +509,19 @@
         <section id='template-other-producrs'><title>Relationships with Other
Apache Products</title>  
             <blockquote>
                 <p>
-Apache projects to be open to collaboration with other open source projects both 
+Apache projects should be open to collaboration with other open source projects both 
 within Apache and without. Candidates should be willing to reach outside their own little
bubbles.
 				</p><p>
-This is a an opertunity to talk about existing links. It is also the right place to 
+This is a an opportunity to talk about existing links. It is also the right place to 
 talk about potential future links and plans.
                 </p><p>
 Apache allows different projects to have competing or overlapping goals. However, this should

-mean friendly competition with coorporation whenever this makes sense. Competition between
code
-but cordial coorporation between communities.
+mean friendly competition between codebases and cordial cooperation between communities.
                 </p><p>
 It is not always obvious whether a candidate is a direct competitor to an existing
-project, an indirect competitor (same problem space, different ecological niche) or just

-peers with some overlap. So, it's best to note this. In the case of indirect competition,
it is 
-important that the abstract describes accurately the niche. Competitors should expect 
+project, an indirect competitor (same problem space, different ecological niche) or are just

+peers with some overlap. In the case of indirect competition, it is 
+important that the abstract describes accurately the niche. Direct competitors should expect

 to be asked to summarize architectural differences and similarities to existing projects.
 				</p>
 <pre>
@@ -687,10 +685,11 @@
 and user lists as they become necessary.
                 </p><p>
 Existing open source projects moving to Apache will probably want to adopt the
-same mailing list set up here as they have already. However, the transition for users may
-prove more smooth if only the development lists are bootstrapped. The user
-lists can then be migrated (by a simple podling vote) once the Apache infrastructure 
-is ready and fully prepared.
+same mailing list set up here as they have already. However, there is no necessity
+that all mailing lists be created during bootstrapping. New mailing lists can be
+<a href='http://www.apache.org/dev/reporting-issues.html#mail'>added</a> 
+by a <a href='http://www.apache.org/foundation/voting.html'>VOTE</a> 
+on the Podling list. 
                 </p>
                 <p>
 It is conventional to use an all lower case, dash-separated (<code>-</code>)
 prefix
@@ -709,7 +708,7 @@
         <blockquote>
         	<p>
 It is conventional to use all lower case, dash-separated (<code>-</code>) directory
names.
-The directory should be within the incubatory directory space 
+The directory should be within the incubator directory space 
 (<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
         	</p>
 <pre>
@@ -733,15 +732,16 @@
         </section>
         <section id='template-other-resources'><title>Other Resources</title>
             <blockquote>
+            	<p>
+Describe here any other special infrastructure requirements necessary for the proposal.
+Note that the infrastructure team usually requires a compelling argument
+before new services are allowed on core hardware. Most proposal do not require this section.
+            	</p>
                 <p>
-Other standard resources such as continuous integration and so on should be
-added by the Podling later in the usual way (by vote on list) as momentum is gained. 
+Most standard resources not covered above (such as continuous integration) 
+should be added after bootstrapping. 
 The <a href='http://www.apache.org/dev'>infrastructure documentation</a> explains

 the process.
-                </p><p>
-Describe here any other special infrastructure requirements that the project has initially.
-The infrastructure team usually requires a compelling argument
-before new services are allowed on core hardware.
                 </p>
                 </blockquote>
             </section>
@@ -749,11 +749,11 @@
         <section id='template-initial-committers'><title>Initial Committers</title>
             <blockquote>
                 <p>
-        List of committers used to bootstrap the community. Mark each which has
-submitted a <a href='http://www.apache.org/licenses/#clas'>contributor license agreement</a>

-(CLA). Please list name and an email address.
-Existing committers should use their <code>apache.org</code> (since they
-require only appropriate karma for their existing account).
+List of committers (stating name and an email address) used to bootstrap the community. 
+Mark each which has submitted a 
+<a href='http://www.apache.org/licenses/#clas'>contributor license agreement</a>
(CLA). 
+Existing committers should use their <code>apache.org</code> email address (since
they
+require only appropriate karma).
             </p>
                 <p>
 It is a good idea to submit CLAs at the same time as the proposal. 
@@ -789,7 +789,7 @@
 any current affiliations which may effect their perceived independence to be 
 listed openly at the start. 
                 </p><p>
-For example, those in a salaried positions whose job is to work on the
+For example, those in salaried positions whose job is to work on the
 project should list their affiliation. Having this list helps to judge how
 much diversity exists in the initial list and so how much work there is to
 do.
@@ -825,17 +825,17 @@
                 </p>
                     <p>
 It is common for additional Mentors to <a href='partication.html#mentor'>volunteer</a>
their services
-during the development of the proposal. The number of mentors a podling can have is limited
only by the
+during the development of the proposal. The number of mentors for a Podling is limited only
by the
 energy and interest of those eligible to Mentor. Three Mentors gives a quorum and allows

-a podling more autonomy. The current consensus is that three or more Mentors will make the
+a Podling more autonomy. The current consensus is that three or more Mentors will make the
 incubation process run more smoothly.
                 </p>
                 <p>
 Note that since Mentors are appointed by the 
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>
 Incubator PMC</a> 
-as part of the acceptance process, they have no formal role before the proposal 
-is submitted. But informal enthusiasm from nominee Mentors is taken as a good sign.
+at the end of the acceptance process, they have no formal role until the proposal is accepted.

+But informal enthusiasm from nominee Mentors is taken as a good sign.
 				</p>
                 </blockquote>
             </section>
@@ -843,7 +843,7 @@
                 <blockquote>
                         <p>
 The <a href='/incubation/Roles_and_Responsibility.html#Sponsor'>Sponsor</a> 
-is the organisational unit within Apache taking responsibility for this proposal.
+is the organizational unit within Apache taking responsibility for this proposal.
 The sponsoring entity can be:
 </p>
 <ul>
@@ -856,7 +856,7 @@
 proposal asks that the incubator PMC to act as sponsor.
                 </p>
                 <p>
-Note that the final destination within the Apache organisational structure
+Note that the final destination within the Apache organizational structure
 will be decided upon graduation.
                 </p>
                 </blockquote>

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?rev=439034&r1=439033&r2=439034&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Thu Aug 31 12:54:25 2006
@@ -110,12 +110,12 @@
 <a href="/incubation/Process_Description">process</a> decided by a vote. 
 The proposal is the document upon which the 
 <a href="/incubation/Roles_and_Responsibilities.html#Sponsor">Sponsor</a> votes.

-So, though it's nether necessary nor sufficient to have a good proposal,
+So, though it's neither necessary nor sufficient to have a good proposal,
 a good proposal increases the chances of a positive result.
            </p>
 <p>
-The proposal is (in some ways) a manifesto. Much of the information contained 
-should be reused in the <a href="website.html">podling website</a>. A good proposal
+The proposal is (in some ways) a manifesto. Much of the information
+will be reused in the <a href="website.html">Podling website</a>. A good proposal
 should shape the future evolution of the project.
            </p>
 </div>
@@ -150,8 +150,8 @@
 </h3>
 <div class="section-content">
 <p>
-Start with research. The <a href="entry.html">incubator entry guide</a> is a
good place to start this
-process. Read the <a href="http://www.apache.org">Apache</a> 
+Start with research. The <a href="entry.html">incubator entry guide</a> is a
good place to start. 
+Read the <a href="http://www.apache.org">Apache</a> 
 <a href="http://www.apache.org/foundation">documentation</a>.
        </p>
 <p>
@@ -167,14 +167,16 @@
 <p>
 Before starting on the formal proposal, recruit a 
 <a href="/incubation/Roles_and_Responsibilities.html#Champion">Champion</a>.
The Champion understands 
-Apache works and should be able to help navigate the process.
+Apache and should be able to help navigate the process.
        </p>
 <p>
-Review <a href="http://wiki.apache.org/incubator/">recent proposals</a> and how
they have been received.
+Review <a href="http://wiki.apache.org/incubator/">recent proposals</a> and how
they have been 
+<a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">received</a>.
        </p>
 <p>
 The incoming community needs to work together before presenting this
 proposal to the incubator. Think about and discuss future goals and the reasons for coming
to Apache.
+Feel free to ask questions <a href="lists.html#general+at+incubator.apache.org">on
list</a>.
        </p>
 </div>
 <h3>
@@ -183,15 +185,15 @@
 <div class="section-content">
 <p>
 Once the preparatory work is done, the proposal should be presented to the
-incubator.  This is done by posting the proposal
-in plain text in a email whose subject is prefixed with <code>[PROPOSAL]</code>.
+incubator.  Post the proposal in plain text in a email whose subject is prefixed 
+with <code>[PROPOSAL]</code>.
         </p>
 <p>
 If there is interest in the proposal, expect a lively debate to begin. 
 Approval is an open and 
 <a href="http://www.apache.org/foundation/voting.html">democratic</a> 
 <a href="entry.html#understanding">process</a>.
-So this discussion is an important part of opinion formation. A proposal
+Discussion is an important part of opinion formation. A proposal
 will require development if it is to gain the maximum level of support from the
 <a href="/incubation/whoweare.html">electorate</a>.
         </p>
@@ -203,15 +205,15 @@
 <p>
 Expect to work on improving the template on list after presenting it. The
 <a href="http://wiki.apache.org/incubator/">wiki</a> is an good 
-development tool. Consider creating a wiki page containing the proposal 
-content and supplying a link. Those who are interested should add themselves 
+development tool. Consider creating a wiki page containing the evolving proposal 
+content. Those who are interested should add themselves 
 to the watch list for the page so they can receive change notifications.
        </p>
 <p>
 Developing the proposal on the wiki allows easy collaboration. This has disadvantages
 as well as advantages. The wiki is just a tool to assist the easy development of the 
 final proposal (the one that will be voted upon). Not every change improves a proposal
-and there is no requirement that every change is accepted. Note that the incubator 
+and there is no requirement that every change is accepted by the proposers. Note that the
incubator 
 asks all participants to abide by appropriate <a href="participation.html">netiquette</a>.
         </p>
 <p>
@@ -240,12 +242,10 @@
 <div class="section-content">
 <p>
 The aim of presenting a template with examples and comments is educational.
-Proposals are not required to adopt this format. Best practice evolves.
-      </p>
-<p>
+Proposals are not required to adopt this format. 
 Every proposal is different. There may be sections which don't seem to be
 useful. It's fine to miss them out and to add new ones that the proposal seems
-to need. Innovation is acceptable.
+to need. Best practice evolves. Innovation is acceptable.
       </p>
 <p>
 The format is less important than the content. 
@@ -277,7 +277,7 @@
 The abstract should be suitable for reuse in
 the board resolution used to create the official project upon graduation,
 as the first paragraph on the podling <a href="website.html">web site</a> 
-and as the DOAP description.
+and in the <a href="http://projects.apache.org/create.html">DOAP</a> document.
 </p>
 <pre>
 Examples:
@@ -319,12 +319,12 @@
 <p>
 Provides context for those unfamiliar with the problem space and history. 
 </p><p>
-Explain the meaning of any terms whose meaning may be confused (for example, 
-if there is not a single widely adopted definition).
+Explain terms whose meanings may be misunderstood  (for example, 
+where there is not a single widely adopted definition).
 <p>
 </p>
 This content should be capable of being safely ignored by domain experts.
-It should probably find an eventual home on the podlng website.
+It should probably find an eventual home on the Podling website.
 </p>
 <pre>
 Example (Heraldry):
@@ -344,8 +344,7 @@
 <blockquote>
 <p>
 Explains why this project needs to exist and why should it be adopted by Apache.
-More discursive material is should be included in this section rather than in
-the <a href="#template-proposal">proposal</a>.
+This is the right place for discursive material.
 </p>
 <pre>
 Example (Beehive):
@@ -365,7 +364,7 @@
 <blockquote>
 <p>
 A complex proposal (involving multiple existing code bases, for example)
-may cause concerns that the proposal may not be practical. A good way
+may cause concerns about its practicality. A good way
 to address these concerns is to create a plan that demonstrates the proposal
 is feasible and has been carefully thought through.
 </p>
@@ -394,16 +393,16 @@
 <p>
 This section (and the contained topics) describes
 the candidate's current status and development practices.
-This should be an honest accessment balancing these against Apache's 
+This should be an honest assessment balancing these against Apache's 
 <a href="http://www.apache.org/foundation/">principles</a> and 
 <a href="http://www.apache.org/foundation/how-it-works.html#management">development
ideals</a>. 
 </p><p>
 For some proposals, this is a chance to demonstrate understanding 
 of the issues that will need to addressed before graduation.
-For others, this is a chance to highlight the close match with Apache.
-Proposals without an inital codebase should just simply state that.
+For others, this is a chance to highlight the close match with Apache that already exists.
+Proposals without an initial codebase should just simply state that.
 </p><p>
-Some proposals name this section <em>criteria</em> though the term is a little
misleading.
+Some proposals name this section <em>criteria</em> (though the term is a little
misleading).
 </p>
         	</blockquote>
 <h5> 
@@ -421,7 +420,7 @@
 		</p>
 		<p>
 This process of renewal is vital to the long term health of Apache projects.  
-This is the right place to demonstrate that this is understood 
+This is the right place to demonstrate that this process is understood 
 by the proposers.
         </p>
         <pre>
@@ -487,7 +486,7 @@
 		<p>
 It is useful to provide a brief introduction to the developers on the 
 <a href="#template-initial-committers">initial committers</a> list.
-This is best done here (and not in that section). This may be used to discuss 
+This is best done here (and not in that section). This section may be used to discuss 
 the diversity of the core development team.
         </p>
  <pre>
@@ -511,7 +510,7 @@
 <blockquote>
         <p>
 Describe why Apache is a good match for the proposal.
-An opertunity to highlight links with Apache 
+An opportunity to highlight links with Apache 
 <a href="http://projects.apache.org">projects</a>
 and <a href="http://www.apache.org/foundation/how-it-works.html">development philosophy</a>.
         </p>
@@ -549,7 +548,7 @@
 A public commitment to future development. 
 			</p><p>
 Recruiting a diverse development community and strong user base takes time. 
-Apache needs to be confident that those already working on the product are still committed.
+Apache needs to be confident that the proposers are committed.
             </p>
 <pre>
 Example (Yoko):
@@ -578,7 +577,7 @@
 Successfully opening up a closed project means an investment of energy by all involved. 
 It requires a willingness to learn and to give back to the community. If the proposal is
based
 around a closed project and comes with very little understand of the open source space,
-then acknowledge this and demonstrate these qualities.
+then acknowledge this and demonstrate a willingness to learn.
 		</p>
  <pre>
 Example (Cayenne):
@@ -599,7 +598,7 @@
 <blockquote>
                 <p>
 Healthy projects need a mix of developers. Open development requires a commitment 
-to encouraging a diverse mixture. There is also an art to working as part of 
+to encouraging a diverse mixture. This includes the art of working as part of 
 a geographically scattered group in a distributed environment. 
                 </p>
                 <p>
@@ -649,20 +648,19 @@
 <div class="section-content">
 <blockquote>
                 <p>
-Apache projects to be open to collaboration with other open source projects both 
+Apache projects should be open to collaboration with other open source projects both 
 within Apache and without. Candidates should be willing to reach outside their own little
bubbles.
 				</p><p>
-This is a an opertunity to talk about existing links. It is also the right place to 
+This is a an opportunity to talk about existing links. It is also the right place to 
 talk about potential future links and plans.
                 </p><p>
 Apache allows different projects to have competing or overlapping goals. However, this should

-mean friendly competition with coorporation whenever this makes sense. Competition between
code
-but cordial coorporation between communities.
+mean friendly competition between codebases and cordial cooperation between communities.
                 </p><p>
 It is not always obvious whether a candidate is a direct competitor to an existing
-project, an indirect competitor (same problem space, different ecological niche) or just

-peers with some overlap. So, it's best to note this. In the case of indirect competition,
it is 
-important that the abstract describes accurately the niche. Competitors should expect 
+project, an indirect competitor (same problem space, different ecological niche) or are just

+peers with some overlap. In the case of indirect competition, it is 
+important that the abstract describes accurately the niche. Direct competitors should expect

 to be asked to summarize architectural differences and similarities to existing projects.
 				</p>
 <pre>
@@ -850,10 +848,11 @@
 and user lists as they become necessary.
                 </p><p>
 Existing open source projects moving to Apache will probably want to adopt the
-same mailing list set up here as they have already. However, the transition for users may
-prove more smooth if only the development lists are bootstrapped. The user
-lists can then be migrated (by a simple podling vote) once the Apache infrastructure 
-is ready and fully prepared.
+same mailing list set up here as they have already. However, there is no necessity
+that all mailing lists be created during bootstrapping. New mailing lists can be
+<a href="http://www.apache.org/dev/reporting-issues.html#mail">added</a> 
+by a <a href="http://www.apache.org/foundation/voting.html">VOTE</a> 
+on the Podling list. 
                 </p>
                 <p>
 It is conventional to use an all lower case, dash-separated (<code>-</code>)
 prefix
@@ -875,7 +874,7 @@
 <blockquote>
         	<p>
 It is conventional to use all lower case, dash-separated (<code>-</code>) directory
names.
-The directory should be within the incubatory directory space 
+The directory should be within the incubator directory space 
 (<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
         	</p>
 <pre>
@@ -905,15 +904,16 @@
 </h5> 
 <div class="section-content">
 <blockquote>
+            	<p>
+Describe here any other special infrastructure requirements necessary for the proposal.
+Note that the infrastructure team usually requires a compelling argument
+before new services are allowed on core hardware. Most proposal do not require this section.
+            	</p>
                 <p>
-Other standard resources such as continuous integration and so on should be
-added by the Podling later in the usual way (by vote on list) as momentum is gained. 
+Most standard resources not covered above (such as continuous integration) 
+should be added after bootstrapping. 
 The <a href="http://www.apache.org/dev">infrastructure documentation</a> explains

 the process.
-                </p><p>
-Describe here any other special infrastructure requirements that the project has initially.
-The infrastructure team usually requires a compelling argument
-before new services are allowed on core hardware.
                 </p>
                 </blockquote>
 </div>
@@ -924,11 +924,11 @@
 <div class="section-content">
 <blockquote>
                 <p>
-        List of committers used to bootstrap the community. Mark each which has
-submitted a <a href="http://www.apache.org/licenses/#clas">contributor license agreement</a>

-(CLA). Please list name and an email address.
-Existing committers should use their <code>apache.org</code> (since they
-require only appropriate karma for their existing account).
+List of committers (stating name and an email address) used to bootstrap the community. 
+Mark each which has submitted a 
+<a href="http://www.apache.org/licenses/#clas">contributor license agreement</a>
(CLA). 
+Existing committers should use their <code>apache.org</code> email address (since
they
+require only appropriate karma).
             </p>
                 <p>
 It is a good idea to submit CLAs at the same time as the proposal. 
@@ -967,7 +967,7 @@
 any current affiliations which may effect their perceived independence to be 
 listed openly at the start. 
                 </p><p>
-For example, those in a salaried positions whose job is to work on the
+For example, those in salaried positions whose job is to work on the
 project should list their affiliation. Having this list helps to judge how
 much diversity exists in the initial list and so how much work there is to
 do.
@@ -1012,17 +1012,17 @@
                 </p>
                     <p>
 It is common for additional Mentors to <a href="partication.html#mentor">volunteer</a>
their services
-during the development of the proposal. The number of mentors a podling can have is limited
only by the
+during the development of the proposal. The number of mentors for a Podling is limited only
by the
 energy and interest of those eligible to Mentor. Three Mentors gives a quorum and allows

-a podling more autonomy. The current consensus is that three or more Mentors will make the
+a Podling more autonomy. The current consensus is that three or more Mentors will make the
 incubation process run more smoothly.
                 </p>
                 <p>
 Note that since Mentors are appointed by the 
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">
 Incubator PMC</a> 
-as part of the acceptance process, they have no formal role before the proposal 
-is submitted. But informal enthusiasm from nominee Mentors is taken as a good sign.
+at the end of the acceptance process, they have no formal role until the proposal is accepted.

+But informal enthusiasm from nominee Mentors is taken as a good sign.
 				</p>
                 </blockquote>
 </div>
@@ -1033,7 +1033,7 @@
 <blockquote>
                         <p>
 The <a href="/incubation/Roles_and_Responsibility.html#Sponsor">Sponsor</a> 
-is the organisational unit within Apache taking responsibility for this proposal.
+is the organizational unit within Apache taking responsibility for this proposal.
 The sponsoring entity can be:
 </p>
 <ul>
@@ -1046,7 +1046,7 @@
 proposal asks that the incubator PMC to act as sponsor.
                 </p>
                 <p>
-Note that the final destination within the Apache organisational structure
+Note that the final destination within the Apache organizational structure
 will be decided upon graduation.
                 </p>
                 </blockquote>



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


Mime
View raw message