incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r429393 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Mon, 07 Aug 2006 17:10:09 GMT
Author: rdonkin
Date: Mon Aug  7 10:10:08 2006
New Revision: 429393

URL: http://svn.apache.org/viewvc?rev=429393&view=rev
Log:
Editing

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=429393&r1=429392&r2=429393&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Mon Aug  7 10:10:08 2006
@@ -32,21 +32,22 @@
           <p>
 This document is descriptive not normative. It describes ways to go about
 drawing up a proposal for submission. It is not an inflexible standard but
-respresents a consensus condensed from previous discussions on the
+represents a consensus condensed from previous discussions on the
 incubator general list.
           </p>
         </section>
         <section id="background">
           <title>Background</title>
           <p>
-Entry to the incubator is a democractic process. The incubator pmc votes on
-whether to accept or not. The proposal is the document upon which the pmc
-votes. So, though it's not necessary or sufficient to have a good proposal,
-a good proposal document will increase the chances of a positive result.
+<a href='entry.html'>Entry</a> to the incubator is a democratic 
+<a href='/incubation/Process_Description'>process</a>. 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,
+a good proposal document increases the chances of a positive result.
            </p>
            <p>
 The proposal is (in some ways) a manifesto. It should shape the evolution of
-the product at apache. A lot of the information contained should be included
+the product at Apache. A lot of the information it contains should be included
 in the initial project website.
            </p>
         </section>
@@ -61,40 +62,41 @@
     <section id="formulating"><title>Formulating A Proposal</title>
         <section id='preparation'><title>Preparation</title>
       <p>
-Start by RTFM. The Entry To The incubator is a good place to start this
-process.
+Start with research. The <a href='entry.html'>incubator entry guide</a>is a good
place to start this
+process. Also read the <a href='http://www.apache.org'>Apache</a> 
+<a href='http://www.apache.org/foundation'>documentation</a>.
        </p>
        <p>
-Subscribe to general@incubator.apache.org. Spend some time reviewing the 
-mailing lists archives . The mailing lists are the canonical form of
-communication and decision making at Apache. The documentation represents
+<a href='lists.html'>Subscribe</a> to <code>general.AT.incubator.apache.org</code>.

+Spend some time reviewing the 
+<a href='http://mail-archives.apache.org/mod_mbox/incubator-general/'>mailing lists
archives</a>. 
+The mailing lists are the canonical form of communication and decision making at Apache.
The documentation is
 an attempt to codify the consensus formed on list.
        </p>
        <p>
-Before drawing up a lengthy proposal, recruit a champion. [links to other
-documentation explaning role of champion] The champion knows how Apache work
-and should be able to help navigate the process.
+Before drawing up a lengthy proposal, recruit a 
+<a href='/incubation/Roles_and_Responsibilities.html#Champion'>Champion</a>.
The Champion knows 
+how Apache works and should be able to help to navigate the process.
        </p>
        <p>
-Review recent proposals [links to the wiki] and how they have been received.
+Review <a href='http://wiki.apache.org/incubator/'>recent proposals</a> and how
they have been received.
        </p>
        <p>
 The incoming community needs to work together before presenting this
-proposal to
-the incubator. Think about goals and about the reasons for coming to apache.
+proposal to the incubator. Think about goals and about the reasons for coming to Apache.
        </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 [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
-about the proposal. Approval is an open and democractic 
+about the proposal. Approval is an open and democratic 
 <a href='entry.html#understanding'>process</a>
-so discussion is an important part of opinion forming. Every proposal
+so this discussion is an important part of opinion forming. Every proposal
 will require development if it is to gain the maximum level of support from the
 electorate.
         </p>
@@ -103,7 +105,7 @@
             <p>
 Expect to work on improving the template on list after presenting it. The
 wiki is an excellent way to develop a proposal. Consider creating a wiki
-page containing the same content and supplying a link. Interested parties
+page containing the proposal content and supplying a link. Interested parties
 may wish to add themselves to the watch list for the page so that received
 email notifications when the page is changed.
        </p>
@@ -112,12 +114,12 @@
 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 any change is accepted. Note that the incubator 
-asks all participants to abide by appopriate <a href='participation.html'>netiquette</a>.
+asks all participants to abide by appropriate <a href='participation.html'>netiquette</a>.
         </p>
             <p>
 Effective management of this development is an exercise in community building. 
-The wiki is not an appropriate forum for debating changing. Discussion should be
-gently moved onto the appropriate mailing list.
+The wiki is not an appropriate forum for debating changes. Discussion should be
+gently moved onto the appropriate mailing list. 
         </p>
     </section>
         <section id='vote'><title>The Vote</title>
@@ -126,7 +128,7 @@
 proposal can be put to the vote. If the wiki is used to develop the proposal,
 please ensure that the wiki matches the final proposal then add a notice to 
 the wiki that development of the document is now complete. 
-See <a href='entry.html#'>this</a>.
+See <a href='entry.html#vote'>this</a>.
         </p>
     </section>
 </section>
@@ -216,7 +218,7 @@
         <section id='template-rationale'><title>Rationale</title>
         <blockquote>
 <p>
-Why does this project need to exist and why should it be adopted by apache?
+Why does this project need to exist and why should it be adopted by Apache?
 <p>
 </p>
 More discursive material is probably better in this section rather than in
@@ -235,7 +237,7 @@
 <p>
 Only include this section if it is not obvious. If the proposal is complex
 (probably involving multiple code bases) then people may worry about it's
-practicallity and whether it may drag in too much Apache energy. 
+practicality and whether it may drag in too much Apache energy. 
 <p>
 </p>
 This is a good place to explain the plan and demonstrate that the proposal
@@ -262,7 +264,7 @@
 <p>
 Questions are often asked about the current status of the constituent codebases
 and current development practices.
-It is sometimes useful to prempt these questions by stating honestly
+It is sometimes useful to preempt these questions by stating honestly
 where how these balance up against principles and ideals. 
 Some proposals describe this section as criteria.
 </p><p>
@@ -298,14 +300,14 @@
 <p>
 An exercise in self-knowledge.
 Risks don't mean that a project is unacceptable.
-It is useful to collect together material prempting questions about possible risks.
+It is useful to collect together material preempting questions about possible risks.
 </p>
         </blockquote>
         <section id='template-orphaned-products'><title>Orphaned products</title>
         <blockquote>
             <p>
               [needs improvements?] This is the right place for the
-proposers to publically state their commitment to future development. It
+proposers to publicly state their commitment to future development. It
 takes quite a while to recruit a diverse development community. So Apache
 needs to be confident that those already working on the product are still
 committed.
@@ -342,7 +344,7 @@
                 <p> 
                [needs improvements?] People worry about salaried developers
 who are interested in working on this project only whilst they are employed
-to do so. Apache focusses on people, not corporations. We'd like developers
+to do so. Apache focuses on people, not corporations. We'd like developers
 to continue to be involved with Apache no matter who their current employer
 happens to be.
                 </p>
@@ -354,7 +356,7 @@
                [needs improvements?]
                People are concerned about projects that work just inside
 their own little bubble. Apache encourages projects to open to collaboration
-with other open source projects both within apache and without. This may be
+with other open source projects both within Apache and without. This may be
 existing links but is also a good place to talk about potential future links
 and plans.
                 </p><p>
@@ -412,7 +414,7 @@
         <section id='template-ip'><title>Source and Intellectual Property Submission
Plan</title>
             <blockquote>
 <p>
-More complex proposals (typically involving mutliple code bases) may find it useful
+More complex proposals (typically involving multiple code bases) may find it useful
 to draw up an initial plan for the submission of the code here in a separate
 section. Demonstrates that the proposal is practical.
 </p>
@@ -456,7 +458,7 @@
         <section id='template-mailing-lists'><title>Mailing lists</title>
             <blockquote>
                 <p>
-             Minimum project-private (for pmc) project-dev listing
+             Minimum project-private (for PMC) project-dev listing
                 </p><p>
 If this project is new to open source, it is often best to start with 
 these minimum lists. The initial focus needs to be on recruiting new developers. 
@@ -486,7 +488,7 @@
 The infrastructure documentation should explain the process.
                 </p><p>
         If the proposal requires other special infrastructure, it is best to
-give an explaination. The Apache infrastructure team usually take some
+give an explanation. The Apache infrastructure team usually take some
 convincing before allowing new services on core Apache hardware.
                 </p>
 <pre>
@@ -557,7 +559,7 @@
                 <blockquote>
                     <p>
 [needs improvements?]
-A list of <a href='/incubation/Incubation_Policy.html#Mentor'>eligable</a>  
+A list of <a href='/incubation/Incubation_Policy.html#Mentor'>eligible</a>  
 individuals nominated as <a href='/incubation/Roles_and_Responsibilities.html#Mentor'>mentors</a>

 [<a href='/incubation/Incubation_Policy.html#Mentor'>definition</a>] for the
candidate 
 would are willing to serve.
@@ -569,7 +571,7 @@
                 </p>
                     <p>
 The number of mentors a podling can have is limited only by the
-energy and interest of those eligable to mentor.
+energy and interest of those eligible to mentor.
                 </p>
                     <p>
 It is common for mentors to <a href='partication.html#mentor'>volunteer</a> their
services
@@ -580,7 +582,7 @@
             <section id='template-sponsoring-entity'><title>Sponsoring Entity</title>
                 <blockquote>
                         <p>
-This is the organisational unit within Apache taking resposibility for this
+This is the organisational unit within Apache taking responsibility for this
 proposal.
 The sponsoring entity can be:
 </p>
@@ -590,8 +592,8 @@
         <li>Another Apache project</li>
 </ul>
                 <p>
-Unless there are strong links to an existing pmc, it is recommended that the
-proposal asked that the incubator pmc to act as sponsor.
+Unless there are strong links to an existing PMC, it is recommended that the
+proposal asked that the incubator PMC to act as sponsor.
                 </p>
                 <p>
 Note that the final destination within the Apache organisational structure

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?rev=429393&r1=429392&r2=429393&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Mon Aug  7 10:10:08 2006
@@ -97,7 +97,7 @@
 <p>
 This document is descriptive not normative. It describes ways to go about
 drawing up a proposal for submission. It is not an inflexible standard but
-respresents a consensus condensed from previous discussions on the
+represents a consensus condensed from previous discussions on the
 incubator general list.
           </p>
 </div>
@@ -106,14 +106,15 @@
 </h3>
 <div class="section-content">
 <p>
-Entry to the incubator is a democractic process. The incubator pmc votes on
-whether to accept or not. The proposal is the document upon which the pmc
-votes. So, though it's not necessary or sufficient to have a good proposal,
-a good proposal document will increase the chances of a positive result.
+<a href="entry.html">Entry</a> to the incubator is a democratic 
+<a href="/incubation/Process_Description">process</a>. 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,
+a good proposal document increases the chances of a positive result.
            </p>
 <p>
 The proposal is (in some ways) a manifesto. It should shape the evolution of
-the product at apache. A lot of the information contained should be included
+the product at Apache. A lot of the information it contains should be included
 in the initial project website.
            </p>
 </div>
@@ -136,27 +137,28 @@
 </h3>
 <div class="section-content">
 <p>
-Start by RTFM. The Entry To The incubator is a good place to start this
-process.
+Start with research. The <a href="entry.html">incubator entry guide</a>is a good
place to start this
+process. Also read the <a href="http://www.apache.org">Apache</a> 
+<a href="http://www.apache.org/foundation">documentation</a>.
        </p>
 <p>
-Subscribe to general@incubator.apache.org. Spend some time reviewing the 
-mailing lists archives . The mailing lists are the canonical form of
-communication and decision making at Apache. The documentation represents
+<a href="lists.html">Subscribe</a> to <code>general.AT.incubator.apache.org</code>.

+Spend some time reviewing the 
+<a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">mailing lists
archives</a>. 
+The mailing lists are the canonical form of communication and decision making at Apache.
The documentation is
 an attempt to codify the consensus formed on list.
        </p>
 <p>
-Before drawing up a lengthy proposal, recruit a champion. [links to other
-documentation explaning role of champion] The champion knows how Apache work
-and should be able to help navigate the process.
+Before drawing up a lengthy proposal, recruit a 
+<a href="/incubation/Roles_and_Responsibilities.html#Champion">Champion</a>.
The Champion knows 
+how Apache works and should be able to help to navigate the process.
        </p>
 <p>
-Review recent proposals [links to the wiki] and how they have been received.
+Review <a href="http://wiki.apache.org/incubator/">recent proposals</a> and how
they have been received.
        </p>
 <p>
 The incoming community needs to work together before presenting this
-proposal to
-the incubator. Think about goals and about the reasons for coming to apache.
+proposal to the incubator. Think about goals and about the reasons for coming to Apache.
        </p>
 </div>
 <h3>
@@ -166,13 +168,13 @@
 <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 [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
-about the proposal. Approval is an open and democractic 
+about the proposal. Approval is an open and democratic 
 <a href="entry.html#understanding">process</a>
-so discussion is an important part of opinion forming. Every proposal
+so this discussion is an important part of opinion forming. Every proposal
 will require development if it is to gain the maximum level of support from the
 electorate.
         </p>
@@ -184,7 +186,7 @@
 <p>
 Expect to work on improving the template on list after presenting it. The
 wiki is an excellent way to develop a proposal. Consider creating a wiki
-page containing the same content and supplying a link. Interested parties
+page containing the proposal content and supplying a link. Interested parties
 may wish to add themselves to the watch list for the page so that received
 email notifications when the page is changed.
        </p>
@@ -193,12 +195,12 @@
 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 any change is accepted. Note that the incubator 
-asks all participants to abide by appopriate <a href="participation.html">netiquette</a>.
+asks all participants to abide by appropriate <a href="participation.html">netiquette</a>.
         </p>
 <p>
 Effective management of this development is an exercise in community building. 
-The wiki is not an appropriate forum for debating changing. Discussion should be
-gently moved onto the appropriate mailing list.
+The wiki is not an appropriate forum for debating changes. Discussion should be
+gently moved onto the appropriate mailing list. 
         </p>
 </div>
 <h3>
@@ -210,7 +212,7 @@
 proposal can be put to the vote. If the wiki is used to develop the proposal,
 please ensure that the wiki matches the final proposal then add a notice to 
 the wiki that development of the document is now complete. 
-See <a href="entry.html#">this</a>.
+See <a href="entry.html#vote">this</a>.
         </p>
 </div>
 </div>
@@ -316,7 +318,7 @@
 <div class="section-content">
 <blockquote>
 <p>
-Why does this project need to exist and why should it be adopted by apache?
+Why does this project need to exist and why should it be adopted by Apache?
 <p>
 </p>
 More discursive material is probably better in this section rather than in
@@ -338,7 +340,7 @@
 <p>
 Only include this section if it is not obvious. If the proposal is complex
 (probably involving multiple code bases) then people may worry about it's
-practicallity and whether it may drag in too much Apache energy. 
+practicality and whether it may drag in too much Apache energy. 
 <p>
 </p>
 This is a good place to explain the plan and demonstrate that the proposal
@@ -368,7 +370,7 @@
 <p>
 Questions are often asked about the current status of the constituent codebases
 and current development practices.
-It is sometimes useful to prempt these questions by stating honestly
+It is sometimes useful to preempt these questions by stating honestly
 where how these balance up against principles and ideals. 
 Some proposals describe this section as criteria.
 </p><p>
@@ -419,7 +421,7 @@
 <p>
 An exercise in self-knowledge.
 Risks don't mean that a project is unacceptable.
-It is useful to collect together material prempting questions about possible risks.
+It is useful to collect together material preempting questions about possible risks.
 </p>
         </blockquote>
 <h5> 
@@ -429,7 +431,7 @@
 <blockquote>
             <p>
               [needs improvements?] This is the right place for the
-proposers to publically state their commitment to future development. It
+proposers to publicly state their commitment to future development. It
 takes quite a while to recruit a diverse development community. So Apache
 needs to be confident that those already working on the product are still
 committed.
@@ -475,7 +477,7 @@
                 <p> 
                [needs improvements?] People worry about salaried developers
 who are interested in working on this project only whilst they are employed
-to do so. Apache focusses on people, not corporations. We'd like developers
+to do so. Apache focuses on people, not corporations. We'd like developers
 to continue to be involved with Apache no matter who their current employer
 happens to be.
                 </p>
@@ -490,7 +492,7 @@
                [needs improvements?]
                People are concerned about projects that work just inside
 their own little bubble. Apache encourages projects to open to collaboration
-with other open source projects both within apache and without. This may be
+with other open source projects both within Apache and without. This may be
 existing links but is also a good place to talk about potential future links
 and plans.
                 </p><p>
@@ -560,7 +562,7 @@
 <div class="section-content">
 <blockquote>
 <p>
-More complex proposals (typically involving mutliple code bases) may find it useful
+More complex proposals (typically involving multiple code bases) may find it useful
 to draw up an initial plan for the submission of the code here in a separate
 section. Demonstrates that the proposal is practical.
 </p>
@@ -616,7 +618,7 @@
 <div class="section-content">
 <blockquote>
                 <p>
-             Minimum project-private (for pmc) project-dev listing
+             Minimum project-private (for PMC) project-dev listing
                 </p><p>
 If this project is new to open source, it is often best to start with 
 these minimum lists. The initial focus needs to be on recruiting new developers. 
@@ -655,7 +657,7 @@
 The infrastructure documentation should explain the process.
                 </p><p>
         If the proposal requires other special infrastructure, it is best to
-give an explaination. The Apache infrastructure team usually take some
+give an explanation. The Apache infrastructure team usually take some
 convincing before allowing new services on core Apache hardware.
                 </p>
 <pre>
@@ -741,7 +743,7 @@
 <blockquote>
                     <p>
 [needs improvements?]
-A list of <a href="/incubation/Incubation_Policy.html#Mentor">eligable</a>  
+A list of <a href="/incubation/Incubation_Policy.html#Mentor">eligible</a>  
 individuals nominated as <a href="/incubation/Roles_and_Responsibilities.html#Mentor">mentors</a>

 [<a href="/incubation/Incubation_Policy.html#Mentor">definition</a>] for the
candidate 
 would are willing to serve.
@@ -753,7 +755,7 @@
                 </p>
                     <p>
 The number of mentors a podling can have is limited only by the
-energy and interest of those eligable to mentor.
+energy and interest of those eligible to mentor.
                 </p>
                     <p>
 It is common for mentors to <a href="partication.html#mentor">volunteer</a> their
services
@@ -767,7 +769,7 @@
 <div class="section-content">
 <blockquote>
                         <p>
-This is the organisational unit within Apache taking resposibility for this
+This is the organisational unit within Apache taking responsibility for this
 proposal.
 The sponsoring entity can be:
 </p>
@@ -777,8 +779,8 @@
         <li>Another Apache project</li>
 </ul>
                 <p>
-Unless there are strong links to an existing pmc, it is recommended that the
-proposal asked that the incubator pmc to act as sponsor.
+Unless there are strong links to an existing PMC, it is recommended that the
+proposal asked that the incubator PMC to act as sponsor.
                 </p>
                 <p>
 Note that the final destination within the Apache organisational structure



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


Mime
View raw message