incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r371723 [3/4] - in /incubator/public/trunk/site: ./ xdocs/ xdocs/ipclearance/ xdocs/projects/ xdocs/stylesheets/
Date Mon, 23 Jan 2006 23:58:43 GMT
Modified: incubator/public/trunk/site/xdocs/process_description.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/process_description.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/process_description.xml (original)
+++ incubator/public/trunk/site/xdocs/process_description.xml Mon Jan 23 15:58:11 2006
@@ -1,71 +1,71 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="Process Description">
-
-<subsection name="The Process of Incubation">
-
-<p>The incubation process covers the establishment of a candidate, acceptance (or rejection) of a candidate leading to the potential establishment of a Podling and associated incubation process, which ultimately leads to the establishment or a new Apache Top-Level-Project (TLP) or sub-project within an existing Apache Project. </p>
-<p>
-<img alt="incubation-process.png" src="incubation-process.png"/></p>
-<p>Readers should also review the  <a href="site:incubation/rolesandersponsibilities">Roles and Responsibilities </a>document for a description of the various parties involved in the Incubation process. </p>
-
-</subsection>
-<subsection name="Establishment">
-
-<p>The first thing you will want to do is find a  <strong>Champion </strong> for your project.  One way to do this is to explore the Apache site to find similar projects.  Spend some time reading both the projects' web pages and mailing lists.  By simply lurking on the mailing lists (see Mailing Lists section  in this document), you may get ideas about who you would like to ask to help you with your project proposal.  However, Champions must either be ASF   <a href="ext:apache/foundation/members">members </a>or  <a href="ext:apache/foundation/officers">officers </a>(see the Champion section later in this document for more on Champion criteria and responsibilities).  Once you have found an eligible person who is willing to act as Champion, you can use this person to help you determine if and how your proposal can complement the ASF.  If you and your Champion are convinced that your candidate project would fit with the "Apache Way", your Champion can help you to get it establi
 shed. </p>
-<p>The establishment of a candidate involves the preparation of a project description (consistent with the candidate description detailed below) endorsed by a  <strong>Champion</strong> .   </p>
-<p>A  <strong>Candidate </strong> project description should be submitted to the relevant mailing list(s) of a  <strong>Sponsor </strong> (see the Mailing Lists section in this document).  See the  <a class="external" href="http://jakarta.apache.org/site/newproject.html">Jakarta Guidelines for New Projects </a>for a list of issues that should be addressed in your proposal; also see  <a class="external" href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF Proposal Pages </a>for other examples.  Typically a  <strong>Candidate </strong> is submitted under a message tagged with [[PROPOSAL].  Such a message will normally trigger some discussions on the receiving mailing list(s).  Your Champion will be involved in these discussions acting as your advocate. </p>
-<p>As a proposer you should consider the feedback and attempt to gauge a sense of consensus.  Do not be put off by extended threads under your initial post that have little or nothing to do with your proposal - however, if you feel that your candidate project is not being addressed, you may want to specifically request a decision on the Candidate by the Sponsor by posting a request to the decision making list (either pmc@{project-name}.apache.org or board@apache.org; see Mailing List section for more details).  Sometimes a vote will be announced without you asking for it (perhaps you have done some homework and have a PMC member assisting you though the process), other times you may need to cut through discussions and push your request forward for a decision. </p>
-
-</subsection>
-<subsection name="Acceptance">
-
-<p>The decision to accept a project is taken on a vote by the Sponsor.  The format of this vote will depend on the rules of the entity in question.  Here again it helps if you have a PMC Member (or board member if the Sponsor is the ASF board) aligned with your project (preferably as your Champion) because you stand a better chance of getting feedback about what is actually happening.  The Sponsor will typically take about 7-10 days before announcing a vote result.   </p>
-<p>If that vote is affirmative, the Sponsor will propose to the  <strong>Incubator PMC </strong> (referencing the voting result e-mail) that your candidate project be escalated to  <strong>Podling </strong> status.  The Sponsor will assign a  <strong>Mentor </strong> .  The Mentor may, or may not, be your original Champion.  If not, it is expected your Champion will remain involved during the rest of the Incubation process, providing as much assistance as possible. </p>
-<p>The Mentor is there to protect you, but be warned - the Mentor is also holding a big stick. The Mentor is automatically made a member of the Incubator PMC, and reports to both the PMC and the Sponsor about your overall health and suitability for eventual inclusion within the Apache Community (or recommendation to terminate).  However, the Mentor (with the assistance of the Champion) is also looking after you through the incubation.    </p>
-<p>One of the roles of the Mentor is to keep away the wolves - and in the case of incubation the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy and delays.  The Mentor can help you by guiding and protecting you from much of this based on his/her experience in the process and familiarity with the policy and procedures of incubation.  In performing their role, the Mentor is representing the Sponsor.   </p>
-<p>Your Sponsor, represented by your Mentor, has specific responsibilities towards you and the Incubator PMC.  There are a bunch of administrative and technical actions to take care of.  Your Mentor is responsible for ensuring that these things happen quickly and efficiently.  Also, your Mentor is going to help you out with the getting in place of the policies and procedures you use for introducing new comitters, decision making, etc.  These aspects will be watched closely by the Incubator PMC as they provide a good indication of community dynamics, health and correlation with Apache practices. </p>
-
-</subsection>
-<subsection name="Review">
-
-<p>As your project sorts things out and things stabilize (infrastructure, communications, decision making) you will inevitably come under an assessment by the Incubator PMC concerning the exit of your project from the incubator.  Keep in mind that exit can be a good things and bad thing.  Exit via escalation to a top-level project or perhaps a subproject of an existing PMC would typically be viewed as a positive exit.  On the other-hand, termination is also an exit condition that may be considered.  With an upcoming assessment it is generally a good idea to have your STATUS file right up to-date and to ensure that your Mentor is doing his/her job of evangelizing your project and has good picture of where you are relative to acceptance or the last assessment point.  This information will help the Incubator PMC to recommend the best action for for your project.   </p>
-<p>Conclusion of a review process will be a recommendation (to the Sponsor) of one of the following: </p>
-<ul>
-<li>termination; </li>
-<li>continuation under incubation with recommendations; or </li>
-<li>exit via escalation into Apache. </li>
-</ul>
-<p>Note that whilst this is a recommendation, it carries a lot of weight.  A Sponsor will only over-ride the recommendation of the Incubator in exceptional circumstances, and even then it is likely that the issue in question would be escalated to the ASF board for their consideration. </p>
-
-</subsection>
-<subsection name="Termination">
-
-<p>If you receive a recommendation for termination then you have a problem.  Chances are that there are either legal or structural problems with your project that in the opinion of the Incubator PMC are not resolvable within a reasonable time frame.  A termination decision is basically time to close down the project. However, you do have the right to appeal a termination decision with the Board of Directors and/or your Sponsor.  You should be aware that several Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely to be successful.  </p>
-
-</subsection>
-<subsection name="Continuation">
-
-<p>A recommendation by the Incubator PMC for continuation of incubation shall include development recommendations. The Incubator PMC has a responsibility to ensure that the recommended actions are tangible and quantifiable.  For example, an assessment could be that your project has not established a sufficient community to be viable, in which case the Incubator PMC is obliged to state specific targets that they consider as viable.  This does not necessarily mean that if you meet this target by the next review that you are out of incubation - but it does give you concrete achievements that you can cite. Your Mentor is also specifically accountable to you for ensuring that the recommendations for continuation are usable, substantive and tangible. If this is not the case, you have every right to appeal an Incubator decision to the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios should arise. </p>
-
-</subsection>
-<subsection name="Escalation">
-
-<p>For Podlings that aim to establish sub-projects or products within existing communities you are almost home-free. The main issues you need to deal with now is migration of your code into the target project, something you should be confident in doing based on the contacts and understanding you gained during initial establishment and incubation.   </p>
-<p>For projects aiming to be a Top-Level-Project (TLP), you have an additional obstacle, namely the ASF Board.  While the ASF Board might be your Sponsor, this does not mean they have formally accepted you as a TLP.  To establish a TLP you need to draft a board motion that identifies the project scope, mission and charter.  You can submit the motion to the Board using the board@apache.org email address.  Well-prepared projects will have already developed contacts with members of the Board so this should not be a surprise agenda item.  Keep in mind that the Board can approve your motion as supplied, amend it, or reject it.  If you are rejected then you need to sort this out with the Incubator PMC and allies you have developed during the incubation process. In other words, for a TLP objective the Incubator PMC okay is only half of the story.   </p>
-<p>However, in practice, assuming you are building contacts with members in Apache, the Incubator PMC, and the ASF Board, the transition from Podling to TLP should be a smooth and painless process. </p>
-
-</subsection>
-</section>
-
- </body>
- </document>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="Process Description">
+
+<subsection name="The Process of Incubation">
+
+<p>The incubation process covers the establishment of a candidate, acceptance (or rejection) of a candidate leading to the potential establishment of a Podling and associated incubation process, which ultimately leads to the establishment or a new Apache Top-Level-Project (TLP) or sub-project within an existing Apache Project. </p>
+<p>
+<img alt="incubation-process.png" src="incubation-process.png"/></p>
+<p>Readers should also review the  <a href="site:incubation/rolesandersponsibilities">Roles and Responsibilities </a>document for a description of the various parties involved in the Incubation process. </p>
+
+</subsection>
+<subsection name="Establishment">
+
+<p>The first thing you will want to do is find a  <strong>Champion </strong> for your project.  One way to do this is to explore the Apache site to find similar projects.  Spend some time reading both the projects' web pages and mailing lists.  By simply lurking on the mailing lists (see Mailing Lists section  in this document), you may get ideas about who you would like to ask to help you with your project proposal.  However, Champions must either be ASF   <a href="ext:apache/foundation/members">members </a>or  <a href="ext:apache/foundation/officers">officers </a>(see the Champion section later in this document for more on Champion criteria and responsibilities).  Once you have found an eligible person who is willing to act as Champion, you can use this person to help you determine if and how your proposal can complement the ASF.  If you and your Champion are convinced that your candidate project would fit with the "Apache Way", your Champion can help you to get it establi
 shed. </p>
+<p>The establishment of a candidate involves the preparation of a project description (consistent with the candidate description detailed below) endorsed by a  <strong>Champion</strong> .   </p>
+<p>A  <strong>Candidate </strong> project description should be submitted to the relevant mailing list(s) of a  <strong>Sponsor </strong> (see the Mailing Lists section in this document).  See the  <a class="external" href="http://jakarta.apache.org/site/newproject.html">Jakarta Guidelines for New Projects </a>for a list of issues that should be addressed in your proposal; also see  <a class="external" href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF Proposal Pages </a>for other examples.  Typically a  <strong>Candidate </strong> is submitted under a message tagged with [[PROPOSAL].  Such a message will normally trigger some discussions on the receiving mailing list(s).  Your Champion will be involved in these discussions acting as your advocate. </p>
+<p>As a proposer you should consider the feedback and attempt to gauge a sense of consensus.  Do not be put off by extended threads under your initial post that have little or nothing to do with your proposal - however, if you feel that your candidate project is not being addressed, you may want to specifically request a decision on the Candidate by the Sponsor by posting a request to the decision making list (either pmc@{project-name}.apache.org or board@apache.org; see Mailing List section for more details).  Sometimes a vote will be announced without you asking for it (perhaps you have done some homework and have a PMC member assisting you though the process), other times you may need to cut through discussions and push your request forward for a decision. </p>
+
+</subsection>
+<subsection name="Acceptance">
+
+<p>The decision to accept a project is taken on a vote by the Sponsor.  The format of this vote will depend on the rules of the entity in question.  Here again it helps if you have a PMC Member (or board member if the Sponsor is the ASF board) aligned with your project (preferably as your Champion) because you stand a better chance of getting feedback about what is actually happening.  The Sponsor will typically take about 7-10 days before announcing a vote result.   </p>
+<p>If that vote is affirmative, the Sponsor will propose to the  <strong>Incubator PMC </strong> (referencing the voting result e-mail) that your candidate project be escalated to  <strong>Podling </strong> status.  The Sponsor will assign a  <strong>Mentor </strong> .  The Mentor may, or may not, be your original Champion.  If not, it is expected your Champion will remain involved during the rest of the Incubation process, providing as much assistance as possible. </p>
+<p>The Mentor is there to protect you, but be warned - the Mentor is also holding a big stick. The Mentor is automatically made a member of the Incubator PMC, and reports to both the PMC and the Sponsor about your overall health and suitability for eventual inclusion within the Apache Community (or recommendation to terminate).  However, the Mentor (with the assistance of the Champion) is also looking after you through the incubation.    </p>
+<p>One of the roles of the Mentor is to keep away the wolves - and in the case of incubation the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy and delays.  The Mentor can help you by guiding and protecting you from much of this based on his/her experience in the process and familiarity with the policy and procedures of incubation.  In performing their role, the Mentor is representing the Sponsor.   </p>
+<p>Your Sponsor, represented by your Mentor, has specific responsibilities towards you and the Incubator PMC.  There are a bunch of administrative and technical actions to take care of.  Your Mentor is responsible for ensuring that these things happen quickly and efficiently.  Also, your Mentor is going to help you out with the getting in place of the policies and procedures you use for introducing new comitters, decision making, etc.  These aspects will be watched closely by the Incubator PMC as they provide a good indication of community dynamics, health and correlation with Apache practices. </p>
+
+</subsection>
+<subsection name="Review">
+
+<p>As your project sorts things out and things stabilize (infrastructure, communications, decision making) you will inevitably come under an assessment by the Incubator PMC concerning the exit of your project from the incubator.  Keep in mind that exit can be a good things and bad thing.  Exit via escalation to a top-level project or perhaps a subproject of an existing PMC would typically be viewed as a positive exit.  On the other-hand, termination is also an exit condition that may be considered.  With an upcoming assessment it is generally a good idea to have your STATUS file right up to-date and to ensure that your Mentor is doing his/her job of evangelizing your project and has good picture of where you are relative to acceptance or the last assessment point.  This information will help the Incubator PMC to recommend the best action for for your project.   </p>
+<p>Conclusion of a review process will be a recommendation (to the Sponsor) of one of the following: </p>
+<ul>
+<li>termination; </li>
+<li>continuation under incubation with recommendations; or </li>
+<li>exit via escalation into Apache. </li>
+</ul>
+<p>Note that whilst this is a recommendation, it carries a lot of weight.  A Sponsor will only over-ride the recommendation of the Incubator in exceptional circumstances, and even then it is likely that the issue in question would be escalated to the ASF board for their consideration. </p>
+
+</subsection>
+<subsection name="Termination">
+
+<p>If you receive a recommendation for termination then you have a problem.  Chances are that there are either legal or structural problems with your project that in the opinion of the Incubator PMC are not resolvable within a reasonable time frame.  A termination decision is basically time to close down the project. However, you do have the right to appeal a termination decision with the Board of Directors and/or your Sponsor.  You should be aware that several Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely to be successful.  </p>
+
+</subsection>
+<subsection name="Continuation">
+
+<p>A recommendation by the Incubator PMC for continuation of incubation shall include development recommendations. The Incubator PMC has a responsibility to ensure that the recommended actions are tangible and quantifiable.  For example, an assessment could be that your project has not established a sufficient community to be viable, in which case the Incubator PMC is obliged to state specific targets that they consider as viable.  This does not necessarily mean that if you meet this target by the next review that you are out of incubation - but it does give you concrete achievements that you can cite. Your Mentor is also specifically accountable to you for ensuring that the recommendations for continuation are usable, substantive and tangible. If this is not the case, you have every right to appeal an Incubator decision to the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios should arise. </p>
+
+</subsection>
+<subsection name="Escalation">
+
+<p>For Podlings that aim to establish sub-projects or products within existing communities you are almost home-free. The main issues you need to deal with now is migration of your code into the target project, something you should be confident in doing based on the contacts and understanding you gained during initial establishment and incubation.   </p>
+<p>For projects aiming to be a Top-Level-Project (TLP), you have an additional obstacle, namely the ASF Board.  While the ASF Board might be your Sponsor, this does not mean they have formally accepted you as a TLP.  To establish a TLP you need to draft a board motion that identifies the project scope, mission and charter.  You can submit the motion to the Board using the board@apache.org email address.  Well-prepared projects will have already developed contacts with members of the Board so this should not be a surprise agenda item.  Keep in mind that the Board can approve your motion as supplied, amend it, or reject it.  If you are rejected then you need to sort this out with the Incubator PMC and allies you have developed during the incubation process. In other words, for a TLP objective the Incubator PMC okay is only half of the story.   </p>
+<p>However, in practice, assuming you are building contacts with members in Apache, the Incubator PMC, and the ASF Board, the transition from Podling to TLP should be a smooth and painless process. </p>
+
+</subsection>
+</section>
+
+ </body>
+ </document>

Propchange: incubator/public/trunk/site/xdocs/process_description.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/site/xdocs/projects/activemq.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/projects/activemq.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/projects/activemq.xml (original)
+++ incubator/public/trunk/site/xdocs/projects/activemq.xml Mon Jan 23 15:58:11 2006
@@ -1,357 +1,357 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="ActiveMQ 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/activemq">project website</a>.
-</p>
-
-<subsection name="Description">
-
-<p>
-The ActiveMQ project is a robust and high performance Message Orientated Middleware provider which is 
-integrated into Apache Geronimo but also be usable from inside any JVM.
-</p>
-
-</subsection>
-<subsection 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>
-
-</subsection>
-<subsection name="Project Info">
-
-<!--
-<ul>
-  <li>link to the main website </li>
-</ul>
-
-<ul>
-  <li>link to the page(s) that tell how to participate (Website,Mailing
-lists,Bug tracking,Source code) </li>
-</ul>
-
-<ul>
-  <li>link to the project status file (Committers,non-incubation action
-        items,project resources, etc) </li>
-</ul>
--->
-
-<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/activemq/">http://incubator.apache.org/activemq/</a></td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>dev </td>
-      <td>activemq-dev@geronimo.apache.org </td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>users </td>
-      <td>activemq-users@geronimo.apache.org </td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>commits </td>
-      <td>activemq-commits@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/activemq/<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>
-
-</subsection>
-<subsection name="Incubation Status Reports">
-
-<ul>
-  <li>[none yet]</li>
-</ul>
-
-</subsection>
-<subsection name="Incubation Work Items">
-
-</subsection>
-<subsection name="Project Setup">
-
-<p>
-This is the first phase on incubation, needed to start the project
-at Apache. This is currently in progress.
-</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>
-
-<strong>Identify the project to be incubated</strong>
-<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>N/A <br/>
-      </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 <br/>
-      </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>
-
-<strong>Interim responsibility</strong>
-<table>
-    <tr>
-      <th>date </th>
-      <th>item </th>
-    </tr>
-    <tr>
-      <td>TBD </td>
-      <td>Identify all the Mentors for the incubation, by asking all
-that can be Mentors. </td>
-    </tr>
-    <tr>
-      <td>TBD <br/>
-      </td>
-      <td>Subscribe all Mentors on the pmc and general lists. </td>
-    </tr>
-    <tr>
-      <td>TBD <br/>
-      </td>
-      <td>Give all Mentors access to all incubator CVS modules. (to be
-done by PMC chair) </td>
-    </tr>
-    <tr>
-      <td>TBD <br/>
-      </td>
-      <td>Tell Mentors to track progress in the file
-'incubator/projects/activemq.html' </td>
-    </tr>
-</table>
-
-<strong>Copyright</strong>
-<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>
-
-<strong>Verify distribution rights</strong>
-<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>
-
-<strong>Establish a list of active committers</strong>
-<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
-cvs.apache.org. </td>
-    </tr>
-</table>
-
-<strong>Infrastructure</strong>
-<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>
-
-<strong>Project specific </strong>
-<p>
-<em>Add project specific tasks here.</em> </p>
-
-
-<strong>Incubation </strong>
-<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>
-
-<strong>Collaborative Development </strong>
-<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>
-<strong>Licensing awareness </strong>
-<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>
-
-<strong>Exit</strong>
-<p>
-<em>Things to check for before voting the project out.</em> </p>
-<strong>Organizational acceptance of responsibility for the project </strong>
-<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 name="Incubator sign-off">
-<ul>
-  <li>Has the Incubator decided that the project has accomplished all
-of the above tasks? </li>
-</ul>
-
-</subsection>
-
-</section>
-
-</body>
-</document>
-
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="ActiveMQ 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/activemq">project website</a>.
+</p>
+
+<subsection name="Description">
+
+<p>
+The ActiveMQ project is a robust and high performance Message Orientated Middleware provider which is 
+integrated into Apache Geronimo but also be usable from inside any JVM.
+</p>
+
+</subsection>
+<subsection 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>
+
+</subsection>
+<subsection name="Project Info">
+
+<!--
+<ul>
+  <li>link to the main website </li>
+</ul>
+
+<ul>
+  <li>link to the page(s) that tell how to participate (Website,Mailing
+lists,Bug tracking,Source code) </li>
+</ul>
+
+<ul>
+  <li>link to the project status file (Committers,non-incubation action
+        items,project resources, etc) </li>
+</ul>
+-->
+
+<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/activemq/">http://incubator.apache.org/activemq/</a></td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>dev </td>
+      <td>activemq-dev@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>users </td>
+      <td>activemq-users@geronimo.apache.org </td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>commits </td>
+      <td>activemq-commits@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/activemq/<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>
+
+</subsection>
+<subsection name="Incubation Status Reports">
+
+<ul>
+  <li>[none yet]</li>
+</ul>
+
+</subsection>
+<subsection name="Incubation Work Items">
+
+</subsection>
+<subsection name="Project Setup">
+
+<p>
+This is the first phase on incubation, needed to start the project
+at Apache. This is currently in progress.
+</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>
+
+<strong>Identify the project to be incubated</strong>
+<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>N/A <br/>
+      </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 <br/>
+      </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>
+
+<strong>Interim responsibility</strong>
+<table>
+    <tr>
+      <th>date </th>
+      <th>item </th>
+    </tr>
+    <tr>
+      <td>TBD </td>
+      <td>Identify all the Mentors for the incubation, by asking all
+that can be Mentors. </td>
+    </tr>
+    <tr>
+      <td>TBD <br/>
+      </td>
+      <td>Subscribe all Mentors on the pmc and general lists. </td>
+    </tr>
+    <tr>
+      <td>TBD <br/>
+      </td>
+      <td>Give all Mentors access to all incubator CVS modules. (to be
+done by PMC chair) </td>
+    </tr>
+    <tr>
+      <td>TBD <br/>
+      </td>
+      <td>Tell Mentors to track progress in the file
+'incubator/projects/activemq.html' </td>
+    </tr>
+</table>
+
+<strong>Copyright</strong>
+<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>
+
+<strong>Verify distribution rights</strong>
+<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>
+
+<strong>Establish a list of active committers</strong>
+<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
+cvs.apache.org. </td>
+    </tr>
+</table>
+
+<strong>Infrastructure</strong>
+<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>
+
+<strong>Project specific </strong>
+<p>
+<em>Add project specific tasks here.</em> </p>
+
+
+<strong>Incubation </strong>
+<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>
+
+<strong>Collaborative Development </strong>
+<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>
+<strong>Licensing awareness </strong>
+<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>
+
+<strong>Exit</strong>
+<p>
+<em>Things to check for before voting the project out.</em> </p>
+<strong>Organizational acceptance of responsibility for the project </strong>
+<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 name="Incubator sign-off">
+<ul>
+  <li>Has the Incubator decided that the project has accomplished all
+of the above tasks? </li>
+</ul>
+
+</subsection>
+
+</section>
+
+</body>
+</document>
+

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

Modified: incubator/public/trunk/site/xdocs/projects/project_template.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site/xdocs/projects/project_template.xml?rev=371723&r1=371722&r2=371723&view=diff
==============================================================================
--- incubator/public/trunk/site/xdocs/projects/project_template.xml (original)
+++ incubator/public/trunk/site/xdocs/projects/project_template.xml Mon Jan 23 15:58:11 2006
@@ -1,346 +1,346 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-
-<document>
-
- <properties>
-  <title>Apache Incubator</title>
-  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
- </properties>
-
- <body>
-
-<section name="##PROJECT_NAME Project Incubation Status">
-
-<p>
-This page tracks the project status, incubator-wise. For more
-general project status, look at the 
-<a href="##LINK_TO_PROJECT">project website</a>.
-</p>
-
-<p>
-This page tracks the project status pertaining to incubation. Items marked <b>DONE</b> have been completed.
-</p>
-
-<subsection name="Description">
-
-<p>
-##PUT_DESCRIPTION_HERE
-</p>
-
-</subsection>
-<subsection name="News">
-
-<ul>
-  <li>##YYYY-MM-DD Project accepted by Incubator</li>
-  <li>##YYYY-MM-DD Project proposed incubation in Apache.</li>
-</ul>
-
-</subsection>
-<subsection name="Project Info">
-
-<ul>
-  <li>link to the main website </li>
-</ul>
-
-<ul>
-  <li>link to the page(s) that tell how to participate (Website,Mailing
-lists,Bug tracking,Source code) </li>
-</ul>
-
-<ul>
-  <li>link to the project status file (Committers,non-incubation action
-        items,project resources, etc) </li>
-</ul>
-
-<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>##PROJECTS_SITE</td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>dev </td>
-      <td>##DEVLIST</td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>users </td>
-      <td>##USERLIST</td>
-    </tr>
-    <tr>
-      <td>Mailing list </td>
-      <td>commits </td>
-      <td>##COMMITLIST</td>
-    </tr>
-    <tr>
-      <td>Bug tracking </td>
-      <td>JIRA</td>
-      <td>##JIRA</td>
-    </tr>
-    <tr>
-      <td>Source code </td>
-      <td>svn</td>
-      <td>##SVN_REPO</td>
-    </tr>
-    <tr>
-      <td>Mentors </td>
-      <td></td>
-      <td>##MENTOR_NAME<br/>
-      </td>
-    </tr>
-    <tr>
-      <td>Committers </td>
-      <td></td>
-      <td>##COMMITTER_NAME</td>
-    </tr>
-    <tr>
-      <td></td>
-      <td></td>
-      <td></td>
-    </tr>
-</table>
-
-</subsection>
-<subsection name="Incubation Status Reports">
-
-<ul>
-  <li>[none yet]</li>
-</ul>
-
-</subsection>
-<subsection name="Incubation Work Items">
-
-</subsection>
-<subsection name="Project Setup">
-
-<p>
-This is the first phase on incubation, needed to start the project
-at Apache. This is currently in progress.
-</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>
-
-<strong>Identify the project to be incubated</strong>
-<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 cvs 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>
-
-<strong>Interim responsibility</strong>
-<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/activemq.html' 
-       </td>
-    </tr>
-</table>
-
-<strong>Copyright</strong>
-<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>
-
-<strong>Verify distribution rights</strong>
-<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>
-
-<strong>Establish a list of active committers</strong>
-<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
-cvs.apache.org. </td>
-    </tr>
-</table>
-
-<strong>Infrastructure</strong>
-<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>
-
-<strong>Project specific </strong>
-<p>
-<em>Add project specific tasks here.</em> </p>
-
-
-<strong>Incubation </strong>
-<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>
-
-<strong>Collaborative Development </strong>
-<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>
-<strong>Licensing awareness </strong>
-<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>
-
-<strong>Exit</strong>
-<p>
-<em>Things to check for before voting the project out.</em> </p>
-<strong>Organizational acceptance of responsibility for the project </strong>
-<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 name="Incubator sign-off">
-<ul>
-  <li>Has the Incubator decided that the project has accomplished all
-of the above tasks? </li>
-</ul>
-
-</subsection>
-
-</section>
-
-</body>
-</document>
-
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+
+ <properties>
+  <title>Apache Incubator</title>
+  <author email="general@incubator.apache.org">Incubator Documentation Team</author>
+ </properties>
+
+ <body>
+
+<section name="##PROJECT_NAME Project Incubation Status">
+
+<p>
+This page tracks the project status, incubator-wise. For more
+general project status, look at the 
+<a href="##LINK_TO_PROJECT">project website</a>.
+</p>
+
+<p>
+This page tracks the project status pertaining to incubation. Items marked <b>DONE</b> have been completed.
+</p>
+
+<subsection name="Description">
+
+<p>
+##PUT_DESCRIPTION_HERE
+</p>
+
+</subsection>
+<subsection name="News">
+
+<ul>
+  <li>##YYYY-MM-DD Project accepted by Incubator</li>
+  <li>##YYYY-MM-DD Project proposed incubation in Apache.</li>
+</ul>
+
+</subsection>
+<subsection name="Project Info">
+
+<ul>
+  <li>link to the main website </li>
+</ul>
+
+<ul>
+  <li>link to the page(s) that tell how to participate (Website,Mailing
+lists,Bug tracking,Source code) </li>
+</ul>
+
+<ul>
+  <li>link to the project status file (Committers,non-incubation action
+        items,project resources, etc) </li>
+</ul>
+
+<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>##PROJECTS_SITE</td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>dev </td>
+      <td>##DEVLIST</td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>users </td>
+      <td>##USERLIST</td>
+    </tr>
+    <tr>
+      <td>Mailing list </td>
+      <td>commits </td>
+      <td>##COMMITLIST</td>
+    </tr>
+    <tr>
+      <td>Bug tracking </td>
+      <td>JIRA</td>
+      <td>##JIRA</td>
+    </tr>
+    <tr>
+      <td>Source code </td>
+      <td>svn</td>
+      <td>##SVN_REPO</td>
+    </tr>
+    <tr>
+      <td>Mentors </td>
+      <td></td>
+      <td>##MENTOR_NAME<br/>
+      </td>
+    </tr>
+    <tr>
+      <td>Committers </td>
+      <td></td>
+      <td>##COMMITTER_NAME</td>
+    </tr>
+    <tr>
+      <td></td>
+      <td></td>
+      <td></td>
+    </tr>
+</table>
+
+</subsection>
+<subsection name="Incubation Status Reports">
+
+<ul>
+  <li>[none yet]</li>
+</ul>
+
+</subsection>
+<subsection name="Incubation Work Items">
+
+</subsection>
+<subsection name="Project Setup">
+
+<p>
+This is the first phase on incubation, needed to start the project
+at Apache. This is currently in progress.
+</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>
+
+<strong>Identify the project to be incubated</strong>
+<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 cvs 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>
+
+<strong>Interim responsibility</strong>
+<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/activemq.html' 
+       </td>
+    </tr>
+</table>
+
+<strong>Copyright</strong>
+<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>
+
+<strong>Verify distribution rights</strong>
+<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>
+
+<strong>Establish a list of active committers</strong>
+<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
+cvs.apache.org. </td>
+    </tr>
+</table>
+
+<strong>Infrastructure</strong>
+<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>
+
+<strong>Project specific </strong>
+<p>
+<em>Add project specific tasks here.</em> </p>
+
+
+<strong>Incubation </strong>
+<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>
+
+<strong>Collaborative Development </strong>
+<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>
+<strong>Licensing awareness </strong>
+<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>
+
+<strong>Exit</strong>
+<p>
+<em>Things to check for before voting the project out.</em> </p>
+<strong>Organizational acceptance of responsibility for the project </strong>
+<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 name="Incubator sign-off">
+<ul>
+  <li>Has the Incubator decided that the project has accomplished all
+of the above tasks? </li>
+</ul>
+
+</subsection>
+
+</section>
+
+</body>
+</document>
+

Propchange: incubator/public/trunk/site/xdocs/projects/project_template.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