incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r370716 [9/11] - in /incubator/public/trunk/site/xdocs2: ./ guides/ incubation/ ip-clearance/ learn/ projects/ projects/agila/ projects/geronimo/
Date Fri, 20 Jan 2006 03:11:54 GMT
Added: incubator/public/trunk/site/xdocs2/projects/pluto.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/pluto.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/pluto.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/pluto.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,370 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>pluto
+</title>
+  </properties>
+  <body>
+    <section id="Pluto+Project+Incubation+Status" name="Pluto Project Incubation Status">
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look on the project
+
+        <a href="http://jakarta.apache.org/pluto/">website
+</a>.
+
+      </p>
+    </section>
+    <section id="Description" name="Description">
+      <p>Pluto is the Reference Implementation of the Java Portlet
+Specfication. The current version of this specification is &lt;JSR
+168|http://jcp.org/en/jsr/detail?id=168]. Please read the
+
+        <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">proposal
+</a>that started the project in the incubator.
+
+      </p>
+    </section>
+    <section id="News" name="News">
+      <p>Pluto Graduated! On May 15, 2004, The Incubator PMC released Pluto to
+the Portals project. See thread at:
+</p>
+      <p>http://mail-archives.apache.org/eyebrowse/BrowseList?listName=general@
+ncubator.apache.org&amp;by=thread&amp;from=751960
+</p>
+    </section>
+    <section id="Project+info" name="Project info">
+      <ul>
+        <li>
+          <a href="http://jakarta.apache.org/pluto/">Website
+</a>
+        </li>
+        <li>
+          <a href="http://jakarta.apache.org/pluto/project-info.html">Project Info
+</a>
+        </li>
+        <li>
+          <a href="http://cvs.apache.org/viewcvs.cgi/jakarta-pluto/">CVS
+</a>
+        </li>
+        <li>
+          <a href="http://jakarta.apache.org/site/mail2.html#Pluto">Mailing Lists
+</a>
+        </li>
+      </ul>
+    </section>
+    <section id="Incubation+status+reports" name="Incubation status reports">
+      <subsection id="2004-05-01+Pluto+Status" name="2004-05-01 Pluto Status">
+        <source>2004-05-01 Pluto Status * Is the STATUS file up to date? (also post
+link) Yes. http://incubator.apache.org/projects/pluto.html * Any
+legal, cross-project or personal issues that still need to be
+addressed? No outstanding issues. * What has been done for incubation
+since the last report? All project committers have received
+confirmation that CLA's have been received and accepted. The Pluto
+has worked hard towards 1.0 release of the Pluto Portlet Container
+reference implementation. The release is ready, pending graduation of
+Pluto from incubation. The Pluto Web Site has continued to be updated
+and built out. http://jakarta.apache.org/pluto Upon graduation from
+incubation and acceptance into Apache Portals, Pluto will be moved to
+http://portals.apache.org/pluto All source files have been modified
+to include the ASF v2.0 copyright notice. The mailing lists
+pluto-dev@jakarta.apache.org and pluto-user@jakarta.apache.org are
+now being archived at both Apache and MARC. Past list traffic has
+been imported into the Apache archives. * What are the project's
+plans and expectations for the next period? Put out release 1.0 to
+coincide with the Java Portlet API Specification. Future work will
+include refactoring and compontenization of Pluto, and support of the
+next release of the Java Portlet API Specification. Assemble a to-do
+list (roadmap) for future development and publish to the Pluto web
+site. Exit the Apache Incubator (hey, it was fun). * Any
+recommendations for how incubation could run more smoothly for you?
+The current process has worked well for us.
+</source>
+      </subsection>
+    </section>
+    <section id="Incubation+work+items" name="Incubation work items">
+      <subsection id="Project+Setup" name="Project Setup">
+        <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>
+        <subsection id="Identify+the+project+to+be+incubated" name="Identify the project to be incubated">
+          <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>2003-09-13
+</td>
+              <td>If request from an existing Apache project to adopt an external
+package, then ask the Apache project for the cvs module and mail
+address names.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-13
+</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>2003-09-13
+</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>
+        </subsection>
+        <subsection id="Interim+responsibility" name="Interim responsibility">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-10-03
+</td>
+              <td>Identify all the Mentors for the incubation, by asking all that can
+be Mentors.
+</td>
+            </tr>
+            <tr>
+              <td>2003-10-03
+</td>
+              <td>Subscribe all Mentors on the pmc and general lists.
+</td>
+            </tr>
+            <tr>
+              <td>2003-10-03
+</td>
+              <td>Give all Mentors access to all incubator CVS modules. (to be done by
+PMC chair)
+</td>
+            </tr>
+            <tr>
+              <td>2003-10-03
+</td>
+              <td>Tell Mentors to track progress in the file
+'incubator/projects/{project.name}.cwiki'
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-05-03
+</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>2004-05-03
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-04-13
+</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>2004-04-13
+</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>
+        </subsection>
+        <subsection id="Establish+a+list+of+active+committers+%21" name="Establish a list of active committers !">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-01-21
+</td>
+              <td>Check that all active committers have submitted a contributors
+agreement.
+</td>
+            </tr>
+            <tr>
+              <td>2004-02-13
+</td>
+              <td>Add all active committers in the STATUS file.
+</td>
+            </tr>
+            <tr>
+              <td>2004-01-21
+</td>
+              <td>Ask root for the creation of committers' accounts on cvs.apache.org.
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Infrastructure+%21" name="Infrastructure !">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-09-13
+</td>
+              <td>Ask infrastructure to create source repository modules and grant the
+committers karma.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-13
+</td>
+              <td>Ask infrastructure to set up and archive Mailing lists.
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-13
+</td>
+              <td>Decide about and then ask infrastructure to setup an issuetracking
+system (Bugzilla, Scarab, Jira).
+</td>
+            </tr>
+            <tr>
+              <td>2003-09-13
+</td>
+              <td>Migrate the project to our infrastructure.
+</td>
+            </tr>
+          </table>
+        </subsection>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <ul>
+            <li>Have all of the active long-term volunteers been identified and
+acknowledged as committers on the project?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <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>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <li>Are project decisions being made in public by the committers?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <li>Are the decision-making guidelines published and agreed to by all of
+the committers?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <ul>
+            <li>If graduating to an existing PMC, has the PMC voted to accept it?
+</li>
+          </ul>
+          <p>Yes. The Apache Portals Project PMC has voted to unanimously accept
+Pluto into the Apache Portals project.
+</p>
+          <ul>
+            <li>If graduating to a new PMC, has the board voted to accept it?
+</li>
+          </ul>
+          <p>See above.
+</p>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+          <p>Yes. On May 15, 2004, The Incubator PMC released Pluto to the Portals
+project. See thread at:
+</p>
+          <p>http://mail-archives.apache.org/eyebrowse/BrowseList?listName=general@
+ncubator.apache.org&amp;by=thread&amp;from=751960
+</p>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/pluto.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/projects/roller.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/roller.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/roller.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/roller.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,538 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Roller Project Incubation Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Roller+Project+Incubation+Status" name="Roller Project Incubation Status">
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look on the project website.
+</p>
+    </section>
+    <section id="Description" name="Description">
+      <p>Roller is the open source blog server that drives Sun Microsystem's
+blogs.sun.com employee blogging site, the Javalobby's JRoller Java
+community site, and hundreds of other sites. If you want to set up a
+blog server for yourself or for several thousand of your closest
+friends, then Roller is the perfect choice..
+</p>
+    </section>
+    <section id="News" name="News">
+      <ul>
+        <li>none yet
+</li>
+      </ul>
+    </section>
+    <section id="Project+info" name="Project info">
+      <table>
+        <tr>
+          <th>item
+</th>
+          <th>type
+</th>
+          <th>reference
+</th>
+        </tr>
+        <tr>
+          <td>Website
+</td>
+          <td>www
+</td>
+          <td>
+            <a href="http://www.rollerweblogger.org/page/project">http://www.rollerweblogger.org/page/project
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>wiki
+</td>
+          <td>
+            <a href="http://www.rollerweblogger.org/wiki/Wiki.jsp">http://www.rollerweblogger.org/wiki/Wiki.jsp
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>roller-dev@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>user
+</td>
+          <td>roller-user@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>commits
+</td>
+          <td>roller-commits@roller.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>jira
+</td>
+          <td>
+            <a href="http://opensource2.atlassian.com/projects/roller/">http://opensource2.atlassian.com/projects/roller/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>SVN
+</td>
+          <td>incubator/roller
+</td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>rubys
+</td>
+          <td>Sam Ruby
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>bayard
+</td>
+          <td>Henri Yandell
+</td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>.
+</td>
+          <td>.
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>agilliland
+</td>
+          <td>Allen Gilliland
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>gangolli
+</td>
+          <td>Anil Gangolli
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>snoopdave
+</td>
+          <td>David Johnson
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>bayard
+</td>
+          <td>Henri Yandell
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>lance
+</td>
+          <td>Lance Lavandowska
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>mraible
+</td>
+          <td>Matt Raible
+</td>
+        </tr>
+        <tr>
+          <td>Extra
+</td>
+          <td>.
+</td>
+          <td>.
+</td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+status+reports" name="Incubation status reports">
+      <ul>
+        <li>none yet
+</li>
+      </ul>
+    </section>
+    <section id="Incubation+work+items" name="Incubation work items">
+      <subsection id="Project+Setup" name="Project Setup">
+        <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>
+        <subsection id="Identify+the+project+to+be+incubated" name="Identify the project to be incubated">
+          <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>
+        </subsection>
+        <subsection id="Interim+responsibility" name="Interim responsibility">
+          <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>
+        </subsection>
+        <subsection id="Copyright" name="Copyright">
+          <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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <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>
+        </subsection>
+        <subsection id="Establish+a+list+of+active+committers" name="Establish a list of active committers">
+          <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>
+        </subsection>
+        <subsection id="Infrastructure" name="Infrastructure">
+          <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>
+        </subsection>
+        <subsection id="Project+specific" name="Project specific">
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <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>
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <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>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+        </subsection>
+        <subsection id="Project+Specific" name="Project Specific">
+          <p>Below is the project STATUS.txt file. It needs integrating with the
+above list.
+</p>
+          <p/>
+          <pre>LEGAL * All code ASL'ed INCOMPLETE. We have a top-level ASL, but not
+all source files have had a notice added to them. * No non ASL or ASL
+compatbile dependencies in the code base INCOMPLETE. We have
+dependencies on some LGPL code, notably Hibernate, and the JSPWiki
+plugin. * License grant complete UNKNOWN. We believe this is
+complete. Mentor, please verify. * CLAs on file. COMPLETE. CLAs for
+all current committers are on file. * Check of project name for
+trademark issues UNKNOWN. We believe the Roller Weblogger name to be
+free of trademark issues. Will Apache Legal be responsible to
+confirm? If not, what verification should be undertaken by project
+developers? MERITOCRACY * Demonstrate an active and diverse
+development community BELIEVED COMPLETE. We believe we satisfy this
+today with our current set of committers, and we are open to
+additional qualified developers. * The project is not highly
+dependent on any single contributor (there's at least 3 legally
+independent committers and there is no single company or entity that
+is vital to the success of the project). BELIEVED COMPLETE. We
+believe we satisfy this today with the current set of committers. *
+The above implies that new committers are admitted according to ASF
+practices ONGOING. We will admit new committers according to ASF
+practices. * ASF style voting has been adopted and is standard
+practice ONGOING. We have been using ASF-style voting since before
+our entry into incubation, and we plan to maintain this practice with
+some additional rigor / regularity. * Demonstrate ability to tolerate
+and resolve conflict within the community. ONGOING. The community has
+been able to do this successfully to date. There has been very little
+in the way of conflict however. We use the development mailing list
+for discussions and request votes as necessary. * Release plans are
+developed and excuted in public by the community. ONGOING. We use the
+mailing lists to announce release plans and accept comments. * Note:
+incubator projects are not permitted to issue an official Release.
+Test snapshots (however good the quality) and Release plans are OK.
+NOTED. We will likely wish to release "test snapshots" with
+"incubating" clearly noted in the packaging. * Destination PMC, or
+ASF Board for a TLP, has voted for final acceptance INCOMPLETE. This
+will be our final step (or among them), after meeting other
+requirements. ALIGNMENT / SYNERGY * Use of other ASF subprojects
+BELIEVED COMPLETE. Roller depends on at least the following Apache
+components: Struts, Velocity (Jakarta), Lucene, Log4j (Logging), some
+elements of the Jakarta Commons libraries. In addition, we favor
+Tomcat as a servlet container, to the extent that we provide primary
+installation guide documentation and additional user support for
+configuring Roller on Tomcat. We also depend on the Rome project
+components (RSS/Atom support) which we expect will be in incubation
+during a period overlapping that of the Roller project. * Develop
+synergistic relationship with other ASF subprojects UNKNOWN. We're
+great at using the other ASF stuff; hopefully we'll find ways to give
+back. INFRASTRUCTURE * CVS module has been created COMPLETE. SVN
+module has been created at
+https://svn.apache.org/repos/asf/incubator/roller/trunk/ * Mailing
+list(s) have been created COMPLETE. Roller developer list
+(roller-dev@incubator.apache.org) and Roller user list
+(roller-user@incubator.apache.org). * Mailing lists are being
+archived INCOMPLETE. Mentor, please help. * Bugzilla has been created
+BELIEVED INCOMPLETE. We need both to add Roller to the appropriate
+Bugzilla and to migrate from our current issue tracking
+(http://opensource.atlassian.com/projects/roller/). * Project website
+has been created INCOMPLETE. * Project ready to comply with ASF
+mirroring guidlines INCOMPLETE. * Project is integrated with GUMP if
+appropriate INCOMPLETE. * Releases are PGP signed by a member of the
+community INCOMPLETE. * Developers tied into ASF PGP web of trust
+INCOMPLETE.
+</pre>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <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>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/roller.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/projects/servicemix.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/servicemix.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/servicemix.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/servicemix.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,205 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>ServiceMix Incubation Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="ServiceMix+Project+Incubation+Status" name="ServiceMix Project Incubation Status">
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look at the
+
+        <a href="http://incubator.apache.org/servicemix">project website
+</a>.
+
+      </p>
+    </section>
+    <section id="Description" name="Description">
+      <p>The ServiceMix project is an ESB and component suite based on the
+Java Business Interface (JBI) standard - JSR 208.
+</p>
+    </section>
+    <section id="News" name="News">
+      <ul>
+        <li>2005-12-09 Project announced publicly.
+</li>
+        <li>2005-11-18 Project proposed and accepted for incubation in Apache.
+</li>
+      </ul>
+    </section>
+    <section id="Project+info" name="Project info">
+      <p>If the project website and code repository are not yet setup, use the
+following table:
+</p>
+      <table>
+        <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/servicemix/">http://incubator.apache.org/servicemix/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>servicemix-dev@geronimo.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>JIRA
+
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>svn
+
+            <br/>
+          </td>
+          <td>svn co http://svn.apache.org/repos/asf/incubator/servicemix/
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>James Strachan
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>James Strachan (jstrachan@logicblaze.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+Status+Reports" name="Incubation Status Reports">
+      <ul>
+        <li>[none yet]
+</li>
+      </ul>
+    </section>
+    <section id="Incubation+Work+Items" name="Incubation Work Items">
+      <subsection id="Project+Setup" name="Project Setup">
+        <p>This is the first phase on incubation, needed to start the project at
+Apache. This is currently in progress.
+</p>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <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>
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <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>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+        </subsection>
+        <subsection id="Project+Specific" name="Project Specific">
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <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>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/servicemix.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/projects/spamassassin.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/spamassassin.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/spamassassin.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/spamassassin.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,641 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties>
+    <title>spamassassin
+</title>
+  </properties>
+  <body>
+    <section id="SpamAssassin+Project+Incubation+Status" name="SpamAssassin Project Incubation Status">
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look on the project website.
+</p>
+    </section>
+    <section id="Description" name="Description">
+      <p>SpamAssassin(tm) is a mail filter to identify spam.
+</p>
+      <p>Using its rule base, it uses a wide range of heuristic tests on mail
+headers and body text to identify "spam", also known as unsolicited
+commercial email.
+</p>
+    </section>
+    <section id="News" name="News">
+      <ul>
+        <li>none yet
+</li>
+      </ul>
+    </section>
+    <section id="Project+info" name="Project info">
+      <table>
+        <tr>
+          <th>item
+</th>
+          <th>type
+</th>
+          <th>reference
+</th>
+        </tr>
+        <tr>
+          <td>Website
+</td>
+          <td>www
+</td>
+          <td>
+            <a href="http://spamassassin.org/">http://spamassassin.org/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>wiki
+</td>
+          <td>
+            <a href="http://wiki.apache.org/spamassassin/">http://wiki.apache.org/spamassassin/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>spamassassin-dev@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>cvs
+</td>
+          <td>spamassassin-cvs@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>ppmc
+</td>
+          <td>spamassassin-ppmc@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>users
+</td>
+          <td>spamassassin-users@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>devel-br
+</td>
+          <td>spamassassin-devel-br@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>devel-de
+</td>
+          <td>spamassassin-devel-de@incubator.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>announce
+</td>
+          <td>spamassassin-announce@lists.sourceforge.net
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>.
+</td>
+          <td>(replacement spamassassin-announce exists on incubator, but will not
+be used until graduation)
+</td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>.
+</td>
+          <td>
+            <a href="http://bugzilla.spamassassin.org/">http://bugzilla.spamassassin.org/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>SVN
+</td>
+          <td>incubator/spamassassin/
+</td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>striker
+</td>
+          <td>Sander Striker
+</td>
+        </tr>
+        <tr>
+          <td>PPMC
+</td>
+          <td>felicity
+</td>
+          <td>Theo Van Dinter
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>jm
+</td>
+          <td>Justin Mason
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>quinlan
+</td>
+          <td>Daniel Quinlan
+</td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>duncf
+</td>
+          <td>Duncan A. Findlay
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>felicity
+</td>
+          <td>Theo Van Dinter
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>jm
+</td>
+          <td>Justin Mason
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>mss
+</td>
+          <td>Malte Sebastian Stretz
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>parker
+</td>
+          <td>Michael Parker
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>quinlan
+</td>
+          <td>Daniel Quinlan
+</td>
+        </tr>
+        <tr>
+          <td>.
+</td>
+          <td>sidney
+</td>
+          <td>Sidney Markowitz
+</td>
+        </tr>
+        <tr>
+          <td>Extra
+</td>
+          <td>DNS
+</td>
+          <td>spamassassin.org
+</td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+status+reports" name="Incubation status reports">
+      <subsection id="2004-04-22" name="2004-04-22">
+        <source>* is the Incubation Status file up to date? (also post link) Yep --
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/s
+amassassin.cwiki * any legal, cross-project or personal issues that
+still need to be addressed? Copyright and distribution rights still
+remain to be verified by ASF. The trademark issue on the
+"SpamAssassin" name is still in progress. * what has been done for
+incubation since the last report? news.spamassassin.org has been shut
+down; it was becoming just a dumping-ground for third-party press
+releases, and Wiki pages were more appropriate. We're still waiting
+for trademark assignment to be taken care of. Also unsure if the ASF
+have vetted the CLA coverage of the current codebase. Mostly, the
+ball is in the ASF's court ;) Have received agreement from current
+domain holder of "spamassassin.org" that it will be transferred to
+the ASF. * plans and expectations for the next period? Hopefully
+we'll get the TM assignment taken care of, and the CLAs vetted; then
+we'll be ready (at least in terms of ASF procedures) to issue a 3.0.0
+release of SpamAssassin as an ASF project. * any recommendations for
+how incubation could run more smoothly for you? * etc (your own
+thoughts on what is important would be helpful!)
+</source>
+      </subsection>
+      <subsection id="2004-03-%3F%3F" name="2004-03-??">
+        <source>* STATUS is up to date
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/s
+amassassin.cwiki is now the canonical STATUS file and it is now
+up-to-date. The trunk copy points at it now. * 3.0.0 tree under
+development at ASF * 2.6x not under development at ASF
+</source>
+      </subsection>
+      <subsection id="2004-01-21" name="2004-01-21">
+        <source>* is the STATUS file up to date? (also post link)
+http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator/site/projects/s
+amassass in.cwiki Not quite -- the two 'Establish a list of active
+committers' items are not up to date. All active committers are now
+signed up, so that can be closed off. The second item is 'Add all
+active committers in the STATUS file.' However, I'm now confused.
+Which is the canonical STATUS file --
+/incubator/spamassassin/trunk/STATUS, or
+/incubator/site/projects/spamassassin.cwiki? Some signs seem to be
+pointing to the latter... so, if the latter, some cut and paste from
+the former to the latter is then required (and note, I don't think I
+or anyone else on the SpamAssassin PPMC have write access to it). I'm
+kind of taking the approach that the latter is the incubation
+checklist, and the former is tracking our assets and people. That may
+be wrong though BTW the former is here:
+http://svn.apache.org/repos/asf/incubator/spamassassin/trunk/STATUS
+Also, the two tasks under 'Verify distribution rights', should be
+complete. All code in the trunk is covered by CLAs, and the
+non-covered branches have README files noting their non-Apache status
+and presence for historical purposes only. However, perhaps this may
+need to be verified by the ASF before the task can be marked as
+complete, I'm not sure. * any legal, cross-project or personal issues
+that still need to be addressed? Copyright and distribution rights
+still remain to be verified, although all CLAs should now be in. --
+so it's up to ASF legal now. The trademark issue on the
+"SpamAssassin" name is still in progress; as far as I know, NAI legal
+still need to provide some documentation to DW, Jim Jagielski et al.
+* what has been done for incubation since the last report? Lots! - -
+all committer accounts are set up; - - source code is now running
+from the Apache Incubator SVN repository; - - all of the
+developer-oriented mailing lists are now at the Incubator - although
+some user-oriented lists are still external, to avoid user confusion;
+- - all code has been vetted for CLA coverage, and removed or
+clean-roomed if a CLA could not be provided, and this is now awaiting
+verification by the ASF; - - and all major code or rules files in SVN
+are tagged with the ASL 1.1. - - The Wiki has been moved to
+wiki.apache.org. * plans and expectations for the next period? We
+need to transition more infrastructure, including our main website,
+Wiki and Bugzilla. Bugzilla uses some custom code to track CLAs,
+which would be nice to bring over. We also plan to finish up the
+legal situation, by getting the CLA coverage verified by the ASF,
+then the trademark. Also we have several cron scripts that are used
+to perform distributed rule QA, and a very large rsync server contain
+2.7Gb of data, which will need to be migrated. What to do with these
+is still a topic of discussion, since they're *big* in terms of disk
+space usage, and there may not be room at the ASF infrastructure for
+this! There's also a spamtrap server which almost definitely should
+*not* come along -- it handles approx 1 Gbit of traffic per day (in
+spam reports) and would be a waste of ASF hardware and bandwidth,
+IMO. * any recommendations for how incubation could run more smoothly
+for you? A little more introductory doco would be nice; I hadn't
+heard of http://www.apache.org/dev/ until quite late in the process,
+and there were a few other issues where I had to hop around the
+apache.org website to figure out what things meant or what a given
+procedure was. Also, one thing I'm concerned about is how many
+aspects of our infrastructure will wind up with "incubator" in their
+URL or hostname; as a mature project, it'd be much easier to
+transition with the minimum of changes for the existing community,
+and this scoping of URLs and hostnames as in incubation means an
+additional change once we leave the incubator. As a result, it gives
+us a bit of an incentive to *not* set things up (lists, etc.) until
+we leave.
+</source>
+      </subsection>
+    </section>
+    <section id="Incubation+work+items" name="Incubation work items">
+      <subsection id="Project+Setup" name="Project Setup">
+        <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>
+        <subsection id="Identify+the+project+to+be+incubated" name="Identify the project to be incubated">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-02-16
+</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>DONE
+</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>
+          <p>
+            <em>NOTE
+</em>
+          </p>
+          <source>There is a trademark
+</source>
+        </subsection>
+        <subsection id="Interim+responsibility" name="Interim responsibility">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-12-20
+</td>
+              <td>Identify all the Mentors for the incubation, by asking all that can
+be Mentors.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+</td>
+              <td>Subscribe all Mentors on the pmc and general lists.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+</td>
+              <td>Give all Mentors access to all incubator CVS modules. (to be done by
+PMC chair)
+</td>
+            </tr>
+            <tr>
+              <td>2003-12-29
+</td>
+              <td>Tell Mentors to track progress in the file
+'incubator/projects/spamassassin.cwiki'
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-02-16
+</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>2004-02-16
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Check and make sure that for all code included with the distribution
+that is not under the Apache license, we have the right to combine
+with Apache-licensed code and redistribute.
+</td>
+            </tr>
+            <tr>
+              <td>DONE
+</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>
+        </subsection>
+        <subsection id="Establish+a+list+of+active+committers" name="Establish a list of active committers">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2004-01-21
+</td>
+              <td>Check that all active committers have submitted a contributors
+agreement.
+</td>
+            </tr>
+            <tr>
+              <td>2004-01-21
+</td>
+              <td>Add all active committers in the STATUS file.
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Infrastructure" name="Infrastructure">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>2003-12-23
+</td>
+              <td>Ask root for the creation of committers' accounts on svn.apache.org.
+</td>
+            </tr>
+            <tr>
+              <td>2004-01-07
+</td>
+              <td>Ask infrastructure to create source repository modules and grant the
+committers karma.
+</td>
+            </tr>
+            <tr>
+              <td>2003-12-25
+</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>
+          <p>
+            <em>NOTES
+</em>
+          </p>
+          <source>Discussion is underway to whether SA wants to use Jira, or wants to
+import their BZ database into the existing ASF installation.
+</source>
+          <source>The moving to the ASF infrastructure is partly delayed by the limited
+resources available in the ASF Infrastructure team (time). Also, this
+mature project has quite a lot of infrastructure to move. I suggest
+we don't let this be one of the points to keep SA in the Incubator;
+the intent to move to the ASF infrastructure is there.
+</source>
+        </subsection>
+        <subsection id="Project+specific" name="Project specific">
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <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>
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <ul>
+            <li>Have all of the active long-term volunteers been identified and
+acknowledged as committers on the project?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <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>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <li>Are project decisions being made in public by the committers?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+          <ul>
+            <li>Are the decision-making guidelines published and agreed to by all of
+the committers?
+</li>
+          </ul>
+          <p>Yes.
+</p>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+          <p>Two trademarks are being assigned to the ASF:
+</p>
+          <p>SpamAssassin:
+http://assignments.uspto.gov/assignments/q?db=tm&amp;sno=78148991
+</p>
+          <p>Powered by SpamAssassin:
+http://assignments.uspto.gov/assignments/q?db=tm&amp;sno=78213077
+</p>
+        </subsection>
+        <subsection id="Project+Specific" name="Project Specific">
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <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>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/spamassassin.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/projects/stdcxx.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/stdcxx.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/stdcxx.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/stdcxx.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,768 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Apache stdcxx Incubation Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Apache+stdcxx+Incubation+Status" name="Apache stdcxx Incubation Status">
+      <div class="section">
+        <p>This page tracks the incubation status of the stdcxx project.
+</p>
+      </div>
+    </section>
+    <section id="Description" name="Description">
+      <div class="section">
+        <p>The Apache C++ Standard Library project is a complete implementation
+of the ISO/IEC 14882 C++ Standard Library.
+</p>
+        <p>The most distinguishing characteristic of this implementation of the
+C++ Standard Library is its portability to a large number of C++
+compilers, operating systems, and hardware architectures.
+</p>
+      </div>
+    </section>
+    <section id="News" name="News">
+      <div class="section">
+        <ul>
+          <li>11/25/2005 Windows configuration and build infarstructure
+
+            <a href="http://svn.apache.org/viewcvs.cgi?rev=349027&amp;view=rev">committed
+</a>to Subversion (
+
+            <a href="http://issues.apache.org/jira/browse/stdcxx-5">stdcxx-5
+</a>).
+
+          </li>
+          <li>9/16/2005 The first
+
+            <a href="http://cvs.apache.org/dist/incubator/stdcxx/snapshots/stdcxx-incubating-4.1.2-2005-07-19.tar.gz">snapshot
+</a>of stdcxx 4.1.2 has been published.
+
+          </li>
+          <li>9/5/2005 The test suite driver
+
+            <a href="http://svn.apache.org/viewcvs.cgi/incubator/stdcxx/trunk/tests/?rev=278837">committed
+</a>to Subversion (
+
+            <a href="http://issues.apache.org/jira/browse/stdcxx-3">stdcxx-3
+</a>).
+
+          </li>
+          <li>9/1/2005 A
+
+            <a href="http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200508.mbox/%3c430E39CD.7040501@roguewave.com%3e">proposal
+</a>to publish the first stdcxx snapshot on the stdcxx Web site has
+passed the community
+
+            <a href="http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200509.mbox/%3c4317A0AE.9040204@roguewave.com%3e">vote
+</a>.
+
+          </li>
+          <li>8/28/2005 The process of downloading stdcxx files documented on the
+
+            <a href="http://incubator.apache.org/stdcxx/download.html">Download
+</a>page. (See
+
+            <a href="http://issues.apache.org/jira/browse/stdcxx-17">stdcxx-17
+</a>).
+
+          </li>
+          <li>8/01/2005 The process of reporting bugs in the stdcxx
+
+            <a href="http://issues.apache.org/jira/browse/stdcxx">bug tracking database
+</a>documented and published on the
+
+            <a href="http://incubator.apache.org/stdcxx/bugs.html">Bugs
+</a>page. (See
+
+            <a href="http://issues.apache.org/jira/browse/stdcxx-9">stdcxx-9
+</a>.)
+
+          </li>
+          <li>7/19/2005 stdcxx
+
+            <a href="http://incubator.apache.org/stdcxx">project page
+</a>and
+
+            <a href="http://incubator.apache.org/projects/stdcxx.html">status page
+</a>committed to subversion.
+
+          </li>
+          <li>7/18/2005 stdcxx sources and documentation moved to
+
+            <a href="http://svn.apache.org/repos/asf/incubator/stdcxx/">subversion
+</a>.
+
+          </li>
+          <li>5/19/2005 stdcxx project
+
+            <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200505.mbox/%3cC398496DF88AD711908C00065BEEE32C01473785@dfwmail.quovadx.com%3e">accepted
+</a>for incubation.
+
+          </li>
+          <li>5/13/2005 stdcxx project
+
+            <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200505.mbox/%3cC398496DF88AD711908C00065BEEE32C01473747@dfwmail.quovadx.com%3e">proposal
+</a>.
+
+          </li>
+        </ul>
+      </div>
+    </section>
+    <section id="Project+Info" name="Project Info">
+      <div class="section">
+        <table>
+          <tr>
+            <th>item
+</th>
+            <th>id
+</th>
+            <th>reference
+</th>
+          </tr>
+          <tr>
+            <td>Web site
+</td>
+            <td>www
+</td>
+            <td>
+              <a href="http://incubator.apache.org/stdcxx/">http://incubator.apache.org/stdcxx/
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>wiki
+</td>
+            <td>Wiki not requested.
+</td>
+          </tr>
+          <tr>
+            <td>Mailing lists
+</td>
+            <td>dev
+</td>
+            <td>
+              <a href="mailto:stdcxx-dev@incubator.apache.org">stdcxx-dev@incubator.apache.org
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>user
+</td>
+            <td>
+              <a href="mailto:stdcxx-user@incubator.apache.org">stdcxx-user@incubator.apache.org
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>svn
+</td>
+            <td>
+              <a href="mailto:stdcxx-commits@incubator.apache.org">stdcxx-commits@incubator.apache.org
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>ppmc
+</td>
+            <td>
+              <a href="mailto:stdcxx-ppmc@incubator.apache.org">stdcxx-ppmc@incubator.apache.org
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td>Moderators
+</td>
+            <td>sebor
+</td>
+            <td>
+              <a href="mailto:sebor_at_apache_dot_org">Martin Sebor
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>wrowe
+</td>
+            <td>
+              <a href="mailto:wrowe_at_rowe-clan_dot_net">William A. Rowe, Jr.
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td>Bug tracking
+</td>
+            <td>jira
+</td>
+            <td>
+              <a href="http://issues.apache.org/jira/browse/stdcxx">http://issues.apache.org/jira/browse/stdcxx
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td>Source code
+</td>
+            <td>svn
+</td>
+            <td>
+              <a href="http://svn.apache.org/repos/asf/incubator/stdcxx/">http://svn.apache.org/repos/asf/incubator/stdcxx/
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td>Sponsor
+</td>
+            <td/>
+            <td>
+              <a href="mailto:pmc_at_incubator_dot_apache_dot_org">Incubator PMC
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td>Mentors
+</td>
+            <td>jerenkrantz
+</td>
+            <td>
+              <a href="mailto:justin_at_erenkrantz_dot_com">Justin Erenkrantz
+</a>(See this
+
+              <a href="http://www.mail-archive.com/general@incubator.apache.org/msg04836.html">post
+</a>.)
+
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>ben
+</td>
+            <td>
+              <a href="mailto:ben_at_algroup_dot_co_dot_uk">Ben Laurie
+</a>(See this
+
+              <a href="http://www.mail-archive.com/general@incubator.apache.org/msg04844.html">post
+</a>.)
+
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>wrowe
+</td>
+            <td>
+              <a href="mailto:wrowe_at_rowe-clan_dot_net">William A. Rowe, Jr.
+</a>(See this
+
+              <a href="http://www.mail-archive.com/general@incubator.apache.org/msg04972.html">post
+</a>.)
+
+            </td>
+          </tr>
+          <tr>
+            <td id="committers">Committers
+</td>
+            <td>hbuelow
+</td>
+            <td>
+              <a href="mailto:heidi_dot_buelow_at_apache_dot_org">Heidi Buelow
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>ldiduck
+</td>
+            <td>
+              <a href="mailto:lancediduck_at_nyc_dot_rr_dot_com">Lance Diduck
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>jhollis
+</td>
+            <td>
+              <a href="mailto:johnh_at_roguewave_dot_com">John Hollis
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>ajindal
+</td>
+            <td>
+              <a href="mailto:jindal_at_roguewave_dot_com">Amit Jindal
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>lnicoara
+</td>
+            <td>
+              <a href="mailto:nicoara_at_roguewave_dot_com">Liviu Nicoara
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>rpalepu
+</td>
+            <td>
+              <a href="mailto:palepu_at_roguewave_dot_com">
+                <em>Ravi Palepu
+</em>
+              </a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>sebor
+</td>
+            <td>
+              <a href="mailto:sebor_at_roguewave_dot_com">Martin Sebor
+</a>
+            </td>
+          </tr>
+          <tr>
+            <td/>
+            <td>ttriemstra
+</td>
+            <td>
+              <a href="mailto:ttriemstra_at_apache_org">Tim Triemstra
+</a>
+            </td>
+          </tr>
+        </table>
+        <p>Committers in
+
+          <em>italics
+</em>do not have a signed
+
+          <a href="http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf">Contributor License Agreement
+</a>on file.
+
+        </p>
+      </div>
+    </section>
+    <section id="Incubation+Status+Reports" name="Incubation Status Reports">
+      <div class="section">
+        <table>
+          <tr>
+            <th>file
+</th>
+            <th>note
+</th>
+          </tr>
+          <tr>
+            <td>
+              <a href="http://svn.apache.org/viewcvs/incubator/stdcxx/site/status/2005-09.text">2005-12.text
+</a>
+            </td>
+            <td>Status report for the calendar quarter ending in 12/2005.
+</td>
+          </tr>
+          <tr>
+            <td>
+              <a href="http://svn.apache.org/viewcvs/incubator/stdcxx/site/status/2005-09.text">2005-09.text
+</a>
+            </td>
+            <td>Status report for the calendar quarter ending in 9/2005.
+</td>
+          </tr>
+        </table>
+      </div>
+    </section>
+    <section id="Incubation+Work+Items" name="Incubation Work Items">
+      <p/>
+      <subsection id="Project+Setup" name="Project Setup">
+        <p/>
+        <subsection id="Identify+the+project+to+be+incubated" name="Identify the project to be incubated">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>TBD
+</td>
+              <td>Make sure that the requested project name does not already exist and
+check
+
+                <a href="http://www.nameprotect.com">NameProtect
+</a>to be sure that the name is not already trademarked for an existing
+software product.
+
+              </td>
+            </tr>
+            <tr>
+              <td>N/A
+</td>
+              <td>If request from an existing Apache project to adopt an external
+package, then ask the Apache project for the cvs module and mail
+address names.
+</td>
+            </tr>
+            <tr>
+              <td>N/A
+</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>N/A
+</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>
+        </subsection>
+        <subsection id="Interim+responsibility" name="Interim responsibility">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Identify all the Mentors for the incubation, by asking all that can
+be Mentors.
+</td>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Subscribe all Mentors on the pmc and general lists.
+</td>
+            </tr>
+            <tr>
+              <td>TBD
+</td>
+              <td>Give all Mentors access to all incubator SVN modules (to be done by
+PMC chair).
+</td>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Tell Mentors to track progress in the status file.
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Copyright" name="Copyright">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE
+</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>In progress
+</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>
+        </subsection>
+        <subsection id="Verify+distribution+rights" name="Verify distribution rights">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Check and make sure that for all code included with the distribution
+that is not under the Apache license, has the right to combine with
+Apache-licensed code and redistribute.
+</td>
+            </tr>
+            <tr>
+              <td>DONE
+</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>
+        </subsection>
+        <subsection id="Establish+a+list+of+active+committers" name="Establish a list of active committers">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>7/11/2005
+</td>
+              <td>Check that all active committers have submitted a contributors
+agreement (see the list of
+
+                <a href="#committers">committers
+</a>above for any exceptions).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/19/2005
+</td>
+              <td>Add all active committers in the STATUS file.
+</td>
+            </tr>
+            <tr>
+              <td>7/16/2005
+</td>
+              <td>Ask root to create committers' accounts on cvs.apache.org (
+
+                <a href="http://issues.apache.org/jira/browse/INFRA-440">INFRA-440
+</a>).
+
+              </td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Infrastructure" name="Infrastructure">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>7/16/2005
+</td>
+              <td>Ask infrastructure to create source repository modules and grant the
+committers karma (
+
+                <a href="http://issues.apache.org/jira/browse/INFRA-441">INFRA-441
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/13/2005
+</td>
+              <td>Ask infrastructure to set up and archive mailing lists (
+
+                <a href="http://issues.apache.org/jira/browse/INFRA-339">INFRA-339
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/16/2005
+</td>
+              <td>Decide about and then ask infrastructure to setup an issue tracking
+system (
+
+                <a href="http://issues.apache.org/jira/browse/INFRA-438">INFRA-438
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>DONE
+</td>
+              <td>Migrate the project to our infrastructure.
+</td>
+            </tr>
+          </table>
+        </subsection>
+        <subsection id="Project-specific" name="Project-specific">
+          <table>
+            <tr>
+              <th>date
+</th>
+              <th>item
+</th>
+            </tr>
+            <tr>
+              <td>8/2/2005 - 8/3/2005
+</td>
+              <td>Publish a
+
+                <a href="http://incubator.apache.org/stdcxx/bugs.html">page
+</a>on how to file issues against the project and how to submit patches (
+
+                <a href="http://issues.apache.org/jira/browse/STDCXX-9">INFRA-9
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - 7/31/2005
+</td>
+              <td>Improve the
+
+                <a href="http://incubator.apache.org/stdcxx/">project page
+</a>(
+
+                <a href="http://issues.apache.org/jira/browse/STDCXX-6">INFRA-6
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - ...
+</td>
+              <td>Make the
+
+                <a href="http://svn.apache.org/repos/asf/incubator/stdcxx/trunk/doc/stdlibref/">Class Reference
+</a>and
+
+                <a href="http://svn.apache.org/repos/asf/incubator/stdcxx/trunk/doc/stdlibug/">Users Guide
+</a>available online, from the project page.
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - 9/16/2005
+</td>
+              <td>Make a snapshot of stable project sources available for download from
+the project site.
+</td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - ...
+</td>
+              <td>Document the design and development practices and publish them on the
+project site.
+</td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - ...
+</td>
+              <td>Put together a list of things to do and publish it on the project
+site.
+</td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - 9/5/2005
+</td>
+              <td>Check in the test driver (
+
+                <a href="http://issues.apache.org/jira/browse/stdcxx-3">STDCXX-3
+</a>).
+
+              </td>
+            </tr>
+            <tr>
+              <td>7/25/2005 - ...
+</td>
+              <td>Check in the project test suite (
+
+                <a href="http://issues.apache.org/jira/browse/stdcxx-4">STDCXX-4
+</a>).
+
+              </td>
+            </tr>
+          </table>
+        </subsection>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <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>
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <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>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+        </subsection>
+        <subsection id="Project-specific-N10439" name="Project-specific">
+          <p>
+            <em>No project-specific tasks.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <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>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/stdcxx.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/public/trunk/site/xdocs2/projects/synapse.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs2/projects/synapse.xml?rev=370716&view=auto
==============================================================================
--- incubator/public/trunk/site/xdocs2/projects/synapse.xml (added)
+++ incubator/public/trunk/site/xdocs2/projects/synapse.xml Thu Jan 19 19:10:36 2006
@@ -0,0 +1,385 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<document>
+  <properties><!--
+
+    <meta content="HTML Tidy, see www.w3.org" name="generator"/>-->
+<!--
+
+    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>-->
+
+    <title>Synapse Incubation Status
+</title>
+    <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
+  </properties>
+  <body>
+    <section id="Synapse+Project+Incubation+Status" name="Synapse Project Incubation Status">
+      <p>This page tracks the project status, incubator-wise. For more general
+project status, look at the
+
+        <a href="http://incubator.apache.org/synapse">project website
+</a>.
+
+      </p>
+    </section>
+    <section id="Description" name="Description">
+      <p>The Synapse project will create a robust, lightweight implementation
+of a highly scalable and distributed service mediation framework
+based on Web services specifications.
+</p>
+    </section>
+    <section id="News" name="News">
+      <ul>
+        <li>2005-08-22 Project announced publicly.
+</li>
+        <li>2005-08-13 Project proposed and accepted for incubation in Apache.
+</li>
+      </ul>
+    </section>
+    <section id="Project+info" name="Project info">
+      <p>If the project website and code repository are not yet setup, use the
+following table:
+</p>
+      <table>
+        <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/synapse/">http://incubator.apache.org/synapse/
+</a>
+          </td>
+        </tr>
+        <tr>
+          <td>Mailing list
+</td>
+          <td>dev
+</td>
+          <td>synapse-dev@ws.apache.org
+</td>
+        </tr>
+        <tr>
+          <td>Bug tracking
+</td>
+          <td>JIRA
+
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>Source code
+</td>
+          <td>svn
+
+            <br/>
+          </td>
+          <td>svn co http://svn.apache.org/repos/asf/incubator/synapse/
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>Mentors
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>Davanum Srinivas
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Sanjiva Weerawarana
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Glen Daniels
+</td>
+        </tr>
+        <tr>
+          <td>Committers
+</td>
+          <td>
+            <br/>
+          </td>
+          <td>Fabrice Medio (fmedio@bluetitan.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Dan Kulp (daniel.kulp@iona.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Adi Sakala (adi.sakala@iona.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Carl Trieloff (ctrieloff@iona.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Sathish Kumar T.K (sathish@infravio.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>D. Hariharasudhan (hari@infravio.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>P. Vikas Roonwal (vikas@infravio.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Dave Chappell (chappell@sonicsoftware.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Glen Daniels (gdaniels@apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Paul Fremantle (paul@wso2.com)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Davanum Srinivas (dims@apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Sanjiva Weerawarana (sanjiva@apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Eran Chinthaka (chinthaka@apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Chamikara Jayalath (chamikara@apache.org)
+
+            <br/>
+          </td>
+        </tr>
+        <tr>
+          <td>
+            <br/>
+          </td>
+          <td>
+            <br/>
+          </td>
+          <td>Sanka Samaranayake (sanka@opensource.lk)
+
+            <br/>
+          </td>
+        </tr>
+      </table>
+    </section>
+    <section id="Incubation+Status+Reports" name="Incubation Status Reports">
+      <ul>
+        <li>[none yet]
+</li>
+      </ul>
+    </section>
+    <section id="Incubation+Work+Items" name="Incubation Work Items">
+      <subsection id="Project+Setup" name="Project Setup">
+        <p>This is the first phase on incubation, needed to start the project at
+Apache. This is currently in progress.
+</p>
+      </subsection>
+      <subsection id="Incubation" name="Incubation">
+        <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>
+        <subsection id="Collaborative+Development" name="Collaborative Development">
+          <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>
+        </subsection>
+        <subsection id="Licensing+awareness" name="Licensing awareness">
+          <ul>
+            <li>Are all licensing, trademark, credit issues being taken care of and
+acknowleged by all committers?
+</li>
+          </ul>
+        </subsection>
+        <subsection id="Project+Specific" name="Project Specific">
+          <p>
+            <em>Add project specific tasks here.
+</em>
+          </p>
+        </subsection>
+      </subsection>
+      <subsection id="Exit" name="Exit">
+        <p>
+          <em>Things to check for before voting the project out.
+</em>
+        </p>
+        <subsection id="Organizational+acceptance+of+responsibility+for+the+project" name="Organizational acceptance of responsibility for the project">
+          <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>
+        </subsection>
+        <subsection id="Incubator+sign-off" name="Incubator sign-off">
+          <ul>
+            <li>Has the Incubator decided that the project has accomplished all of
+the above tasks?
+</li>
+          </ul>
+        </subsection>
+      </subsection>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/site/xdocs2/projects/synapse.xml
------------------------------------------------------------------------------
    svn:eol-style = native



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


Mime
View raw message