incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r432660 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Fri, 18 Aug 2006 17:41:05 GMT
Author: rdonkin
Date: Fri Aug 18 10:41:04 2006
New Revision: 432660

URL: http://svn.apache.org/viewvc?rev=432660&view=rev
Log:
Phrasing improvements and some more examples.

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=432660&r1=432659&r2=432660&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Fri Aug 18 10:41:04 2006
@@ -199,7 +199,7 @@
 More discursive material can be included in later sections.
 </p>
 <pre>
-Example:
+Example (XAP):
         XAP is to provide an XML-based declarative framework 
         for building, deploying and maintaining rich, interactive, 
         Ajax-powered web applications. A basic principal of XAP 
@@ -226,7 +226,7 @@
 This material should probably find an eventual home on the project website.
 </p>
 <pre>
-Example:
+Example (Heraldry):
    To provide some background, the Higgins Project is being actively
    developed within Eclipse and is a framework that will enable users
    and enterprises to integrate identity, profile, and relationship 
@@ -272,18 +272,16 @@
 is feasible and has been thought through.
 </p>
 <pre>
-Example:
-    Initial Goals
-    -------------
-      * Expansion of Yadis and OpenID libraries into additional
-        languages beyond the existing Python, Ruby, Perl, and 
-        PHP libraries
-      * OpenID authentication specification revision to fix known
-        security considerations, investigate compatibility with 
-        the DIX IETF proposal, describe Yadis integration, and 
-        allow either an URL or XRI be used as the End User's 
-        Identifier
-      ...
+Example (Heraldry):
+    * Expansion of Yadis and OpenID libraries into additional
+       languages beyond the existing Python, Ruby, Perl, and 
+       PHP libraries
+    * OpenID authentication specification revision to fix known
+       security considerations, investigate compatibility with 
+       the DIX IETF proposal, describe Yadis integration, and 
+       allow either an URL or XRI be used as the End User's 
+       Identifier
+     ...
 </pre>
         </blockquote>
         </section>
@@ -488,30 +486,43 @@
         <section id='template-reliance-on-salaried-developers'><title>Reliance
on Salaried Developers</title>            
             <blockquote>
                 <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 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.
+Some worry about the long term health of projects dominated by salaried developers
+who are interested in working on the code only whilst they are employed
+to do so. Apache is 
+<a href='http://www.apache.org/foundation/how-it-works.html#hats'>about</a> people,
not corporations. 
+We hope that developers continue to be involved with Apache no matter who their current employer
+happens to be. A healthy Apache project should be able to continue in the case of salaried

+developers being withdrawn.
                 </p>
                 <p>
 This is a right place to indicate the balance between salaried developers 
-and volunteers. 
+and volunteers. It's also good to talk about the level of commitment of the developers.
                 </p>
+<pre>
+Example (OpenJPA):
+
+  Most of the developers are paid by their employer to contribute 
+  to this project, but given the anticipation from the Java community 
+  for the a JPA implementation and the committers' sense of ownership 
+  for the code, the project would continue without issue if no salaried 
+  developers contributed to the project.
+</pre>
             </blockquote>
         </section>
         <section id='template-other-producrs'><title>Relationships with Other
Apache Products</title>  
             <blockquote>
                 <p>
-There are concerns about projects that work just inside
+There are concerns about that a candidate may work just inside
 their own little bubble. Apache encourages projects to be open to collaboration
-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.
+with other open source projects both within Apache and without. 
+				</p><p>
+This is a an opertunity 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.
+coorporation whenever this makes sense. Competition between code
+but cordial coorporation between communities.
                 </p><p>
 It is not always obvious to all
 whether the proposers see themselves as direct competitors with an existing
@@ -521,26 +532,41 @@
 In the case of indirect competition, it may be important that the abstract 
 describe accurately the niche.
                 </p>
+<pre>
+Example (OpenJPA):
+
+  Open JPA will likely be used by Geronimo, requires some Apache 
+  products (regexp, commons collections, commons lang, commons pool), 
+  and supports Apache commons logging.
+</pre>
             </blockquote>
         </section>
         <section id='template-brand-fascination'><title>A Fascination with the
Apache Brand</title>  
             <blockquote>
                 <p>
-               [needs improvements?] Concerns have been raised in the past
-that some projects are proposed just to generate positive publicity for
-themselves. 
+Concerns have been raised in the past that some projects appear to have been proposed 
+just to generate positive publicity for the proposers. A candidate with a closed
+source background should definitely say given some sort of public statement in 
+proposal to convince any possible doubters that this is not the case.
 				</p><p>
-This is the right place to chance to build bridges with the 
+This is also the right place to chance to build bridges with the 
 community after past misdemeanors (for example, if any of those associated 
 with the proposal have - in the past - sort to associate themselves with the Apache brand
in
 factually incorrect ways) and promise good conduct for the future.
 [is this right? why do we have this section?]
                 </p>
-            </blockquote>
-        </section>
 <pre>
-Examples:
+Example (CeltiXfire):
+
+  While we expect the Apache brand may help attract more 
+  contributors, our interests in starting this project is based 
+  on the factors mentioned in the Rationale section. However, 
+  we will be sensitive to inadvertent abuse of the Apache brand 
+  and will work with the Incubator PMC and the PRC to ensure 
+  the brand policies are respected.
 </pre>
+            </blockquote>
+        </section>
         </section>
         <section id='template-documentation'><title>Documentation</title>
             <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=432660&r1=432659&r2=432660&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Fri Aug 18 10:41:04 2006
@@ -296,7 +296,7 @@
 More discursive material can be included in later sections.
 </p>
 <pre>
-Example:
+Example (XAP):
         XAP is to provide an XML-based declarative framework 
         for building, deploying and maintaining rich, interactive, 
         Ajax-powered web applications. A basic principal of XAP 
@@ -326,7 +326,7 @@
 This material should probably find an eventual home on the project website.
 </p>
 <pre>
-Example:
+Example (Heraldry):
    To provide some background, the Higgins Project is being actively
    developed within Eclipse and is a framework that will enable users
    and enterprises to integrate identity, profile, and relationship 
@@ -378,18 +378,16 @@
 is feasible and has been thought through.
 </p>
 <pre>
-Example:
-    Initial Goals
-    -------------
-      * Expansion of Yadis and OpenID libraries into additional
-        languages beyond the existing Python, Ruby, Perl, and 
-        PHP libraries
-      * OpenID authentication specification revision to fix known
-        security considerations, investigate compatibility with 
-        the DIX IETF proposal, describe Yadis integration, and 
-        allow either an URL or XRI be used as the End User's 
-        Identifier
-      ...
+Example (Heraldry):
+    * Expansion of Yadis and OpenID libraries into additional
+       languages beyond the existing Python, Ruby, Perl, and 
+       PHP libraries
+    * OpenID authentication specification revision to fix known
+       security considerations, investigate compatibility with 
+       the DIX IETF proposal, describe Yadis integration, and 
+       allow either an URL or XRI be used as the End User's 
+       Identifier
+     ...
 </pre>
         </blockquote>
 </div>
@@ -623,16 +621,27 @@
 <div class="section-content">
 <blockquote>
                 <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 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.
+Some worry about the long term health of projects dominated by salaried developers
+who are interested in working on the code only whilst they are employed
+to do so. Apache is 
+<a href="http://www.apache.org/foundation/how-it-works.html#hats">about</a> people,
not corporations. 
+We hope that developers continue to be involved with Apache no matter who their current employer
+happens to be. A healthy Apache project should be able to continue in the case of salaried

+developers being withdrawn.
                 </p>
                 <p>
 This is a right place to indicate the balance between salaried developers 
-and volunteers. 
+and volunteers. It's also good to talk about the level of commitment of the developers.
                 </p>
+<pre>
+Example (OpenJPA):
+
+  Most of the developers are paid by their employer to contribute 
+  to this project, but given the anticipation from the Java community 
+  for the a JPA implementation and the committers' sense of ownership 
+  for the code, the project would continue without issue if no salaried 
+  developers contributed to the project.
+</pre>
             </blockquote>
 </div>
 <h5> 
@@ -641,15 +650,17 @@
 <div class="section-content">
 <blockquote>
                 <p>
-There are concerns about projects that work just inside
+There are concerns about that a candidate may work just inside
 their own little bubble. Apache encourages projects to be open to collaboration
-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.
+with other open source projects both within Apache and without. 
+				</p><p>
+This is a an opertunity 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.
+coorporation whenever this makes sense. Competition between code
+but cordial coorporation between communities.
                 </p><p>
 It is not always obvious to all
 whether the proposers see themselves as direct competitors with an existing
@@ -659,6 +670,13 @@
 In the case of indirect competition, it may be important that the abstract 
 describe accurately the niche.
                 </p>
+<pre>
+Example (OpenJPA):
+
+  Open JPA will likely be used by Geronimo, requires some Apache 
+  products (regexp, commons collections, commons lang, commons pool), 
+  and supports Apache commons logging.
+</pre>
             </blockquote>
 </div>
 <h5> 
@@ -667,21 +685,29 @@
 <div class="section-content">
 <blockquote>
                 <p>
-               [needs improvements?] Concerns have been raised in the past
-that some projects are proposed just to generate positive publicity for
-themselves. 
+Concerns have been raised in the past that some projects appear to have been proposed 
+just to generate positive publicity for the proposers. A candidate with a closed
+source background should definitely say given some sort of public statement in 
+proposal to convince any possible doubters that this is not the case.
 				</p><p>
-This is the right place to chance to build bridges with the 
+This is also the right place to chance to build bridges with the 
 community after past misdemeanors (for example, if any of those associated 
 with the proposal have - in the past - sort to associate themselves with the Apache brand
in
 factually incorrect ways) and promise good conduct for the future.
 [is this right? why do we have this section?]
                 </p>
-            </blockquote>
-</div>
 <pre>
-Examples:
+Example (CeltiXfire):
+
+  While we expect the Apache brand may help attract more 
+  contributors, our interests in starting this project is based 
+  on the factors mentioned in the Rationale section. However, 
+  we will be sensitive to inadvertent abuse of the Apache brand 
+  and will work with the Incubator PMC and the PRC to ensure 
+  the brand policies are respected.
 </pre>
+            </blockquote>
+</div>
 </div>
 <h4>
    <a name="template-documentation">Documentation</a>



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


Mime
View raw message