You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2007/01/11 18:18:53 UTC
svn commit: r495296 [2/3] - in /incubator/uima/site/trunk/uima-website:
docs/ xdocs/ xdocs/stylesheets/
Added: incubator/uima/site/trunk/uima-website/docs/management.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/management.html?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/management.html (added)
+++ incubator/uima/site/trunk/uima-website/docs/management.html Thu Jan 11 09:18:50 2007
@@ -0,0 +1,194 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Copyright 1999-2004 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+
+<!-- Content Stylesheet for Site -->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value="
+ UIMA Documentation Team">
+ <meta name="email" value="uima-dev.AT.incubator.DOT.apache.DOT.org">
+
+
+
+
+
+
+
+ <title>Apache UIMA - Apache UIMA Project Guidelines</title>
+ </head>
+
+ <body bgcolor="#ffffff" text="#000000" link="#525D76">
+ <table border="0" width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <td align="left">
+<a href="http://incubator.apache.org/"><img src="./images/apache-incubator-logo.png" alt="Apache UIMA" border="0"/></a>
+</td>
+ </td>
+ <td align='LEFT'>
+ <td width="80%" align="left" valign="bottom" bgcolor="#ffffff">
+ <font color="#625972" size="+3" face="arial,helvetica,sanserif">
+ <b>Apache UIMA Project Guidelines</b>
+</font>
+</td>
+ </td>
+ </tr>
+ </table>
+ <table border="0" width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td width="20%" valign="top" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://apachecon.com/2005/US/">
+ <img src="http://apache.org/images/ac2005us_blue_125x125.jpg" height="125"
+ width="125" border="0" alt="ApacheCon US 2005" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p><strong>General</strong></p>
+ <ul>
+ <li> <a href="./index.html">Home</a>
+</li>
+ <li> <a href="./news.html">News</a>
+</li>
+ <li> <a href="./license.html">License</a>
+</li>
+ <li> <a href="http://www.apache.org/">ASF</a>
+</li>
+ <li> <a href="./downloads.html">Downloads</a>
+</li>
+ <li> <a href="./javadoc.html">javadoc</a>
+</li>
+ </ul>
+ <p><strong>Community</strong></p>
+ <ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
+ <li> <a href="./get-involved.html">Get Involved</a>
+</li>
+ <li> <a href="./team-list.html">Committers</a>
+</li>
+ <li> <a href="./mail-lists.html">Mailing Lists</a>
+</li>
+ <li> <a href="./documentation.html">Documentation</a>
+</li>
+ <li> <a href="./faq.html">FAQ</a>
+</li>
+ <li> <a href="http://cwiki.apache.org/UIMA/">Wiki</a>
+</li>
+ </ul>
+ <p><strong>Development</strong></p>
+ <ul>
+ <li> <a href="./svn.html">Source Code</a>
+</li>
+ <li> <a href="./svn.html#building.with.maven">Building with Maven</a>
+</li>
+ <li> <a href="./sandbox.html">Sandbox</a>
+</li>
+ <li> <a href="./codeConventions.html">Code Conventions</a>
+</li>
+ <li> <a href="http://issues.apache.org/jira/browse/uima ">JIRA</a>
+</li>
+ <li> <a href="./uima-specification.html">UIMA Specification</a>
+</li>
+ </ul>
+ <p><strong>Conferences</strong></p>
+ <ul>
+ <li> <a href="./news.html#13 December 2006">ApacheCon 07 Europe</a>
+</li>
+ <li> <a href="./gldv07.html">GLDV 2007</a>
+</li>
+ </ul>
+ </td>
+ <td width="80%" align="left" valign="top">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#726982">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Project Management Committee Bylaws"><strong>Project Management Committee Bylaws</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>
+ The Project Management Committee (PMC) has not yet been formed.
+ It will be formed when and if the project graduates from the
+ Incubator. </p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div align="center"><font color="#525D76" size="-1"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></font></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Modified: incubator/uima/site/trunk/uima-website/docs/news.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/news.html?view=diff&rev=495296&r1=495295&r2=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/news.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/news.html Thu Jan 11 09:18:50 2007
@@ -97,6 +97,10 @@
</ul>
<p><strong>Community</strong></p>
<ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
<li> <a href="./get-involved.html">Get Involved</a>
</li>
<li> <a href="./team-list.html">Committers</a>
Added: incubator/uima/site/trunk/uima-website/docs/project-guidelines.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/project-guidelines.html?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/project-guidelines.html (added)
+++ incubator/uima/site/trunk/uima-website/docs/project-guidelines.html Thu Jan 11 09:18:50 2007
@@ -0,0 +1,240 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Copyright 1999-2004 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+
+<!-- Content Stylesheet for Site -->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value=" UIMA Documentation
+ Team">
+ <meta name="email" value="uima-dev.AT.incubator.DOT.apache.DOT.org">
+
+
+
+
+
+
+
+ <title>Apache UIMA - Apache UIMA Project Guidelines</title>
+ </head>
+
+ <body bgcolor="#ffffff" text="#000000" link="#525D76">
+ <table border="0" width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <td align="left">
+<a href="http://incubator.apache.org/"><img src="./images/apache-incubator-logo.png" alt="Apache UIMA" border="0"/></a>
+</td>
+ </td>
+ <td align='LEFT'>
+ <td width="80%" align="left" valign="bottom" bgcolor="#ffffff">
+ <font color="#625972" size="+3" face="arial,helvetica,sanserif">
+ <b>Apache UIMA Project Guidelines</b>
+</font>
+</td>
+ </td>
+ </tr>
+ </table>
+ <table border="0" width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td width="20%" valign="top" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://apachecon.com/2005/US/">
+ <img src="http://apache.org/images/ac2005us_blue_125x125.jpg" height="125"
+ width="125" border="0" alt="ApacheCon US 2005" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p><strong>General</strong></p>
+ <ul>
+ <li> <a href="./index.html">Home</a>
+</li>
+ <li> <a href="./news.html">News</a>
+</li>
+ <li> <a href="./license.html">License</a>
+</li>
+ <li> <a href="http://www.apache.org/">ASF</a>
+</li>
+ <li> <a href="./downloads.html">Downloads</a>
+</li>
+ <li> <a href="./javadoc.html">javadoc</a>
+</li>
+ </ul>
+ <p><strong>Community</strong></p>
+ <ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
+ <li> <a href="./get-involved.html">Get Involved</a>
+</li>
+ <li> <a href="./team-list.html">Committers</a>
+</li>
+ <li> <a href="./mail-lists.html">Mailing Lists</a>
+</li>
+ <li> <a href="./documentation.html">Documentation</a>
+</li>
+ <li> <a href="./faq.html">FAQ</a>
+</li>
+ <li> <a href="http://cwiki.apache.org/UIMA/">Wiki</a>
+</li>
+ </ul>
+ <p><strong>Development</strong></p>
+ <ul>
+ <li> <a href="./svn.html">Source Code</a>
+</li>
+ <li> <a href="./svn.html#building.with.maven">Building with Maven</a>
+</li>
+ <li> <a href="./sandbox.html">Sandbox</a>
+</li>
+ <li> <a href="./codeConventions.html">Code Conventions</a>
+</li>
+ <li> <a href="http://issues.apache.org/jira/browse/uima ">JIRA</a>
+</li>
+ <li> <a href="./uima-specification.html">UIMA Specification</a>
+</li>
+ </ul>
+ <p><strong>Conferences</strong></p>
+ <ul>
+ <li> <a href="./news.html#13 December 2006">ApacheCon 07 Europe</a>
+</li>
+ <li> <a href="./gldv07.html">GLDV 2007</a>
+</li>
+ </ul>
+ </td>
+ <td width="80%" align="left" valign="top">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#726982">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Apache UIMA Project Guidelines"><strong>Apache UIMA Project Guidelines</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p>
+ <br />
+ <p>This document defines the guidelines of the Apache UIMA Project. It includes
+ definitions of the various categories of membership, who is able to vote, how
+ conflicts are resolved by voting, and the procedures to follow for proposing and
+ making changes to the codebase of the Project.</p>
+ <ul>
+ <li>
+ <a href="./roles.html">Roles and Responsibilities</a>
+ <br /> Defines the recognized roles in the project.
+ </li>
+
+ <li>
+ <a href="./communication.html">Communication</a>
+ <br /> Defines how users and developers communicate.
+ </li>
+
+ <li>
+ <a href="./decisions.html">Decision Making</a>
+ <br /> Defines how action items are proposed and voted on.
+ </li>
+
+ <li>
+ <a href="svn.html">Source Repositories</a>
+ <br /> Defines how the Project's source code is organized and developed.
+ </li>
+
+ <!--
+ <li>
+ <a href="./management.html">Project Management</a>
+ <br/>
+ Defines the roles and responsibilities of the
+ Podling Project Management Committee (PPMC).
+ </li>
+ -->
+ <!--
+ <li>
+ <a href="./newproject.html">New Subproject Proposals</a>
+ <br/>
+ Defines the methodology for proposing new top level
+ UIMA Subprojects.
+ </li> -->
+ </ul>
+ <p> This is a living document. Changes can be made by the Podling Project Management
+ Committee. Suggestions for changes should be discussed on the
+ uima-dev.AT.incubator.DOT.apache.DOT.org
+ <a href="mail-lists.html">mailing list</a>
+ </p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div align="center"><font color="#525D76" size="-1"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></font></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Added: incubator/uima/site/trunk/uima-website/docs/roles.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/roles.html?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/roles.html (added)
+++ incubator/uima/site/trunk/uima-website/docs/roles.html Thu Jan 11 09:18:50 2007
@@ -0,0 +1,392 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+
+<!--
+Copyright 1999-2004 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+
+<!-- Content Stylesheet for Site -->
+
+
+<!-- start the processing -->
+ <!-- ====================================================================== -->
+ <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
+ <!-- Main Page Section -->
+ <!-- ====================================================================== -->
+ <html>
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+
+ <meta name="author" value=" UIMA Documentation
+ Team">
+ <meta name="email" value="uima-dev.AT.incubator.DOT.apache.DOT.org">
+
+
+
+
+
+
+
+ <title>Apache UIMA - Apache UIMA Project Guidelines</title>
+ </head>
+
+ <body bgcolor="#ffffff" text="#000000" link="#525D76">
+ <table border="0" width="100%" cellspacing="0">
+ <!-- TOP IMAGE -->
+ <tr>
+ <td align='LEFT'>
+ <td align="left">
+<a href="http://incubator.apache.org/"><img src="./images/apache-incubator-logo.png" alt="Apache UIMA" border="0"/></a>
+</td>
+ </td>
+ <td align='LEFT'>
+ <td width="80%" align="left" valign="bottom" bgcolor="#ffffff">
+ <font color="#625972" size="+3" face="arial,helvetica,sanserif">
+ <b>Apache UIMA Project Guidelines</b>
+</font>
+</td>
+ </td>
+ </tr>
+ </table>
+ <table border="0" width="100%" cellspacing="4">
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+
+ <tr>
+ <!-- LEFT SIDE NAVIGATION -->
+ <td width="20%" valign="top" nowrap="true">
+
+ <!-- special ACon Logo - leave here for next time
+ <a href="http://apachecon.com/2005/US/">
+ <img src="http://apache.org/images/ac2005us_blue_125x125.jpg" height="125"
+ width="125" border="0" alt="ApacheCon US 2005" />
+ </a> -->
+
+ <!-- regular menu -->
+
+
+ <!-- ============================================================ -->
+
+ <p><strong>General</strong></p>
+ <ul>
+ <li> <a href="./index.html">Home</a>
+</li>
+ <li> <a href="./news.html">News</a>
+</li>
+ <li> <a href="./license.html">License</a>
+</li>
+ <li> <a href="http://www.apache.org/">ASF</a>
+</li>
+ <li> <a href="./downloads.html">Downloads</a>
+</li>
+ <li> <a href="./javadoc.html">javadoc</a>
+</li>
+ </ul>
+ <p><strong>Community</strong></p>
+ <ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
+ <li> <a href="./get-involved.html">Get Involved</a>
+</li>
+ <li> <a href="./team-list.html">Committers</a>
+</li>
+ <li> <a href="./mail-lists.html">Mailing Lists</a>
+</li>
+ <li> <a href="./documentation.html">Documentation</a>
+</li>
+ <li> <a href="./faq.html">FAQ</a>
+</li>
+ <li> <a href="http://cwiki.apache.org/UIMA/">Wiki</a>
+</li>
+ </ul>
+ <p><strong>Development</strong></p>
+ <ul>
+ <li> <a href="./svn.html">Source Code</a>
+</li>
+ <li> <a href="./svn.html#building.with.maven">Building with Maven</a>
+</li>
+ <li> <a href="./sandbox.html">Sandbox</a>
+</li>
+ <li> <a href="./codeConventions.html">Code Conventions</a>
+</li>
+ <li> <a href="http://issues.apache.org/jira/browse/uima ">JIRA</a>
+</li>
+ <li> <a href="./uima-specification.html">UIMA Specification</a>
+</li>
+ </ul>
+ <p><strong>Conferences</strong></p>
+ <ul>
+ <li> <a href="./news.html#13 December 2006">ApacheCon 07 Europe</a>
+</li>
+ <li> <a href="./gldv07.html">GLDV 2007</a>
+</li>
+ </ul>
+ </td>
+ <td width="80%" align="left" valign="top">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#726982">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Apache UIMA Roles and Responsibilities"><strong>Apache UIMA Roles and Responsibilities</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft
+ document.</b></font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p>
+ <br />
+ <p> The roles and responsibilities that people can assume in the project are based on
+ merit. Everybody can help no matter what their role. Those who have been long term or
+ valuable contributors to the project obtain the right to vote and commit directly to
+ the source repository.
+ </p>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#9289A2">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Users"><strong>Users</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p> Users are the people who use the products of the Project. People in this role aren't
+ contributing code, but they are using the products, reporting bugs, making
+ feature requests, helping other users, extending the online documentation on the
+ Wiki, and such. This is by far the most important category of people as, without
+ users, there is no reason for the Project.
+ </p>
+ <p> When a user starts to contribute code or documentation patches, they become a
+ Contributor.
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#9289A2">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Contributors"><strong>Contributors</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p> Contributors are the people who write code or documentation patches or
+ contribute positively to the project in other ways. A volunteer's contribution is
+ always recognized. In source code, we have adopted a policy of keeping the author's
+ names out of the individual source code files; attributions are now put into the
+ project's NOTICES file. All volunteers who contribute to a source file may add a
+ section with their name and contributions to the NOTICES file.
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#9289A2">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Committers"><strong>Committers</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p> Contributors who give frequent and valuable contributions to the Project or a
+ subproject of the Project can have their status promoted to that of a "
+ <em>Committer</em>" for the Project or for that subproject. A Committer has
+ write access to the source code repository and gains voting rights allowing them to
+ affect the future of the project/subproject.
+ </p>
+ <p> In order for a Contributor to become a Committer, another Committer can nominate
+ that Contributor or the Contributor can ask for it.
+ </p>
+ <p> Once a Contributor is nominated, all of the Committers for a subproject will vote.
+ If there are at least 3 positive votes and no negative votes, the Contributor is
+ converted into a Committer and given write access to the source code repository for
+ that subproject. This is an example offer letter that should be sent to the
+ volunteer after 3 positive votes have been received:
+ </p>
+ <div align="left">
+ <table cellspacing="4" cellpadding="0" border="0">
+ <tr>
+ <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ </tr>
+ <tr>
+ <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ <td bgcolor="#ffffff"><pre>
+
+ Dear Contributor,
+
+ The Apache UIMA project would like to offer you commit privileges.
+ We have been impressed with your contributions up till now, and
+ believe that your involvement will improve the quality of the
+ libraries we produce.
+
+ It is important that you realize that these commit privileges give
+ you access to the specific Apache UIMA project repository for which you
+ are involved with. They do not provide commit access to any other
+ Apache based project. Those projects will have to grant you commit
+ privileges themselves.
+
+ If you are interested in having commit privileges, please just let us
+ know, and we will setup an account on apache.org. It would expedite
+ the process if you could provide your preferred account name.
+ This process could take a few days once
+ we get this information.
+
+ We all hope that you accept this invitation.
+
+ The Apache UIMA Project Management Committee.
+ </pre></td>
+ <td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ </tr>
+ <tr>
+ <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ <td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ <td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"/></td>
+ </tr>
+ </table>
+ </div>
+ <p> Once there are 3 positive votes and the response to the above letter has been
+ received, someone from the project community who already has commit access should
+ send email to:
+ <strong>root at apache.org</strong> that the account should be created. The
+ following information must be included in the email:
+ </p>
+ <ul>
+ <li> The name and email address of the new user. (ie: John Smith
+ <john.smith@foo.com>)
+ </li>
+ <li> Suggested account userid. This is optional. (ie: jmsith)
+ </li>
+ <li> The project that the user should be given access to. (ie: UIMA)
+ </li>
+ <li> The results of the votes. In other words, the names and email addresses of the
+ committers who approved the addition.
+ </li>
+ </ul>
+ <p> The new committer should also send an email to
+ <strong>asf at jaguNET.com</strong> with the following information (please cut
+ and paste to return format):
+ </p>
+ <blockquote> Name: {your name}
+ <br /> Email: {your email address on the ASF lists}
+ <br /> Projects: {comma separated list of ASF projects to which you have commit
+ access}
+ <br /> Key: {a blank line followed by your public key}
+ </blockquote>
+ <p>For example:</p>
+ <blockquote> Name: Joe Foobar
+ <br /> Email: joe@byteme.com
+ <br /> Projects: Tomcat, httpd
+ <br /> Key:
+ <br /> adklajdAL()@ N*@U)U@()@@ @)U@
+ </blockquote>
+ <p> Finally, a new committer should also submit a signed copy of the Contributor
+ License Agreement to the ASF. See the
+ <a href="http://www.apache.org/licenses/#clas">
+ <strong>Licenses page</strong></a> for details.
+ </p>
+ <p> Note 1: If a committer already has an account on the apache.org server and the
+ committer needs commit access to additional projects, then all that needs to be
+ done is to have the user notify general@incubator.apache.org with the results of
+ the voting (as documented above) and the user will be given access. In other words,
+ the root email address should only be used on the basis of new account creation.
+ </p>
+ <p> Note 2: All committers will be given write access to uima/site SVN on request. In
+ other words, committers should be able to update the main website.
+ </p>
+ <p> At times, Committers may go inactive for a variety of reasons. A Committer that has
+ been inactive for 6 months or more may lose their status as a Committer. Getting
+ access back is as simple as re-requesting it on the project's Developer mailing
+ list.
+ </p>
+ <p> A list of our current Committers can be found in our
+ <a href="team-list.html">Project Credits</a>.
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#9289A2">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Management Committee (PPMC)"><strong>Management Committee (PPMC)</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p> (Note: this section is written for when UIMA graduates from the incubator. Until
+ then, the committers are members of the podling PMC.) Committers who frequently
+ participate with valuable contributions may have their status promoted to that of
+ a "
+ <em>Project Management Committee Member</em>". This committee is the
+ official managing body of the UIMA Project and is responsible for setting overall
+ project direction.
+ </p>
+ <p> To view the Project Management Committee bylaws,
+ <a href="management.html"> click here</a>.
+ </p>
+ <p> A list of our current PMC Members can be found in our
+ <a href="team-list.html">Project Credits</a>.
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+
+ </td>
+ </tr>
+
+ <!-- FOOTER -->
+ <tr><td colspan="2">
+ <hr noshade="" size="1"/>
+ </td></tr>
+ <tr><td colspan="2">
+ <div align="center"><font color="#525D76" size="-1"><em>
+ Copyright © 2003-2006, The Apache Software Foundation
+ </em></font></div>
+ </td></tr>
+ </table>
+ </body>
+ </html>
+<!-- end the processing -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Modified: incubator/uima/site/trunk/uima-website/docs/sandbox.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/sandbox.html?view=diff&rev=495296&r1=495295&r2=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/sandbox.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/sandbox.html Thu Jan 11 09:18:50 2007
@@ -96,6 +96,10 @@
</ul>
<p><strong>Community</strong></p>
<ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
<li> <a href="./get-involved.html">Get Involved</a>
</li>
<li> <a href="./team-list.html">Committers</a>
Modified: incubator/uima/site/trunk/uima-website/docs/svn.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/svn.html?view=diff&rev=495296&r1=495295&r2=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/svn.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/svn.html Thu Jan 11 09:18:50 2007
@@ -96,6 +96,10 @@
</ul>
<p><strong>Community</strong></p>
<ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
<li> <a href="./get-involved.html">Get Involved</a>
</li>
<li> <a href="./team-list.html">Committers</a>
Modified: incubator/uima/site/trunk/uima-website/docs/team-list.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/team-list.html?view=diff&rev=495296&r1=495295&r2=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/team-list.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/team-list.html Thu Jan 11 09:18:50 2007
@@ -96,6 +96,10 @@
</ul>
<p><strong>Community</strong></p>
<ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
<li> <a href="./get-involved.html">Get Involved</a>
</li>
<li> <a href="./team-list.html">Committers</a>
Modified: incubator/uima/site/trunk/uima-website/docs/uima-specification.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/uima-specification.html?view=diff&rev=495296&r1=495295&r2=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/uima-specification.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/uima-specification.html Thu Jan 11 09:18:50 2007
@@ -95,6 +95,10 @@
</ul>
<p><strong>Community</strong></p>
<ul>
+ <li> <a href="./project-guidelines.html">Project Guidelines</a>
+</li>
+ <li> <a href="./contribution-policy.html">Contribution Policies</a>
+</li>
<li> <a href="./get-involved.html">Get Involved</a>
</li>
<li> <a href="./team-list.html">Committers</a>
Added: incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.txt
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.txt?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.txt (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.txt Thu Jan 11 09:18:50 2007
@@ -0,0 +1,152 @@
+Note: This empty document form itself is
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+
+
+
+
+
+ The Apache Software Foundation
+ Apache UIMA Project
+ Bulk Contribution Checklist
+ v1.0 20070111
+
+The Apache UIMA project is dedicated to producing a codebase that
+has clear IP pedigree and protects the IP rights of others. As part
+of this effort, we ask the following questions of all contributions
+of software that has been created outside of the project. Our goal is
+to provide clear and consistent oversight of the project codebase, as
+well as encourage our contributors to carefully examine their
+contributions before bringing to the project.
+
+Please Note : This document and your answers are considered public
+information, and shall be part of the Apache UIMA project public
+records.
+
+
+Part I : Identification
+
+ Please provide the following information
+
+ Name : ___________________________________________
+ E-mail : ___________________________________________
+
+ Mailing address :
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+
+ Employer : ___________________________________________
+
+
+Part II : Description
+
+ Please describe the contribution :
+
+
+
+
+
+Part III : Statement of Origination
+
+a) Have you personally written all of the code or other material
+ that you are intending to contribute to this project, and if so,
+ are you an Authorized Committer on the Apache UIMA project?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", you're done with Part III, skip to Part IV
+ If "no" please continue with the rest of Part III
+
+b) Have you verified the development history of the code to
+ identify ALL of the authors?
+
+ Please list the other authors:
+
+
+c) Do you have a written agreement with all of the authors that
+ either gives you ownership of the material or otherwise provides
+ you sufficient rights to submit this material to the project
+ on their behalf.
+
+ Please provide the details of this agreement:
+
+
+d) Are all of the authors Authorized Apache UIMA Committers for the part of
+ the contribution written/created by each author?
+
+ [ ] Yes ? if "yes", you're done with Part III, skip to Part IV.
+ [ ] No ? if "no", please continue with the rest of part III
+
+
+e) Did any of the authors of the code have access to third
+ party implementations of similar technology while developing the
+ contribution?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", please give details below :
+
+
+f) Was the code developed in accordance with a development
+ process which was designed to prevent unauthorized inclusion
+ of third party intellectual property rights into the code?
+ (e.g., does the process require that developers not have
+ concurrent access to third party implementations of similar
+ technology during development?)
+
+ [ ] Yes
+ [ ] No
+
+ If "no", the code isn't eligible for the Apache UIMA Project.
+
+ If "yes", please provide short description of the process,
+ focusing on protections related to third party intellectual
+ property :
+
+
+
+
+Note : The Apache UIMA project generally performs additional
+scans of it's codebase, including bulk contributions, to help
+confirm code pedigree. Prior to submitting any contribution,
+we strongly encourage you to verify that the contribution is
+acceptable. Please see
+http://incubator.apache.org/uima/code-scan-tools.html
+for more information.
+
+
+Part IV : Checklist
+
+ [ ] Contribution is licensed under the Apache License v2.0
+
+ [ ] Software Grant or Corporate Contributor License Agreement and Software
+ Grant executed and submitted
+
+
+ Signature : ___________________________________________
+Print Name : ___________________________________________
+ Date : ___________________________________________
+
+
+
+v1.0 20070111
+
+
Added: incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/bulk-contribution-checklist.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,190 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+ <properties>
+ <title>Apache UIMA Bulk Contribution Checklist</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+ </properties>
+
+ <body>
+
+ <section name="Apache UIMA Bulk Contribution Checklist">
+
+
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p><br />
+
+
+ <p>
+A text version of this document can be found <a href="bulk-contribution-checklist.txt">here</a>.
+</p>
+<pre>
+ The Apache Software Foundation
+ Apache UIMA Project
+ Bulk Contribution Checklist
+ v1.0 20070111
+
+The Apache UIMA project is dedicated to producing a codebase that
+has clear IP pedigree and protects the IP rights of others. As part
+of this effort, we ask the following questions of all contributions
+of software that has been created outside of the project. Our goal is
+to provide clear and consistent oversight of the project codebase, as
+well as encourage our contributors to carefully examine their
+contributions before bringing to the project.
+
+Please Note : This document and your answers are considered public
+information, and shall be part of the Apache UIMA project public
+records.
+
+
+Part I : Identification
+
+ Please provide the following information
+
+ Name : ___________________________________________
+ E-mail : ___________________________________________
+
+ Mailing address :
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+ ___________________________________________
+
+ Employer : ___________________________________________
+
+
+Part II : Description
+
+ Please describe the contribution :
+
+
+
+
+
+Part III : Statement of Origination
+
+a) Have you personally written all of the code or other material
+ that you are intending to contribute to this project, and if so,
+ are you an Authorized Committer on the Apache UIMA project?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", you're done with Part III, skip to Part IV
+ If "no" please continue with the rest of Part III
+
+b) Have you verified the development history of the code to
+ identify ALL of the authors?
+
+ Please list the other authors:
+
+
+c) Do you have a written agreement with all of the authors that
+ either gives you ownership of the material or otherwise provides
+ you sufficient rights to submit this material to the project
+ on their behalf.
+
+ Please provide the details of this agreement:
+
+
+d) Are all of the authors Authorized Apache UIMA Committers for the part of
+ the contribution written/created by each author?
+
+ [ ] Yes ? if "yes", you're done with Part III, skip to Part IV.
+ [ ] No ? if "no", please continue with the rest of part III
+
+
+ <!--
+e) Was the code written prior to May 2005 (when the Harmony Project
+ was initiated)?
+
+ [ ] Yes
+ [ ] No
+
+ (i) If No, you must provide Authorized Contributor Questionnaires
+ for the authors of the code created after May 2005 such that
+ those authors are classified as Authorized Contributors for
+ the portions of the contribution written by them
+ after May 2005.
+
+ -->
+e) Did any of the authors of the code have access to third
+ party implementations of similar technology while developing the
+ contribution?
+
+ [ ] Yes
+ [ ] No
+
+ If "yes", please give details below :
+
+
+f) Was the code developed in accordance with a development
+ process which was designed to prevent unauthorized inclusion
+ of third party intellectual property rights into the code?
+ (e.g., does the process require that developers not have
+ concurrent access to third party implementations of similar
+ technology during development?)
+
+ [ ] Yes
+ [ ] No
+
+ If "no", the code isn't eligible for the Apache UIMA Project.
+
+ If "yes", please provide short description of the process,
+ focusing on protections related to third party intellectual
+ property :
+
+
+
+
+Note : The Apache UIMA project generally performs additional
+scans of it's codebase, including bulk contributions, to help
+confirm code pedigree. Prior to submitting any contribution,
+we strongly encourage you to verify that the contribution is
+acceptable. Please see
+ <a href="code-scan-tools.html">http://incubator.apache.org/uima/code-scan-tools.html</a>
+for more information.
+
+
+Part IV : Checklist
+
+ [ ] Contribution is licensed under the Apache License v2.0
+
+ [ ] Software Grant or Corporate Contributor License Agreement and Software
+ Grant executed and submitted
+
+
+ Signature : ___________________________________________
+Print Name : ___________________________________________
+ Date : ___________________________________________
+
+
+
+v1.0 20070111
+
+
+</pre>
+ </section>
+
+ </body>
+ </document>
Added: incubator/uima/site/trunk/uima-website/xdocs/code-scan-tools.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/code-scan-tools.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/code-scan-tools.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/code-scan-tools.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+ <properties>
+ <title>Apache UIMA code scanning tools</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+ </properties>
+
+ <body>
+
+ <section name="Apache UIMA code scanning tools">
+
+ <p>When donating "bulk" code to the project, it is sometimes useful to use
+ tools to scan the donation to reduce the risk of accidentally having included
+ in the donation things which could cause licensing issues later. This
+ page collects information on various code-scanning tools that can be useful.</p>
+
+<h3>Incubator code-scanning tool</h3>
+
+<p>This tool is used prior to all release activities in the incubator. Obtain it by
+going to http://code.google.com/p/arat</p>
+
+</section>
+</body>
+</document>
\ No newline at end of file
Added: incubator/uima/site/trunk/uima-website/xdocs/communication.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/communication.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/communication.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/communication.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+ <properties>
+ <title>Apache UIMA Project Guidelines</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+ </properties>
+
+ <body>
+
+ <section name="Communication">
+
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft
+ document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p><br />
+ <p> The Project obtains its strength from the communication of its members. In order for
+ members to easily communicate with each other, the Project has a variety of mailing
+ lists. These lists, with the exception of the announcement lists, are not moderated
+ and anybody is more than welcome to join them. However, you must be subscribed to post
+ to a list.
+ </p>
+
+ <p> To reduce the bandwidth demands on everyone, mail should not contain attachments.
+ It is recommended that you place interesting material either within the body of the
+ message or provide a URL for retrieval. Patches are best done as attachments to a JIRA
+ issue.
+ </p>
+
+ <p> To join the mailing lists, see our
+ <a href="mail-lists.html"> Mailing List</a> page.
+ </p>
+
+ <p> The Project's list fall into the following categories:
+ </p>
+ </section>
+ <!--
+ <section name="Announcement Lists">
+ <p>
+ Announcement lists are very low traffic designed to communicate
+ important information, such as final releases of a subproject's
+ code, to a wide audience.
+ </p>
+ </section>
+ -->
+ <section name="User Lists">
+ <p> User lists are for users of a product to converse about such things as configuration
+ and operating of the products of the Project.
+ </p>
+ </section>
+
+ <section name="Developer Lists">
+ <p> Developer lists are for the developers of the project. On these lists suggestions
+ and comments for code changes are discussed and action items are raised and voted on.
+ For the developer community, these lists are the very center of the project where all
+ the
+ "action" is.
+ </p>
+ </section>
+
+ <section name="Commit Lists">
+ <p> The commit lists are where all cvs code commit messages are sent. All committers are
+ required to subscribe to this list so that they can stay aware of changes to the
+ repository.
+ </p>
+ </section>
+
+ </body>
+</document>
\ No newline at end of file
Added: incubator/uima/site/trunk/uima-website/xdocs/contribution-policy.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/contribution-policy.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/contribution-policy.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/contribution-policy.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,184 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+<properties>
+<title>Apache UIMA Contribution Policy</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+</properties>
+
+<body>
+
+<section name="Apache UIMA Contribution Policy">
+
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p><br />
+<p>
+The Apache UIMA Contribution Policy is summarized below:
+</p>
+
+<ul>
+<li>
+ We are working to ensure that we have broad participation from the community,
+ at all experience levels and interests, but at the same time we are working to
+ minimize any risks to the ASF, the project and our community due to
+ inappropriate contributions of the intellectual property of others.
+</li>
+<li>
+ We adhere to the standard Apache process and contribution agreements.
+</li>
+<li>
+ We require every contributor to fill out the standard Apache
+ <a href="http://www.apache.org/licenses/#clas">Individual
+ Contributors License Agreement</a>.
+</li>
+</ul>
+
+<subsection name="Strict Limits on Committer Contributions">
+
+<p>
+Committers can commit contributions to the repositories
+that they personally created <i>specifically for contribution to Apache UIMA.</i>
+This is the standard stream of fresh original work, small enhancements
+and patches that are the normal flow of project life.
+</p>
+
+ <p>Committers can commit contributions to the repositories that
+ were created by another contributor that do not have commit access,
+ and were created <i>specifically for contribution to Apache UIMA</i>,
+ provided: </p>
+ <ul>
+ <li>the contributor has a signed Contributors License Agreement
+ listed with Apache
+
+</li>
+ <li>the contribution is made as an attachement to a UIMA Jira issue</li>
+ <li>the attachment is marked as "ASF Granted License", indicating that
+ the contributer has granted a license for the attachment sufficient to enable
+ the UIMA Project to incorporate the attachement and distribute the result
+ under the Apache 2.0 license</li>
+
+ </ul>
+
+ <!--
+ <p>Committers can commit bulk code if they
+ adhere to these rules:
+ </p>
+
+ <ul>
+ <li>All contributed code must be the original work of the contributor, or
+ if the contributed code contains third party code not the original work of the
+ contributor, it must be first discussed on the uima-dev discussion list and
+ the IP Clearance process described in
+ <a href="http://incubator.apache.org/ip-clearance/index.html">
+ Intellectual property clearance</a>
+ must be done and documented. A special subdirectory of the UIMA project is
+ kept for storing the results of these clearances.</li>
+
+ <li>The contributor must have an Apache Individual Contributor License Agreement
+ recorded and acknowledged by the ASF.</li>
+ </ul>
+ -->
+
+<p>
+The purpose of
+this rule is to explicitly prohibit re-purposed "bulk" code
+<!-- that the contributor believes is their original work--> from being
+added to the codebase without explicit oversight and acceptance.
+We can still accept contributions like that, but will track them explicitly
+as Bulk Contributions.
+</p>
+
+
+</subsection>
+
+
+<subsection name="Policy for Committers">
+
+<p>
+Each committer is required to complete a standard
+<a href="http://www.apache.org/licenses/#clas">Apache Individual Contributor License Agreement</a>.
+This document asserts that the contributor is licensing their
+material to the ASF under the Apache license and is their original work (there's some other details).
+This document is maintained and managed by the Secretary of the Apache Software Foundation.
+</p>
+
+<p>
+We encourage every committer, if appropriate, to have their employer execute a
+<a href="http://www.apache.org/licenses/">Apache Corporate Contributor License Agreement</a>.
+Note that this is recommended, but not required.
+</p>
+
+</subsection>
+
+<subsection name="Policy for Bulk Contributions">
+
+<p>
+Any software or other contribution that was not created explicitly for
+Apache UIMA <i>in</i> the Apache UIMA project is considered to
+be a 'Bulk Contribution'. This status is independent of the purpose
+or author of said contribution. For example:
+</p>
+
+<ul>
+<li> Personal utilities that a committer always uses on projects</li>
+<li> Code from other open source projects that have a compatible license</li>
+<li> Code from proprietary projects for which the donor has clear title</li>
+<li> Larger pieces of Code being committed on behalf of other contributors, typically using a Software Grant</li>
+</ul>
+
+<p>
+Any Bulk Contribution:
+</p>
+
+<ol>
+<li> Will be donated via the project bug tracking system (JIRA) as a contribution under the Apache License.</li>
+<li> Will be accompanied by a Software Grant (for large contributions) or ICLA (small contributions)
+ which will be registered with the Apache Incubator</li>
+<li> done using a Software Grant will be registered in the Apache UIMA Bulk Contribution Repository
+ via a <a href="bulk-contribution-checklist.html">Bulk Contribution Checklist</a></li>
+</ol>
+
+<p>
+The Bulk Contribution Repository is a separate place in our administrative SVN in which records
+ the Bulk Contribution Checklist and other checklist information, for each contribution.
+We do this to
+ensure that we have a clear and unambiguous record of any repurposed software that was contributed or
+brought into the project source tree.
+</p>
+
+<p>
+We strongly urge any potential contributor to carefully examine their candidate for contribution (for instance,
+ run code scans to insure the contributed code doesn't accidentally contain things that could
+ cause licensing difficulties)
+before offering to the project. To that end, we have started collecting information on tools and
+other aids to help in this process, and it can be found on this page about
+ <a href="code-scan-tools.html">code scan tools</a>.
+</p>
+
+
+</subsection>
+
+
+</section>
+</body>
+</document>
\ No newline at end of file
Added: incubator/uima/site/trunk/uima-website/xdocs/decisions.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/decisions.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/decisions.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/decisions.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,237 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+ <properties>
+ <title>Apache UIMA Project Guidelines</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+ </properties>
+
+ <body>
+ <section name="Decision Making">
+
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft
+ document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p><br />
+
+ <p> All
+ <a href="roles.html">Contributors</a> are encouraged to participate in
+ decisions, but the decision itself is made by those that have
+ <a href="roles.html">Committer</a> status in the Project. In other words, the
+ Project is a
+ "
+ <em>Minimum Threshold Meritocracy</em>".
+ </p>
+
+ <h2>Voting</h2>
+
+ <p> The act of voting carries certain obligations. Voting members are not only stating
+ their opinion, they are also agreeing to help do the work.
+ </p>
+
+ <p> Any subscriber to the list may vote on any issue or action item. However, the only
+ binding votes are those cast by a Committer. <!--If the vote is about a change to the source code or
+ documentation and the primary author is a Contributor and not a
+ Committer, the primary author of what is being changed may also
+ cast a binding vote on that issue. -->
+ </p>
+
+ <p> Any Contributor or Committer ("member") may call for an action-item vote on the
+ uima-dev mailing list. It is preferred that a vote be preceded by a formal proposal
+ offered for discussion purposes. The message announcing a vote should contain a
+ Subject beginning with "[VOTE]", and a distinctive one-line summary corresponding
+ to the action item for the vote.
+ </p>
+
+ <p>Each vote can be made in one of three flavors:</p>
+
+ <table>
+ <tr>
+ <td>
+ <strong>+1</strong>
+ </td>
+ <td>
+ "Yes," "Agree," or "the action should be
+ performed." On some issues this is only binding if the voter has tested the
+ action on their own system(s).
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <strong>+/-0</strong>
+ </td>
+ <td>
+ "Abstain," "no opinion". An abstention may have
+ detrimental effects if too many people abstain. -0 can indicate lack of support,
+ but without any alternative being proposed.
+ </td>
+ </tr>
+
+ <tr>
+ <td>
+ <strong>-1</strong>
+ </td>
+ <td>
+ "No" On issues where consensus is required, this vote counts as a
+ <strong>veto</strong>. All vetos must contain an explanation of why the veto is
+ appropriate, and possibly, an alternative. Vetos with no explanation are void.
+ No veto can be overruled. If you disagree with the veto, you should lobby the
+ person who cast the veto. Voters intending to veto an action item should make
+ their opinions known to the group immediately so that the problem can be remedied
+ as early as possible.
+ </td>
+ </tr>
+
+ </table>
+
+ <p>An action item may need one of two types of approval.</p>
+ <blockquote>
+
+ <p> An action requiring consensus approval must receive at least
+ <strong>3 binding +1</strong> votes and
+ <strong>no binding vetos</strong>.
+ </p>
+ <p> An action requiring majority approval must receive at least
+ <strong>3 binding +1</strong> votes and more
+ <strong>+1</strong> votes than
+ <strong>-1</strong> votes.
+ </p>
+
+ </blockquote>
+ <p> Except for a public release, All other action items are considered to have lazy
+ approval until somebody votes
+ <strong>-1</strong>, at which point the action item is converted to a formal
+ consensus or majority vote, depending on the type of action item.</p>
+
+ <blockquote><p>Note: "Lazy" means the action item has immediate tactic approval, and
+ it is not necessary to tally the vote until a -1 reply is posted. Once a -1 reply is
+ posted, the vote must be tallied and reported before the action item is considered
+ approved. All action-item votes are lazy except for a public release vote.
+ </p></blockquote>
+
+ <h3>Voting Caveats</h3>
+
+ <ul>
+ <!--
+ <li>A +1 vote regarding product code is only can only be made binding
+ if the voter has tested the action on their own system(s) equipment.</li>
+
+ <li>A binding +1 vote on a public release means the (sub)project's Committer
+ agrees to provide ongoing support for that release while it is current.</li>
+ Members who wish to discuss a vote before replying, may open another thread to help avoid premature vetos. Any +/-1's or +/-0's posted to an alternate thread, or any other thread not labeled "[VOTE]", are considered conversational, and do not qualify as an valid action-item vote. A "lazy item" remains subject to lazy approval until a valid -1 reply is posted to the "[VOTE]" thread.
+ -->
+ <li>An abstention may have detrimental effects if too many people abstain.</li>
+ <li>Vetos with no explanation are void. No veto can be overruled. If you disagree with
+ the veto, you should lobby the person who cast the veto. Voters intending to veto an
+ action item should make their opinions known to the group immediately so that the
+ problem can be remedied as early as possible.</li>
+ <!--
+ <li>If a Committer believes the explanation for a veto is invalid,
+ an affirmation of the veto can be requested. If some other
+ Committer does not affirm that the explanation for the veto is
+ valid, the veto shall be void.</li>
+ <li>If a dispute over a veto becomes intractable, the PMC may consent to arbitrate
+ the matter, and, if appropriate, rescind the veto with a 3/4
+ majority vote of the PMC members.</li>
+ -->
+ <li>Members who wish to discuss a vote before replying, may open another thread to
+ help avoid premature vetos. Any +/-1's or +/-0's posted to an alternate thread, or
+ any other thread not labeled "[VOTE]", are considered conversational, and do not
+ qualify as an valid action-item vote. A "lazy item" remains subject to lazy
+ approval until a valid -1 reply is posted to the "[VOTE]" thread.</li>
+ </ul>
+
+ <h2>Action Items</h2>
+
+ <p> All decisions revolve around "
+ <em>Action Items.</em>" Action Items consist of the following:
+ </p>
+
+ <ul>
+ <li><a href="#long_term_plans">Long Term Plans</a></li>
+ <li><a href="#short_term_plans">Short Term Plans</a></li>
+ <li><a href="#release_plan">Release Plan</a></li>
+ <li><a href="#release_testing">Release Testing</a></li>
+ <li><a href="#public_testing">Public Release</a></li>
+ <li><a href="#showstoppers">Showstoppers</a></li>
+ <li><a href="#product_changes">Product Changes</a></li>
+ </ul>
+
+ <h3><a id="long_term_plans">Long Term Plans</a></h3>
+
+ <p> Long term plans are simply announcements that group members are working on
+ particular issues related to the Project. These are not voted on, but Committers who
+ do not agree with a particular plan, or think that an alternative plan would be better,
+ are obligated to inform the group of their feelings.
+ </p>
+
+ <h3><a id="short_term_plans">Short Term Plans</a></h3>
+
+ <p> Short term plans are announcements that a volunteer is working on a particular set of
+ documentation or code files with the implication that other volunteers should avoid
+ them or try to coordinate their changes.
+ </p>
+
+ <h3><a id="release_plan">Release Plan</a></h3>
+
+ <p> A release plan is used to keep all volunteers aware of when a release is desired, who
+ will be the release manager, when the repository will be frozen to create a release,
+ and other assorted information to keep volunteers from tripping over each other.
+ Lazy majority decides each issue in a release plan.
+ </p>
+
+ <h3><a id="release_testing">Release Testing</a></h3>
+
+ <p> After a new release is built, it must be tested before being released to the public.
+ The Release Manager will announce that a release is ready for testing.
+ </p>
+
+ <h3><a id="public_release">Public Release</a></h3>
+
+ <p>Once the Release Manager determines that testing is complete, and all showstoppers
+ for the release have been resolved, the Release Manager shall call for a vote on the
+ public release. Majority approval is required before the public release can be made.
+ The Committers who approve a public release (vote +1) are expected to provide ongoing
+ support for that release while it is current. The Release Manager must summarize the
+ outcome of the vote before the public release becomes final.
+ </p>
+
+ <h3><a id="showstoppers">Showstoppers</a></h3>
+
+ <p> Showstoppers are issues that require a fix be in place before the next public
+ release. They are listed in the status file in order to focus special attention on
+ these problems. An issue becomes a showstopper when it is listed as such in the status
+ file and remains so by lazy consensus.
+ </p>
+
+ <h3>Product Changes</h3>
+
+ <p> Changes to the products of the Project, including code and documentation, will
+ appear as action items in the status file. All product changes to the currently active
+ repository are subject to lazy consensus.
+ </p>
+
+ </section>
+
+ </body>
+</document>
\ No newline at end of file
Added: incubator/uima/site/trunk/uima-website/xdocs/management.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/management.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/management.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/management.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+<properties>
+<title>Apache UIMA Project Guidelines</title>
+<author email="uima-dev.AT.incubator.DOT.apache.DOT.org">
+ UIMA Documentation Team</author>
+</properties>
+
+<body>
+
+ <section name="Project Management Committee Bylaws">
+ <p>
+ The Project Management Committee (PMC) has not yet been formed.
+ It will be formed when and if the project graduates from the
+ Incubator. </p>
+ <!-- was formed by the Apache Board
+ on 17 July 2002. The bylaws were last amended on 6 October 2004.
+ There is no preset number of seats on the PMC. The PMC will strive to
+ add every committer within DB that, in the opinion of the PMC as
+ determined by a vote, displays the capability and desire to help guide
+ the DB project. The PMC will nominate a chairperson from amongst their
+ ranks for presentation to the Board. The list of current members can be found in our
+ <a href="./whoweare.html"> Project Credits</a>.
+ </p>
+
+ <subsection name="Roles">
+ <p>
+ The PMC is responsible for the strategic direction
+ and success of the DB Project. This governing body is expected to
+ ensure the project's welfare and guide its overall direction. The PMC
+ may not necessarily participate in the day-to-day coding but is
+ involved in the overall development plans, the alleviation of any
+ bottlenecks, the resolution of conflicts, and the overall technical
+ success of the project.
+ </p>
+
+ <p>
+ The PMC is answerable to the Apache Board with its Chairman serving as
+ primary liaison.
+ </p>
+ </subsection>
+
+ <subsection name="Meetings">
+ <p>The PMC discusses issues and determines strategic direction via mail
+ list. All binding votes happen on the PMC list.
+ </p>
+ </subsection>
+
+ <subsection name="Membership">
+ <p>
+ PMC members may resign at any time. A committer will remain on the DB
+ PMC until removed by desire of the committer, action of the board, or
+ vote by the PMC. The Chairman may resign as Chairman at any time
+ without resigning membership to the PMC. The chairperson will serve
+ until voluntary resignation, action of the board, or vote by the PMC.
+ The Chairman or any member may be removed from the PMC by a 3/4
+ vote of the PMC.
+ </p>
+
+ <p>
+ In order to be elected to the PMC, a person must have served as a
+ <a href="roles.html">Committer</a> and be
+ nominated by a PMC Member. The nominee must receive 3/4 positive vote
+ with a minimum of 3 positive votes. Abstaining PMC voters do not
+ affect the result.
+ </p>
+ </subsection>
+
+ <subsection name="Creation of Subprojects">
+ <p>
+ PMC members may propose the creation of new subprojects. Creation of
+ a new subproject requires approval by 3/4 positve vote with a minimum
+ of 3 positive votes of the PMC. Abstaining PMC voters do not
+ affect the result. New code enters the DB project in accordance with
+ ASF policy.
+ </p>
+ </subsection>
+
+ <subsection name="Voting">
+ <p>The call for a vote on issues not detailed here may specify
+ requirements for passage. The minimum and default requirement for a
+ passing vote is simple majority of PMC members casting ballots.
+ The default voting period is 10 days and the minimum is 7 days unless
+ the success or failure is arithmetically known.
+ </p>
+ </subsection>
+
+-->
+ </section>
+
+ </body>
+</document>
Added: incubator/uima/site/trunk/uima-website/xdocs/project-guidelines.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/project-guidelines.xml?view=auto&rev=495296
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/project-guidelines.xml (added)
+++ incubator/uima/site/trunk/uima-website/xdocs/project-guidelines.xml Thu Jan 11 09:18:50 2007
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<document>
+
+ <properties>
+ <title>Apache UIMA Project Guidelines</title>
+ <author email="uima-dev.AT.incubator.DOT.apache.DOT.org"> UIMA Documentation
+ Team</author>
+ </properties>
+
+ <body>
+
+ <section name="Apache UIMA Project Guidelines">
+
+ <h3 align="center"><font color="#FF0000"><b>Note: This is a working draft document.</b>
+ </font></h3>
+ <p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p><br />
+
+ <p>This document defines the guidelines of the Apache UIMA Project. It includes
+ definitions of the various categories of membership, who is able to vote, how
+ conflicts are resolved by voting, and the procedures to follow for proposing and
+ making changes to the codebase of the Project.</p>
+
+ <ul>
+ <li>
+ <a href="./roles.html">Roles and Responsibilities</a>
+ <br/> Defines the recognized roles in the project.
+ </li>
+
+ <li>
+ <a href="./communication.html">Communication</a>
+ <br/> Defines how users and developers communicate.
+ </li>
+
+ <li>
+ <a href="./decisions.html">Decision Making</a>
+ <br/> Defines how action items are proposed and voted on.
+ </li>
+
+ <li>
+ <a href="svn.html">Source Repositories</a>
+ <br/> Defines how the Project's source code is organized and developed.
+ </li>
+
+ <!--
+ <li>
+ <a href="./management.html">Project Management</a>
+ <br/>
+ Defines the roles and responsibilities of the
+ Podling Project Management Committee (PPMC).
+ </li>
+ -->
+ <!--
+ <li>
+ <a href="./newproject.html">New Subproject Proposals</a>
+ <br/>
+ Defines the methodology for proposing new top level
+ UIMA Subprojects.
+ </li> -->
+ </ul>
+
+ <p> This is a living document. Changes can be made by the Podling Project Management
+ Committee. Suggestions for changes should be discussed on the
+ uima-dev.AT.incubator.DOT.apache.DOT.org
+ <a href="mail-lists.html">mailing list</a>
+ </p>
+
+ </section>
+
+ </body>
+</document>
\ No newline at end of file