incubator-cvs mailing list archives

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

URL: http://svn.apache.org/viewvc?rev=432023&view=rev
Log:
More examples plus a little content

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=432023&r1=432022&r2=432023&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Wed Aug 16 13:32:25 2006
@@ -249,7 +249,14 @@
 This content should be ignorable for those for whom the need is obvious.
 </p>
 <pre>
-Examples:
+Example (Beehive):
+
+  There is a strong need for a cohesive, easy-to-use programming model 
+  for building J2EE applications. Developers new to Java are forced to 
+  learn a myriad of APIs just to build simple applications; advanced J2EE
+  developers are forced to write tedious plumbing code; and tools authors
+  are limited in what they can do to simplify the experience due to the 
+  underlying complexity.
 </pre>
         </blockquote>
         </section>
@@ -381,13 +388,26 @@
         </section>
         <section id='template-alignment'><title>Alignment</title>
         <p>
-[need more content describing these attributes]
+An opertunity to highlight links either with Apache 
+<a href='http://projects.apache.org'>projects</a>
+or <a href='http://www.apache.org/foundation/how-it-works.html'>philosophy</a>.
+Or otherwise talk about why Apache is a good match for the proposal.
         </p>
-        </section>
 <pre>
-Examples:
+Example (Beehive):
+
+  The initial code base is targeted to run within Tomcat, 
+  but the goal is to allow the framework to run on any 
+  compliant Servlet or J2EE container. The Web services 
+  component, based on JSR-181, will leverage Axis. 
+  The NetUI component builds on top of Struts. The 
+  underlying Controls component framework uses Velocity. 
+  There are other projects that we will need to work with, 
+  such as the Portals and Maven projects.
 </pre>
         </section>
+
+        </section>
         <section id='template-known-risks'><title>Known Risks</title>
         <blockquote>
 <p>
@@ -499,7 +519,20 @@
                 </p>
             </blockquote>
 <pre>
-Examples:
+Examples (Heraldry):
+
+  [1] Information on Yadis can be found at:
+    http://yadis.org 
+    http://www.openidenabled.com
+
+  [2] Information on OpenID can be found at:
+    http://www.openid.net 
+    http://www.openidenabled.com
+
+  The mailing list for both OpenID and Yadis is located at:
+    http://lists.danga.com/mailman/listinfo/yadis
+  ...
+
 </pre>
         </section>
         <section id='template-initial-source'><title>Initial Source</title>
@@ -554,13 +587,17 @@
         <section id='template-external-dependencies'><title>External Dependencies</title>
             <blockquote>
 <p>
-External dependencies for the initial source is important. Apache has policy
+External dependencies for the initial source is important. Apache has 
+<a href='http://www.apache.org/legal/3party.html'>policy</a>
 about dependencies allowed for projects. These are (to some extent) relaxed
 for projects under incubation. Listing dependencies and licenses allows any
 possible problems to be highlighted and the appropriate actions planned.
 </p>
 <pre>
-Examples:
+Example (CeltiXfire):
+
+  The dependencies all have Apache compatible licenses. These include BSD, 
+  CDDL, CPL, MPL and MIT licensed dependencies.
 </pre>
             </blockquote>
         </section>
@@ -568,7 +605,8 @@
             <blockquote>
 <p>
 If the proposal involves cryptographic code either directly or indirectly,
-Apache needs to know so that the relevant paperwork can be obtained.
+Apache needs to know so that the 
+<a href='http://www.apache.org/dev/crypto.html'>relevant paperwork</a> can be
obtained.
 </p>
             </blockquote>
         </section>
@@ -582,7 +620,9 @@
         <section id='template-mailing-lists'><title>Mailing lists</title>
             <blockquote>
                 <p>
-             Minimum project-private (for PMC) project-dev listing
+The minimum required lists are <em>project</em>-private 
+(for confidential <a href='ppmc.html'>PPMC</a> discussions) 
+and  <em>project</em>-dev lists. 
                 </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. 
@@ -591,17 +631,51 @@
 and user lists in the usual way.
                 </p><p>
 Existing open source projects moving to Apache will probably want to adopt the
-same mailing list set up here as they have already. 
-                </p>
+same mailing list set up here as they have already. However, the transition for users may
+prove more smooth if only the development lists are bootstrapped initially. The user
+lists can then be migrated by a simple podling vote once the Apache infrastructure 
+is ready and fully prepared.
+                </p>
+                <p>
+It is conventional to use an all lower case, dash-separated (<code>-</code>)
 prefix
+based on the project name. 
+                </p>
+<pre>
+  Example:
+  
+    * beehive-ppmc (with moderated subscriptions)
+    * beehive-dev
+    * beehive-commits
+    * beehive-user
+</pre>
             </blockquote>
         </section>
         <section id='template-subversion-directory'><title>Subversion Directory</title>
+        <blockquote>
+        	<p>
+It is conventional to use all lower case, dash-separated (<code>-</code>) directory
names.
+The directory should be within the incubatory directory space 
+(<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
+        	</p>
+<pre>
+Example:
+
+   https://svn.apache.org/repos/asf/incubator/openjpa
+</pre>
+			</blockquote>
         </section>
         <section id='template-issue-tracking'><title>Issue Tracking</title>
             <blockquote>
                 <p>
-Apache runs JIRA and Bugzilla.
+Apache runs <a href='https://issues.apache.org/jira/secure/Dashboard.jspa'>JIRA</a>
+and <a href='http://issues.apache.org/bugzilla/'>Bugzilla</a>. Choose one. Include
the
+name by which project will be known in the issue tracking system.
                 </p>
+<pre>
+Example:
+    
+    JIRA Open-JPA (OPEN-JPA)
+</pre>
             </blockquote>
         </section>
         <section id='template-other-resources'><title>Other Resources</title>
@@ -615,9 +689,6 @@
 give an explanation. The Apache infrastructure team usually take some
 convincing before allowing new services on core Apache hardware.
                 </p>
-<pre>
-Examples:
-</pre>
                 </blockquote>
             </section>
         </section>
@@ -680,8 +751,21 @@
             <section id='template-champion'><title>Champion</title>
                 <blockquote>
                 <p>
-[needs improvements?] A champion should be found before the proposal is
-submitted.
+The <a href='/incubation/Roles_and_Responsibilities.html#Champion'>Champion</a>
is
+a person already associated with Apache who leads the proposal process. It is common 
+- but not necessary - for the Champion to also be proposed as a 
+<a href='#template-mentors'>Mentor</a>. Note that since Mentors are appointed
+by the 
+<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>
+Incubator PMC</a> 
+as part of the acceptance process, they can 
+have no formal role before the proposal is submitted hence the need for a Champion.
+				</p>
+				<p>
+A Champion should be found before the proposal is formally submitted. 
+                </p>
+                <p>
+                [move this section into enter the incubator?]
                 </p>
                 </blockquote>
             </section>
@@ -712,8 +796,8 @@
             <section id='template-sponsoring-entity'><title>Sponsoring Entity</title>
                 <blockquote>
                         <p>
-This is the organisational unit within Apache taking responsibility for this
-proposal.
+The <a href='/incubation/Roles_and_Responsibility.html#Sponsor'>Sponsor</a> 
+is the organisational unit within Apache taking responsibility for this proposal.
 The sponsoring entity can be:
 </p>
 <ul>

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?rev=432023&r1=432022&r2=432023&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Wed Aug 16 13:32:25 2006
@@ -352,7 +352,14 @@
 This content should be ignorable for those for whom the need is obvious.
 </p>
 <pre>
-Examples:
+Example (Beehive):
+
+  There is a strong need for a cohesive, easy-to-use programming model 
+  for building J2EE applications. Developers new to Java are forced to 
+  learn a myriad of APIs just to build simple applications; advanced J2EE
+  developers are forced to write tedious plumbing code; and tools authors
+  are limited in what they can do to simplify the experience due to the 
+  underlying complexity.
 </pre>
         </blockquote>
 </div>
@@ -502,13 +509,25 @@
 </h5> 
 <div class="section-content">
 <p>
-[need more content describing these attributes]
+An opertunity to highlight links either with Apache 
+<a href="http://projects.apache.org">projects</a>
+or <a href="http://www.apache.org/foundation/how-it-works.html">philosophy</a>.
+Or otherwise talk about why Apache is a good match for the proposal.
         </p>
-</div>
 <pre>
-Examples:
+Example (Beehive):
+
+  The initial code base is targeted to run within Tomcat, 
+  but the goal is to allow the framework to run on any 
+  compliant Servlet or J2EE container. The Web services 
+  component, based on JSR-181, will leverage Axis. 
+  The NetUI component builds on top of Struts. The 
+  underlying Controls component framework uses Velocity. 
+  There are other projects that we will need to work with, 
+  such as the Portals and Maven projects.
 </pre>
 </div>
+</div>
 <h4>
    <a name="template-known-risks">Known Risks</a>
 </h4>
@@ -644,7 +663,20 @@
                 </p>
             </blockquote>
 <pre>
-Examples:
+Examples (Heraldry):
+
+  [1] Information on Yadis can be found at:
+    http://yadis.org 
+    http://www.openidenabled.com
+
+  [2] Information on OpenID can be found at:
+    http://www.openid.net 
+    http://www.openidenabled.com
+
+  The mailing list for both OpenID and Yadis is located at:
+    http://lists.danga.com/mailman/listinfo/yadis
+  ...
+
 </pre>
 </div>
 <h4>
@@ -708,13 +740,17 @@
 <div class="section-content">
 <blockquote>
 <p>
-External dependencies for the initial source is important. Apache has policy
+External dependencies for the initial source is important. Apache has 
+<a href="http://www.apache.org/legal/3party.html">policy</a>
 about dependencies allowed for projects. These are (to some extent) relaxed
 for projects under incubation. Listing dependencies and licenses allows any
 possible problems to be highlighted and the appropriate actions planned.
 </p>
 <pre>
-Examples:
+Example (CeltiXfire):
+
+  The dependencies all have Apache compatible licenses. These include BSD, 
+  CDDL, CPL, MPL and MIT licensed dependencies.
 </pre>
             </blockquote>
 </div>
@@ -725,7 +761,8 @@
 <blockquote>
 <p>
 If the proposal involves cryptographic code either directly or indirectly,
-Apache needs to know so that the relevant paperwork can be obtained.
+Apache needs to know so that the 
+<a href="http://www.apache.org/dev/crypto.html">relevant paperwork</a> can be
obtained.
 </p>
             </blockquote>
 </div>
@@ -745,7 +782,9 @@
 <div class="section-content">
 <blockquote>
                 <p>
-             Minimum project-private (for PMC) project-dev listing
+The minimum required lists are <em>project</em>-private 
+(for confidential <a href="ppmc.html">PPMC</a> discussions) 
+and  <em>project</em>-dev lists. 
                 </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. 
@@ -754,14 +793,41 @@
 and user lists in the usual way.
                 </p><p>
 Existing open source projects moving to Apache will probably want to adopt the
-same mailing list set up here as they have already. 
-                </p>
+same mailing list set up here as they have already. However, the transition for users may
+prove more smooth if only the development lists are bootstrapped initially. The user
+lists can then be migrated by a simple podling vote once the Apache infrastructure 
+is ready and fully prepared.
+                </p>
+                <p>
+It is conventional to use an all lower case, dash-separated (<code>-</code>)
 prefix
+based on the project name. 
+                </p>
+<pre>
+  Example:
+  
+    * beehive-ppmc (with moderated subscriptions)
+    * beehive-dev
+    * beehive-commits
+    * beehive-user
+</pre>
             </blockquote>
 </div>
 <h5> 
    <a name="template-subversion-directory">Subversion Directory</a> 
 </h5> 
 <div class="section-content">
+<blockquote>
+        	<p>
+It is conventional to use all lower case, dash-separated (<code>-</code>) directory
names.
+The directory should be within the incubatory directory space 
+(<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
+        	</p>
+<pre>
+Example:
+
+   https://svn.apache.org/repos/asf/incubator/openjpa
+</pre>
+			</blockquote>
 </div>
 <h5> 
    <a name="template-issue-tracking">Issue Tracking</a> 
@@ -769,8 +835,15 @@
 <div class="section-content">
 <blockquote>
                 <p>
-Apache runs JIRA and Bugzilla.
+Apache runs <a href="https://issues.apache.org/jira/secure/Dashboard.jspa">JIRA</a>
+and <a href="http://issues.apache.org/bugzilla/">Bugzilla</a>. Choose one. Include
the
+name by which project will be known in the issue tracking system.
                 </p>
+<pre>
+Example:
+    
+    JIRA Open-JPA (OPEN-JPA)
+</pre>
             </blockquote>
 </div>
 <h5> 
@@ -787,9 +860,6 @@
 give an explanation. The Apache infrastructure team usually take some
 convincing before allowing new services on core Apache hardware.
                 </p>
-<pre>
-Examples:
-</pre>
                 </blockquote>
 </div>
 </div>
@@ -864,8 +934,21 @@
 <div class="section-content">
 <blockquote>
                 <p>
-[needs improvements?] A champion should be found before the proposal is
-submitted.
+The <a href="/incubation/Roles_and_Responsibilities.html#Champion">Champion</a>
is
+a person already associated with Apache who leads the proposal process. It is common 
+- but not necessary - for the Champion to also be proposed as a 
+<a href="#template-mentors">Mentor</a>. Note that since Mentors are appointed
+by the 
+<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">
+Incubator PMC</a> 
+as part of the acceptance process, they can 
+have no formal role before the proposal is submitted hence the need for a Champion.
+				</p>
+				<p>
+A Champion should be found before the proposal is formally submitted. 
+                </p>
+                <p>
+                [move this section into enter the incubator?]
                 </p>
                 </blockquote>
 </div>
@@ -902,8 +985,8 @@
 <div class="section-content">
 <blockquote>
                         <p>
-This is the organisational unit within Apache taking responsibility for this
-proposal.
+The <a href="/incubation/Roles_and_Responsibility.html#Sponsor">Sponsor</a> 
+is the organisational unit within Apache taking responsibility for this proposal.
 The sponsoring entity can be:
 </p>
 <ul>



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


Mime
View raw message