Erik Hatcher wrote:
Getting the Forrest website going would be a good step to tackle. See the Incubator site for some details, as well as cloning how Nutch is set up:
http://incubator.apache.org/projects/nutch.html
Well, I don't think I have the karma to commit to the incubator section of the repository, but here's a diff to create a page similar to the Nutch one. If someone can either commit this or tell me what needs to be done to get me the appropriate karma so I can update it myself I'd appreciate it.
There seems to be some variation between the various incubator projects, some use lists and web sites at incubator.apache.org, some use ones at their sponsoring project. I went the same way Nutch did, with lists at the incubator, if this is incorrect let me know and I'll correct it. Also, nutch listed their non-apache web site as the "Project Website", so I've done the same, I hope that's correct.
There are also TODO items on the list that we've accomplished (like having the Lucene PMC vote on acceptance), but I figure it's best to leave everything incomplete until this gets into Subversion, then make incremental changes so there's a record of each thing happening.
-garrett
Index: site-author/projects/lucene4c.html =================================================================== --- site-author/projects/lucene4c.html (revision 0) +++ site-author/projects/lucene4c.html (revision 0) @@ -0,0 +1,261 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> +<html> +<head> +<META http-equiv="Content-Type" content="text/html; charset=UTF-8"> +<title>Lucene4c Incubation Status</title> +<link href="http://purl.org/DC/elements/1.0/"; rel="schema.DC"> +</head> +<body> + +<h1>Lucene4c Project Incubation Status</h1> +<p>This page tracks the project status, incubator-wise. For more +general project status, look on the project website. </p> + +<h1>Description</h1> +<p>Lucene4c is a port of the +<a href="http://lucene.apache.org/java/";>Lucene</a> search engine from Java +to C, built on top of the +<a href="http://apr.apache.org/";>Apache Portable Runtime</a>.</p> + +<p>Unlike other Lucene ports, Lucene4c does not simply stick to the API used +in the original Java based Lucene, instead it attempts to build an idiomatic +APR/C based API that will be familiar to C programmers while making use of the +file formats and algorithms created by the original Lucene project.</p> + +<h1>News</h1> +<ul><li>none yet </li></ul> + +<h1>Project info</h1> +<ul><li>Project Website: + <a href="http://electricjellyfish.net/garrett/lucene4c/";>http://electricjellyfish.net/garrett/lucene4c/</a></li></ul> +<ul><li>Project Mailing Lists: + None yet.</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/lucene4c/";>http://incubator.apache.org/lucene4c/</a></td> + </tr> + <tr> + <td></td><td>wiki</td><td>None, will use Lucene wiki for the time being</td> + </tr> + <tr><td>Mailing list</td> + <td>dev</td><td>[EMAIL PROTECTED]</td></tr> + <tr><td></td><td>commits</td><td>[EMAIL PROTECTED]</td></tr> + <tr><td>Bug tracking</td><td>Jira</td><td><a href="http://issues.apache.org/jira";>http://issues.apache.org/jira/</a></td></tr> + + <tr> + <td>Source code</td><td>SVN</td><td><a href="https://svn.apache.org/repos/asf/incubator/lucene4c";>https://svn.apache.org/repos/asf/incubator/lucene4c</a></td> + </tr> + <tr><td>Mentors</td><td>ehatcher</td><td>Erik Hatcher</td></tr> + + <tr><td>Committers</td><td>rooneg</td><td>Garrett Rooney</td></tr> + </tr> +</table> + +<h1>Incubation status reports</h1> +<ul> +<li>none yet </li> +</ul> + +<h1>Incubation work items</h1> + +<h2>Project Setup</h2> +<p>This is the first phase on incubation, needed to start the project + at Apache. </p> +<p> +<em>Item assignment is shown by the Apache id.</em> +<em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em> +</p> + +<h3>Identify the project to be incubated +</h3> +<table> + <tr> + <th>date</th><th>item</th> + </tr> + <tr> + <td>....-..-..</td><td>Make sure that the requested project name + does not already exist and check www.nameprotect.com to be sure that + the name is not already trademarked for an existing software + product.</td> + </tr> + <tr> + <td>....-..-..</td><td>If request from an existing Apache project to + adopt an external package, then ask the Apache project for the 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> +<h3>Interim responsibility</h3> +<table> + <tr> + <th>date</th><th>item</th> + </tr> + <tr> + <td>....-..-..</td><td>Identify all the Mentors for the incubation, + by asking all that can be Mentors.</td> + </tr> + <tr> + <td>....-..-..</td><td>Subscribe all Mentors on the pmc and general + lists.</td> + </tr> + <tr> + <td>....-..-..</td><td>Give all Mentors access to all incubator CVS + modules. (to be done by PMC chair)</td> + </tr> + <tr> + <td>....-..-..</td><td>Tell Mentors to track progress in the file + 'incubator/projects/{project.name}.cwiki'</td> + </tr> +</table> +<h3>Copyright</h3> +<table> +<tr> +<th>date</th><th>item</th> +</tr> +<tr> + <td>....-..-..</td><td>Check and make sure that the papers that + transfer rights to the ASF been received. It is only necessary to + transfer rights for the package, the core code, and any new code + produced by the project.</td> + </tr> + <tr> + <td>....-..-..</td><td>Check and make sure that the files that have + been donated have been updated to reflect the new ASF + copyright.</td> + </tr> +</table> +<h3>Verify distribution rights</h3> +<table> + <tr> + <th>date</th><th>item</th> + </tr> + <tr> + <td>....-..-..</td><td>Check and make sure that for all code + included with the distribution that is not under the Apache license, + e have the right to combine with Apache-licensed code and + redistribute.</td> + </tr> + <tr> + <td>....-..-..</td><td>Check and make sure that all source code + distributed by the project is covered by one or more of the + following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, + MPL 1.1, or something with essentially the same terms.</td> + </tr> +</table> +<h3>Establish a list of active committers !</h3> +<table> + <tr> + <th>date</th><th>item</th> + </tr> + <tr> + <td>....-..-..</td><td>Check that all active committers have + submitted a contributors agreement.</td> + </tr> + <tr> + <td>....-..-..</td><td>Add all active committers in the STATUS + file.</td> + </tr> + <tr> + <td>....-..-..</td><td>Ask root for the creation of committers' + accounts on cvs.apache.org.</td> + </tr> +</table> + +<h3>Infrastructure !</h3> +<table> + <tr> + <th>date</th><th>item</th> + </tr> + <tr> + <td>....-..-..</td><td>Ask infrastructure to create source + repository modules and grant the committers karma.</td> + </tr> + <tr> + <td>....-..-..</td><td>Ask infrastructure to set up and archive + Mailing lists.</td> + </tr> + <tr> + <td>....-..-..</td><td>Decide about and then ask infrastructure to + setup an issuetracking system (Bugzilla, Scarab, Jira).</td> + </tr> + <tr> + <td>....-..-..</td><td>Migrate the project to our + infrastructure.</td> + </tr> +</table> + +<h3>Project specific </h3> +<p> +<em>Add project specific tasks here.</em> +</p> + +<h2>Incubation </h2> +<p>These action items have to be checked for during the whole +incubation process. </p> +<p> +<em>These items are not to be signed as done during incubation, as +they may change during incubation. </em> <em>They are to be looked +into and described in the status reports and completed in the request +for incubation signoff. </em> +</p> + +<h3>Collaborative Development </h3> +<ul> +<li>Have all of the active long-term volunteers been identified and +acknowledged as committers on the project? </li> +<li>Are there three or more independent committers? (The legal +definition of independent is long and boring, but basically it means +that there is no binding relationship between the individuals, such as +a shared employer, that is capable of overriding their free will as +individuals, directly or indirectly.) </li> +<li>Are project decisions being made in public by the committers? +</li> +<li>Are the decision-making guidelines published and agreed to by all +of the committers? </li> +</ul> + +<h3>Licensing awareness </h3> +<ul> +<li>Are all licensing, trademark, credit issues being taken care of +and acknowleged by all committers? </li> +</ul> + +<h3>Project Specific </h3> +<p> +<em>Add project specific tasks here.</em> +</p> + +<h2>Exit </h2> +<p> +<em>Things to check for before voting the project out.</em> +</p> +<h3>Organizational acceptance of responsibility for the project </h3> +<ul> +<li>If graduating to an existing PMC, has the PMC voted to accept it? +</li> +<li>If graduating to a new PMC, has the board voted to accept it? +</li> +</ul> +<h3>Incubator sign-off </h3> +<ul> +<li>Has the Incubator decided that the project has accomplished all of +the above tasks? </li> +</ul> +</body> +</html> Index: site-author/projects/index.html =================================================================== --- site-author/projects/index.html (revision 154750) +++ site-author/projects/index.html (working copy) @@ -173,8 +173,18 @@ <td colspan="1" rowspan="1">2004-01-31</td> </tr> - + <tr> + +<td colspan="1" rowspan="1"><a href="site:projects/lucene4c">Lucene4c</a></td> + <td colspan="1" rowspan="1">Lucene for C</td> + <td colspan="1" rowspan="1">Lucene PMC</td> + <td colspan="1" rowspan="1">Erik Hatcher</td> + <td colspan="1" rowspan="1">2005-02-21</td> + +</tr> + +<tr> <td colspan="1" rowspan="1"><a href="site:projects/muse">Muse</a></td> <td colspan="1" rowspan="1">A robust implementation of the OASIS WSDM, Management using Web Services (MuWS) specification</td> Index: site-author/site.xml =================================================================== --- site-author/site.xml (revision 154750) +++ site-author/site.xml (working copy) @@ -57,6 +57,7 @@ <log4cxx label="Log4cxx" href="log4cxx.html"/> <log4net label="Log4net" href="log4net.html"/> <log4php label="Log4php" href="log4php.html"/> + <lucene4c label="Lucene4c" href="lucene4c.html"/> <merlindeveloper href="merlin-developer.html"/> <muse label="Muse" href="muse.html"/> <myfaces label="MyFaces" href="myfaces.html"/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
