incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r431653 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Tue, 15 Aug 2006 17:42:39 GMT
Author: rdonkin
Date: Tue Aug 15 10:42:39 2006
New Revision: 431653

URL: http://svn.apache.org/viewvc?rev=431653&view=rev
Log:
Added some examples and altered some wordings.

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=431653&r1=431652&r2=431653&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Tue Aug 15 10:42:39 2006
@@ -399,28 +399,29 @@
         <section id='template-orphaned-products'><title>Orphaned products</title>
         <blockquote>
             <p>
-              [needs improvements?] This is the right place for the
-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.
+This is the right place for those donating the code 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.
             </p>
 <pre>
 Example (Yoko):
     The contributors are leading vendors in this space.
-There is no risk of any of the usual warning signs of orphaned 
-or abandoned code.
+    There is no risk of any of the usual warning signs of orphaned 
+    or abandoned code.
 </pre>
         </blockquote>
         </section>
         <section id='template-inexperience-with-open-source'><title>Inexperience
with Open Source</title>
         <blockquote>
         <p>
-One of the reasons why many closed project choose to apply for the incubator 
-is the experience of Apache in the open source space. But this means an invest of energy

-by Apache so many people look for an indications of a willingness to learn 
-and to give back to the community. If the project contains people with a strong
-open source background then this is the place to highlight this.
+One of the reasons why many closed project choose to apply for incubation
+is the experience of Apache in this space. But successfully opening up a closed  
+project means an invest of energy by Apache. So many people look for indications 
+of a willingness to learn and to give back to the community. [this does not flow rationally]
+		</p><p>
+If the project contains people with a strong open source background 
+then this is the place to highlight this.
         </p>
         </blockquote>
         </section>
@@ -445,6 +446,10 @@
 to continue to be involved with Apache no matter who their current employer
 happens to be.
                 </p>
+                <p>
+This is a right place to indicate the balance between salaried developers 
+and volunteers. 
+                </p>
             </blockquote>
         </section>
         <section id='template-other-producrs'><title>Relationships with Other
Apache Products</title>  
@@ -475,10 +480,11 @@
                 <p>
                [needs improvements?] Concerns have been raised in the past
 that some projects are proposed just to generate positive publicity for
-themselves. This is a 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
+themselves. This is 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>
@@ -499,13 +505,27 @@
         <section id='template-initial-source'><title>Initial Source</title>
             <blockquote>
 <p>
-Describes the origin of the proposed code base. If there is no initial source,
-note that here. 
+Describes the origin of the proposed code base. If the initial code arrives
+from more than one source, this is the right place to outline the different
+histories.
+</p><p>
+If there is no initial source, note that here as well. 
 </p>
             </blockquote>
 <pre>
-Examples:
-</pre>
+Example (Heraldry):
+    OpenID has been in development since the summer of 2005. 
+    It currently has an active community (over 15 million enabled
+    accounts) and libraries in a variety of languages. Additionally
+    it is supported by LiveJournal.com and is continuing to gain 
+    traction in the Open Source Community.
+
+    Yadis has been in development since late 2005 and the 
+    specification has not changed since early 2006. Like OpenID, 
+    it has libraries in various languages and there is a large 
+    overlap between the two communities. The specification is
+    ... 
+ </pre>
         </section>
         <section id='template-ip'><title>Source and Intellectual Property Submission
Plan</title>
             <blockquote>
@@ -515,7 +535,19 @@
 section. Demonstrates that the proposal is practical.
 </p>
 <pre>
-Examples:
+Example (Heraldry):
+    * The OpenID specification and content on openid.net from 
+       Brad Fitzpatrick of Six Apart, Ltd. and David Recordon of 
+       VeriSign, Inc.
+    * The domains openid.net and yadis.org from Brad Fitzpatrick 
+       of Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
+    * OpenID libraries in Python, Ruby, Perl, PHP, and C# from 
+       JanRain, Inc.
+    ...
+    * Yadis conformance test suite from NetMesh and VeriSign, Inc.
+   
+   We will also be soliciting contributions of further plugins and 
+   patches to various pieces of Open Source software.
 </pre>
             </blockquote>
         </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=431653&r1=431652&r2=431653&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Tue Aug 15 10:42:39 2006
@@ -526,17 +526,16 @@
 <div class="section-content">
 <blockquote>
             <p>
-              [needs improvements?] This is the right place for the
-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.
+This is the right place for those donating the code 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.
             </p>
 <pre>
 Example (Yoko):
     The contributors are leading vendors in this space.
-There is no risk of any of the usual warning signs of orphaned 
-or abandoned code.
+    There is no risk of any of the usual warning signs of orphaned 
+    or abandoned code.
 </pre>
         </blockquote>
 </div>
@@ -546,11 +545,13 @@
 <div class="section-content">
 <blockquote>
         <p>
-One of the reasons why many closed project choose to apply for the incubator 
-is the experience of Apache in the open source space. But this means an invest of energy

-by Apache so many people look for an indications of a willingness to learn 
-and to give back to the community. If the project contains people with a strong
-open source background then this is the place to highlight this.
+One of the reasons why many closed project choose to apply for incubation
+is the experience of Apache in this space. But successfully opening up a closed  
+project means an invest of energy by Apache. So many people look for indications 
+of a willingness to learn and to give back to the community. [this does not flow rationally]
+		</p><p>
+If the project contains people with a strong open source background 
+then this is the place to highlight this.
         </p>
         </blockquote>
 </div>
@@ -581,6 +582,10 @@
 to continue to be involved with Apache no matter who their current employer
 happens to be.
                 </p>
+                <p>
+This is a right place to indicate the balance between salaried developers 
+and volunteers. 
+                </p>
             </blockquote>
 </div>
 <h5> 
@@ -617,10 +622,11 @@
                 <p>
                [needs improvements?] Concerns have been raised in the past
 that some projects are proposed just to generate positive publicity for
-themselves. This is a 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
+themselves. This is 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>
@@ -647,13 +653,27 @@
 <div class="section-content">
 <blockquote>
 <p>
-Describes the origin of the proposed code base. If there is no initial source,
-note that here. 
+Describes the origin of the proposed code base. If the initial code arrives
+from more than one source, this is the right place to outline the different
+histories.
+</p><p>
+If there is no initial source, note that here as well. 
 </p>
             </blockquote>
 <pre>
-Examples:
-</pre>
+Example (Heraldry):
+    OpenID has been in development since the summer of 2005. 
+    It currently has an active community (over 15 million enabled
+    accounts) and libraries in a variety of languages. Additionally
+    it is supported by LiveJournal.com and is continuing to gain 
+    traction in the Open Source Community.
+
+    Yadis has been in development since late 2005 and the 
+    specification has not changed since early 2006. Like OpenID, 
+    it has libraries in various languages and there is a large 
+    overlap between the two communities. The specification is
+    ... 
+ </pre>
 </div>
 <h4>
    <a name="template-ip">Source and Intellectual Property Submission Plan</a>
@@ -666,7 +686,19 @@
 section. Demonstrates that the proposal is practical.
 </p>
 <pre>
-Examples:
+Example (Heraldry):
+    * The OpenID specification and content on openid.net from 
+       Brad Fitzpatrick of Six Apart, Ltd. and David Recordon of 
+       VeriSign, Inc.
+    * The domains openid.net and yadis.org from Brad Fitzpatrick 
+       of Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
+    * OpenID libraries in Python, Ruby, Perl, PHP, and C# from 
+       JanRain, Inc.
+    ...
+    * Yadis conformance test suite from NetMesh and VeriSign, Inc.
+   
+   We will also be soliciting contributions of further plugins and 
+   patches to various pieces of Open Source software.
 </pre>
             </blockquote>
 </div>



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


Mime
View raw message