incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdud...@apache.org
Subject svn commit: r356604 - /incubator/public/trunk/site-author/projects/wadi.html
Date Tue, 13 Dec 2005 20:17:28 GMT
Author: bdudney
Date: Tue Dec 13 12:17:20 2005
New Revision: 356604

URL: http://svn.apache.org/viewcvs?rev=356604&view=rev
Log:
adding wadi stuff

Added:
    incubator/public/trunk/site-author/projects/wadi.html

Added: incubator/public/trunk/site-author/projects/wadi.html
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/wadi.html?rev=356604&view=auto
==============================================================================
--- incubator/public/trunk/site-author/projects/wadi.html (added)
+++ incubator/public/trunk/site-author/projects/wadi.html Tue Dec 13 12:17:20 2005
@@ -0,0 +1,331 @@
+<?xml version="1.0"?>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+  <head>
+    <META http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+    <title>WADI Incubation Status</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </head>
+  <body>
+    <h1>WADI Project Incubation Status</h1>
+    <p>This page tracks the project status, incubator-wise. For more general project
status, look on the project website. </p>
+    <h1>Description</h1>
+    <p>Achieving software infrastructure scalability is a tenet of Return on Investment
(ROI) for any IT infrastructure and usually takes place in two forms: vertical scalability
and horizontal scalability. Vertical addresses the scalability within the software itself
whereas horizontal deals with it from the amount of hardware that can be utilized. Clustering,
load balancing and failover is a necessity for any application server to be taken seriously
in the enterprise in terms of scalability. Without the ability to cluster the application
server, vertical scalability cannot take place. Without such vertical scalability, applications
built on top of it can only be scaled horizontally. In order to make Geronimo more enterprise
ready, it needs to provide such vertical scalability.</p>
+
+<p>WADI is a clustering, load balancing and failover solution for the web application
container tier. It currently supports both Jetty and Tomcat and plans are currently afoot
to add full J2EE clustering functionality. WADI will help Geronimo to achieve vertical scalability.</p>
+    <h1>News</h1>
+    <ul>
+      <li>[none yet]</li>
+    </ul>
+    <h1>Project info</h1>
+    <table>
+      <tbody>
+	<tr>
+	  <th>item </th>
+	  <th>type </th>
+	  <th>reference </th>
+	</tr>
+	<tr>
+	  <td>Website </td>
+	  <td>www</td>
+	  <td><a href="http://incubator.apache.org/wadi">http://incubator.apache.org/wadi</a></td>
+	</tr>
+    <tr>
+      <td>WADI WIKI</td>
+      <td>wiki </td>
+      <td><a href="http://wiki.apache.org/wadi/">http://wiki.apache.org/wadi/</a><br>
+      </td>
+    </tr>
+    <tr>
+      <td>Mailing List</td>
+      <td>dev</td>
+      <td>wadi-dev@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>commits</td>
+      <td>SCM</td>
+      <td>wadi-commits@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>Project Management Committe</td>
+      <td>PMC</td>
+      <td>wadi-ppmc@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>User Mailing List</td>
+      <td>user</td>
+      <td>wadi-user@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>Bug tracking </td>
+      <td>JIRA <br>
+      </td>
+      <td> http://issues.apache.org/jira/browse/WADI<br>
+      </td>
+    </tr>
+    <tr>
+      <td>Source code </td>
+      <td>svn<br>
+      </td>
+      <td>incubator/wadi<br>
+      </td>
+    </tr>
+    <tr>
+      <td>Mentor</td>
+      <td> <br>
+      </td>
+      <td>Geir Magnusson Jr.<br>
+      </td>
+    </tr>
+    <tr>
+      <td>Mentor</td>
+      <td> <br>
+      </td>
+      <td>James Strachan<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Committers<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Bill Dudeny<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Bruce Snyder<br>
+      </td>
+    </tr>
+    <tr>
+	<td style="vertical-align: top;"><br>
+	      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Jan Bartel<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Greg Wilkins<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">James Strachan<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Jeff Genender<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Jules Gosnell<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">Gianni Scenini<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">James Goodwill<br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+    </ul>
+    <h1>Incubation status reports</h1>
+    <ul>
+      <li>[none yet]</li>
+    </ul>
+    <h1>Incubation work items</h1>
+    <h2>Project Setup</h2>
+    <p>This is the first phase on incubation, needed to start the project at Apache.
</p>
+    <p>
+      <em>Item assignment is shown by the Apache id.</em>
+      <em>Completed tasks are shown by the completion date (YYYY-MM-dd). </em>
+    </p>
+    <h3>Identify the project to be incubated&#xD;
+</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Make sure that the requested project name does not already exist and check
www.nameprotect.com to be sure that the name is not already trademarked for an existing software
product. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>If request from an existing Apache project to adopt an external package,
then ask the Apache project for the SVN module and mail address names. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>If request from outside Apache to enter an existing Apache project, then
post a message to that project for them to decide on acceptance. </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>If request from anywhere to become a stand-alone PMC, then assess the fit
with the ASF, and create the lists and modules under the incubator address/module names if
accepted. </td>
+      </tr>
+    </table>
+    <h3>Interim responsibility</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Identify all the Mentors for the incubation, by asking all that can be
Mentors.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Subscribe all Mentors on the pmc and general lists.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Give all Mentors access to all incubator CVS modules. (to be done by PMC
chair)   </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'
 </td>
+      </tr>
+    </table>
+    <h3>Copyright</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check and make sure that the papers that transfer rights to the ASF been
received. It is only necessary to transfer rights for the package, the core code, and any
new code produced by the project.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check and make sure that the files that have been donated have been updated
to reflect the new ASF copyright.  </td>
+      </tr>
+    </table>
+    <h3>Verify distribution rights</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check and make sure that for all code included with the distribution that
is not under the Apache license, e have the right to combine with Apache-licensed code and
redistribute.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check and make sure that all source code distributed by the project is
covered by one or more of the following approved licenses:  Apache, BSD, Artistic, MIT/X,
MIT/W3C, MPL 1.1, or something with essentially the same terms. </td>
+      </tr>
+    </table>
+    <h3>Establish a list of active committers</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Check that all active committers have submitted a contributors agreement.
 </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Add all active committers in the STATUS file.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask root for the creation of committers' accounts on people.apache.org.
 </td>
+      </tr>
+    </table>
+    <h3>Infrastructure</h3>
+    <table>
+      <tr>
+        <th>date  </th>
+        <th>item </th>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask infrastructure to create source repository modules and grant the committers
karma.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Ask infrastructure to set up and archive Mailing lists.  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Decide about and then ask infrastructure to setup an issuetracking system
(Bugzilla, Scarab, Jira).  </td>
+      </tr>
+      <tr>
+        <td>....-..-..  </td>
+        <td>Migrate the project to our infrastructure.  </td>
+      </tr>
+    </table>
+    <h3>Project specific </h3>
+    <p>
+      <em>Add project specific tasks here.</em>
+    </p>
+    <h2>Incubation </h2>
+    <p>These action items have to be checked for during the whole incubation process.
</p>
+    <p>
+      <em>These items are not to be signed as done during incubation, as they may change
during incubation.  </em>
+      <em>They are to be looked into and described in the status reports and completed
in the request for incubation signoff.  </em>
+    </p>
+    <h3>Collaborative Development </h3>
+    <ul>
+      <li>Have all of the active long-term volunteers been identified and acknowledged
as committers on the project? </li>
+      <li>Are there three or more independent committers? (The legal definition of
independent is long and boring, but basically it means that there is no binding relationship
between the individuals, such as a shared employer, that is capable of overriding their free
will as individuals, directly or indirectly.) </li>
+      <li>Are project decisions being made in public by the committers? </li>
+      <li>Are the decision-making guidelines published and agreed to by all of the
committers? </li>
+    </ul>
+    <h3>Licensing awareness </h3>
+    <ul>
+      <li>Are all licensing, trademark, credit issues being taken care of and acknowleged
by all committers? </li>
+    </ul>
+    <h3>Project Specific </h3>
+    <p>
+      <em>Add project specific tasks here.</em>
+    </p>
+    <h2>Exit </h2>
+    <p>
+      <em>Things to check for before voting the project out.</em>
+    </p>
+    <h3>Organizational acceptance of responsibility for the project </h3>
+    <ul>
+      <li>If graduating to an existing PMC, has the PMC voted to accept it? </li>
+      <li>If graduating to a new PMC, has the board voted to accept it? </li>
+    </ul>
+    <h3>Incubator sign-off </h3>
+    <ul>
+      <li>Has the Incubator decided that the project has accomplished all of the above
tasks? </li>
+    </ul>
+  </body>
+</html>



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


Mime
View raw message