incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r558790 - in /incubator/public/trunk: site-author/guides/proposal.xml site-publish/guides/proposal.html
Date Mon, 23 Jul 2007 16:26:13 GMT
Author: rdonkin
Date: Mon Jul 23 09:26:08 2007
New Revision: 558790

URL: http://svn.apache.org/viewvc?view=rev&rev=558790
Log:
Added more examples to known risks.

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?view=diff&rev=558790&r1=558789&r2=558790
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Mon Jul 23 09:26:08 2007
@@ -449,6 +449,29 @@
   The contributors are leading vendors in this space. There is no risk
   of any of the usual warning signs of orphaned or abandoned code.
 </source>
+<br/>
+<source>
+Example (Ivy):
+Due to its small number of committers, there is a risk of being orphaned.
+The main knowledge of the codebase is still mainly owned by Xavier Hanin.
+Even if Xavier has no plan to leave Ivy development, this is a problem we
+are aware of and know that need to be worked on so that the project become
+less dependent on an individual.
+</source>
+<br/>
+<source>
+Example (Tika):
+There are a number of projects at various stages of maturity that implement 
+a subset of the proposed features in Tika. For many potential users the 
+existing tools are already enough, which reduces the demand for a more 
+generic toolkit. This can also be seen in the slow progress of this proposal 
+over the past year.
+
+However, once the project gets started we can quickly reach the feature level 
+of existing tools based on seed code from sources mentioned below. After that 
+we believe to be able to quickly grow the developer and user communities based 
+on the benefits of a generic toolkit over custom alternatives.
+</source>
         </section>
         <section id='template-inexperience-with-open-source'><title>Inexperience
with Open Source</title>
         <note>
@@ -473,12 +496,35 @@
 Example (Cayenne):
   Cayenne was started as an open source project in 2001 and has 
   remained so for 5 years.
-	 
+ </source>
+ <br/>
+ <source>	 
 Example (Beehive):
   Many of the committers have experience working on open source 
   projects. Five of them have experience as committers on other
   Apache projects.
  </source>
+ <br/>
+ <source>
+Example (Ivy):
+  While distributed under an open source license, access to Ivy was initially
+  limited with no public access to the issue tracking system or svn
+  repository. While things have changed since then - the svn repository is
+  publicly accessible, a JIRA instance has been setup since june 2005, many
+  new features are first discussed on the forum or JIRA - experience with a
+  true open source development model is currently limited.
+  However, Maarten has already a good experience with true open development
+  process, and bring his experience to the project.
+ </source>
+ <br/>
+ <source>
+Example (River):
+  The initial committers have varying degrees of experience with open source
+  projects. All have been involved with source code that has been released under
+  an open source license, but there is limited experience developing code with an
+  open source development process. We do not, however, expect any difficulty in
+  executing under normal meritocracy rules.
+</source>
         </section>
         <section id='template-homogenuous-developers'><title>Homogenous Developers</title>
             <note>
@@ -500,6 +546,28 @@
   are geographically distributed across the U.S., Europe, and Asia. 
   They are experienced with working in a distributed environment.
 </source>
+<br/>
+<source>
+Example (River)
+  Since the Jini Technology Starter Kit has been mainly developed to date by Sun
+  Microsystems, the vast majority of initial committers to the project are from
+  Sun. Over the years, Sun has received bug fixes and enhancements from other
+  developers which have been incorporated into the code. Our plan is to work with
+  these other developers and add them as committers as we progress. There are
+  three other initial committers (non Sun): Bill Venners, Dan Creswell, and Mark
+  Brouwer. Bill is the lead of the Service UI API work, Dan has been involved with
+  much Jini-based development, including an implementation of the JavaSpaces
+  service called Blitz &lt;http://www.dancres.org/blitz/&gt;, and Mark is veteran
of
+  much Jini-based development, including commercial work at Virgil
+  &lt;http://www.virgil.nl&gt; as well as leading the open source Cheiron
+  &lt;http://www.cheiron.org&gt; project.
+</source>
+<br/>
+<source>
+Example (Ivy):
+  With only two core developers, at least they are not homogenous! Xavier and
+  Maarten knew each other only due to their common interest in Ivy.
+</source>
         </section>
         <section id='template-reliance-on-salaried-developers'><title>Reliance
on Salaried Developers</title>            
             <note>
@@ -524,6 +592,26 @@
   the code, the project would continue without issue if no salaried 
   developers contributed to the project.
 </source>
+<br/>
+<source>
+Example (River):
+  It is expected that Jini development will occur on both salaried time and on
+  volunteer time, after hours. While there is reliance on salaried developers
+  (currently from Sun, but it's expected that other company's salaried developers
+  will also be involved), the Jini Community is very active and things should
+  balance out fairly quickly. In the meantime, Sun will support the project in the
+  future by dedicating 'work time' to Jini, so that there is a smooth transition.
+</source>
+<br/>
+<source>
+Example (Wicket):
+  None of the developers rely on Wicket for consulting work, though two -
+  Martijn and Eelco -  are writing Wicket In Action (publisher Manning) in
+  their spare time. Most of the developers use Wicket for their day jobs,
+  some for multiple projects, and will do so for a considerable while as
+  their companies (specifically Topicus, Cemron and Teachscape) choose
+  Wicket as their development framework of choice.
+</source>
         </section>
         <section id='template-other-producrs'><title>Relationships with Other
Apache Products</title>  
             <note>
@@ -550,6 +638,13 @@
   products (regexp, commons collections, commons lang, commons pool), 
   and supports Apache commons logging.
 </source>
+<br/>
+<source>
+Example (River)
+  Currently the only tie to Apache projects is the starter kit's use 
+  of the Ant build tool. There are potential future ties (http server, 
+  database backend, etc)that will be explored.
+</source>
         </section>
         <section id='template-brand-fascination'><title>A Excessive Fascination
with the Apache Brand</title>  
             <note>
@@ -571,7 +666,9 @@
   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.
-  
+</source>
+<br/>
+<source>
 Example (Wicket):
   The ASF has a strong brand, and that brand is in itself attractive.
   However, the developers of Wicket have been quite successful on 
@@ -581,6 +678,14 @@
   have been enthusiastic users of Apache from the earliest hour 
   (remember JServ anyone?), and feel honored at getting the 
   opportunity to join the club.
+</source>
+<br/>
+<source>
+Example (OpenJPA):
+  We think that Open JPA is something that will benefit from wide
+  collaboration, being able to build a community of developers and
+  committers that outlive the founders, and that will be embraced 
+  by other Apache efforts, such as the Geronimo project.
 </source>
         </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?view=diff&rev=558790&r1=558789&r2=558790
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Mon Jul 23 09:26:08 2007
@@ -836,6 +836,31 @@
   of any of the usual warning signs of orphaned or abandoned code.
 </code>
 </div>
+<br />
+<div class="source"><code>
+Example (Ivy):
+Due to its small number of committers, there is a risk of being orphaned.
+The main knowledge of the codebase is still mainly owned by Xavier Hanin.
+Even if Xavier has no plan to leave Ivy development, this is a problem we
+are aware of and know that need to be worked on so that the project become
+less dependent on an individual.
+</code>
+</div>
+<br />
+<div class="source"><code>
+Example (Tika):
+There are a number of projects at various stages of maturity that implement 
+a subset of the proposed features in Tika. For many potential users the 
+existing tools are already enough, which reduces the demand for a more 
+generic toolkit. This can also be seen in the slow progress of this proposal 
+over the past year.
+
+However, once the project gets started we can quickly reach the feature level 
+of existing tools based on seed code from sources mentioned below. After that 
+we believe to be able to quickly grow the developer and user communities based 
+on the benefits of a generic toolkit over custom alternatives.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-inexperience-with-open-source">Inexperience with Open Source</a>
@@ -865,13 +890,39 @@
 Example (Cayenne):
   Cayenne was started as an open source project in 2001 and has 
   remained so for 5 years.
-	 
+ </code>
+</div>
+<br />
+<div class="source"><code>	 
 Example (Beehive):
   Many of the committers have experience working on open source 
   projects. Five of them have experience as committers on other
   Apache projects.
  </code>
 </div>
+<br />
+<div class="source"><code>
+Example (Ivy):
+  While distributed under an open source license, access to Ivy was initially
+  limited with no public access to the issue tracking system or svn
+  repository. While things have changed since then - the svn repository is
+  publicly accessible, a JIRA instance has been setup since june 2005, many
+  new features are first discussed on the forum or JIRA - experience with a
+  true open source development model is currently limited.
+  However, Maarten has already a good experience with true open development
+  process, and bring his experience to the project.
+ </code>
+</div>
+<br />
+<div class="source"><code>
+Example (River):
+  The initial committers have varying degrees of experience with open source
+  projects. All have been involved with source code that has been released under
+  an open source license, but there is limited experience developing code with an
+  open source development process. We do not, however, expect any difficulty in
+  executing under normal meritocracy rules.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-homogenuous-developers">Homogenous Developers</a>
@@ -899,6 +950,30 @@
   They are experienced with working in a distributed environment.
 </code>
 </div>
+<br />
+<div class="source"><code>
+Example (River)
+  Since the Jini Technology Starter Kit has been mainly developed to date by Sun
+  Microsystems, the vast majority of initial committers to the project are from
+  Sun. Over the years, Sun has received bug fixes and enhancements from other
+  developers which have been incorporated into the code. Our plan is to work with
+  these other developers and add them as committers as we progress. There are
+  three other initial committers (non Sun): Bill Venners, Dan Creswell, and Mark
+  Brouwer. Bill is the lead of the Service UI API work, Dan has been involved with
+  much Jini-based development, including an implementation of the JavaSpaces
+  service called Blitz &lt;http://www.dancres.org/blitz/&gt;, and Mark is veteran
of
+  much Jini-based development, including commercial work at Virgil
+  &lt;http://www.virgil.nl&gt; as well as leading the open source Cheiron
+  &lt;http://www.cheiron.org&gt; project.
+</code>
+</div>
+<br />
+<div class="source"><code>
+Example (Ivy):
+  With only two core developers, at least they are not homogenous! Xavier and
+  Maarten knew each other only due to their common interest in Ivy.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-reliance-on-salaried-developers">Reliance on Salaried Developers</a>
@@ -929,6 +1004,28 @@
   developers contributed to the project.
 </code>
 </div>
+<br />
+<div class="source"><code>
+Example (River):
+  It is expected that Jini development will occur on both salaried time and on
+  volunteer time, after hours. While there is reliance on salaried developers
+  (currently from Sun, but it's expected that other company's salaried developers
+  will also be involved), the Jini Community is very active and things should
+  balance out fairly quickly. In the meantime, Sun will support the project in the
+  future by dedicating 'work time' to Jini, so that there is a smooth transition.
+</code>
+</div>
+<br />
+<div class="source"><code>
+Example (Wicket):
+  None of the developers rely on Wicket for consulting work, though two -
+  Martijn and Eelco -  are writing Wicket In Action (publisher Manning) in
+  their spare time. Most of the developers use Wicket for their day jobs,
+  some for multiple projects, and will do so for a considerable while as
+  their companies (specifically Topicus, Cemron and Teachscape) choose
+  Wicket as their development framework of choice.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-other-producrs">Relationships with Other Apache Products</a>
@@ -961,6 +1058,14 @@
   and supports Apache commons logging.
 </code>
 </div>
+<br />
+<div class="source"><code>
+Example (River)
+  Currently the only tie to Apache projects is the starter kit's use 
+  of the Ant build tool. There are potential future ties (http server, 
+  database backend, etc)that will be explored.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-brand-fascination">A Excessive Fascination with the Apache Brand</a>
@@ -987,7 +1092,10 @@
   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.
-  
+</code>
+</div>
+<br />
+<div class="source"><code>
 Example (Wicket):
   The ASF has a strong brand, and that brand is in itself attractive.
   However, the developers of Wicket have been quite successful on 
@@ -997,6 +1105,15 @@
   have been enthusiastic users of Apache from the earliest hour 
   (remember JServ anyone?), and feel honored at getting the 
   opportunity to join the club.
+</code>
+</div>
+<br />
+<div class="source"><code>
+Example (OpenJPA):
+  We think that Open JPA is something that will benefit from wide
+  collaboration, being able to build a community of developers and
+  committers that outlive the founders, and that will be embraced 
+  by other Apache efforts, such as the Geronimo project.
 </code>
 </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