incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r434164 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Wed, 23 Aug 2006 20:32:04 GMT
Author: rdonkin
Date: Wed Aug 23 13:32:04 2006
New Revision: 434164

URL: http://svn.apache.org/viewvc?rev=434164&view=rev
Log:
Improved phrasing and added links.

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=434164&r1=434163&r2=434164&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Wed Aug 23 13:32:04 2006
@@ -30,10 +30,10 @@
         <section id="abstract">
           <title>Abstract</title>
           <p>
-This document is descriptive not normative. It describes ways to go about
+This document is descriptive, not normative. It describes approaches to
 drawing up a proposal for submission. It is not an inflexible standard but
-represents a consensus condensed from previous discussions on the
-incubator general list.
+represents a consensus condensed from discussions on the
+<a href='lists.html#general+at+incubator.apache.org'>general mailing list</a>.
           </p>
         </section>
         <section id="background">
@@ -48,14 +48,16 @@
            </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 it contains should be included
-in the initial project website.
+the project. Much of the information contained should be reused 
+in the <a href='website.html'>podling website</a>. So, a good proposal
+should prove useful in the future as well as in the present.
            </p>
         </section>
         <section id='note-on-improvements'><title>Continuous Improvement</title>
         	<p>
 The process at the incubator is continuously evolving. Hopefully this will help newer
-projects to be even stronger and more successful then existing ones. 
+projects to be even stronger and more successful then existing ones. A consequence 
+of this approach is that president is not always a reliable guide.
         	</p>
         </section>
         <section id="help-wanted">
@@ -69,19 +71,22 @@
     <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
+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>
-<a href='lists.html'>Subscribe</a> to <code>general.AT.incubator.apache.org</code>.

+<a href='lists.html'>Subscribe</a> to the 
+<a href='lists.html#general+at+incubator.apache.org'>general mailing list</a>.

 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.
+The mailing lists are the canonical form of 
+<a href='http://www.apache.org/foundation/how-it-works.html#communication'>communication</a>

+and <a href='http://www.apache.org/foundation/how-it-works.html#decision-making'>decision
making</a> 
+at Apache. The documentation is an attempt to codify the consensus formed and record the
decisions taken on list.
        </p>
        <p>
-Before drawing up a lengthy proposal, recruit a 
+Before starting on the formal 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>
@@ -111,31 +116,32 @@
         <section id='developing'><title>Developing The Proposal</title>
             <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 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.
+<a href='http://wiki.apache.org/incubator/'>wiki</a> is an good way to 
+develop a proposal. Consider creating a wiki page containing the proposal 
+content and supplying a link. Those who are interested should add themselves 
+to the watch list for the page.
        </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 any change is accepted. Note that the incubator 
+and there is no requirement that every change is accepted. Note that the incubator 
 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 changes. Discussion should be
-gently moved onto the appropriate mailing list. 
+gently moved onto the appropriate 
+<a href='lists.html#general+at+incubator.apache.org'>mailing list</a>. 
         </p>
     </section>
         <section id='vote'><title>The Vote</title>
             <p>
 When the proposal seems finished and some sort of consensus has emerged, the
-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#vote'>this</a>.
+proposal should be put to the <a href='entry.html#vote'>vote</a>. 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.
         </p>
     </section>
 </section>

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?rev=434164&r1=434163&r2=434164&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Wed Aug 23 13:32:04 2006
@@ -95,10 +95,10 @@
 </h3>
 <div class="section-content">
 <p>
-This document is descriptive not normative. It describes ways to go about
+This document is descriptive, not normative. It describes approaches to
 drawing up a proposal for submission. It is not an inflexible standard but
-represents a consensus condensed from previous discussions on the
-incubator general list.
+represents a consensus condensed from discussions on the
+<a href="lists.html#general+at+incubator.apache.org">general mailing list</a>.
           </p>
 </div>
 <h3>
@@ -115,8 +115,9 @@
            </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 it contains should be included
-in the initial project website.
+the project. Much of the information contained should be reused 
+in the <a href="website.html">podling website</a>. So, a good proposal
+should prove useful in the future as well as in the present.
            </p>
 </div>
 <h3>
@@ -125,7 +126,8 @@
 <div class="section-content">
 <p>
 The process at the incubator is continuously evolving. Hopefully this will help newer
-projects to be even stronger and more successful then existing ones. 
+projects to be even stronger and more successful then existing ones. A consequence 
+of this approach is that president is not always a reliable guide.
         	</p>
 </div>
 <h3>
@@ -147,19 +149,22 @@
 </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
+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>
-<a href="lists.html">Subscribe</a> to <code>general.AT.incubator.apache.org</code>.

+<a href="lists.html">Subscribe</a> to the 
+<a href="lists.html#general+at+incubator.apache.org">general mailing list</a>.

 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.
+The mailing lists are the canonical form of 
+<a href="http://www.apache.org/foundation/how-it-works.html#communication">communication</a>

+and <a href="http://www.apache.org/foundation/how-it-works.html#decision-making">decision
making</a> 
+at Apache. The documentation is an attempt to codify the consensus formed and record the
decisions taken on list.
        </p>
 <p>
-Before drawing up a lengthy proposal, recruit a 
+Before starting on the formal 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>
@@ -195,22 +200,23 @@
 <div class="section-content">
 <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 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.
+<a href="http://wiki.apache.org/incubator/">wiki</a> is an good way to 
+develop a proposal. Consider creating a wiki page containing the proposal 
+content and supplying a link. Those who are interested should add themselves 
+to the watch list for the page.
        </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 any change is accepted. Note that the incubator 
+and there is no requirement that every change is accepted. Note that the incubator 
 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 changes. Discussion should be
-gently moved onto the appropriate mailing list. 
+gently moved onto the appropriate 
+<a href="lists.html#general+at+incubator.apache.org">mailing list</a>. 
         </p>
 </div>
 <h3>
@@ -219,10 +225,10 @@
 <div class="section-content">
 <p>
 When the proposal seems finished and some sort of consensus has emerged, the
-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#vote">this</a>.
+proposal should be put to the <a href="entry.html#vote">vote</a>. 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.
         </p>
 </div>
 </div>



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


Mime
View raw message