The Apache Software Foundation
The Apache Software Foundation Incubator

Apache UIMA Project Incubation Status

This page tracks the project status, incubator-wise. For more general project status, look on the project website.

The UIMA project graduated on 2010-03-18


The Apache UIMA Project will create a standardized component framework for the analysis of unstructured data, guided by the UIMA Oasis Standard (http:/ It will include an SDK and tooling for composing and running analytic components written in Java and C++; a scaleout capability, and a set of annotators and other components that can be used with the framework.


Listed newest first.

  • 2010-03-18 Apache UIMA graduates to a top-level project
  • 2010-01-26 Apache UIMA 2.3.0-incubating released
  • 2010-01-04 New committer: Bhavani Iyer
  • 2009-08-10 New committer: Tommaso Teofili
  • 2009-07-11 New committer: Burn Lewis
  • 2009-03-19 UIMA approved as an OASIS Standard
  • 2008-11-19 New committer: Tong Fin
  • 2008-11-19 New committer: Jerry Cwiklik
  • 2008-07-24 Apache UIMA-AS 2.2.2-incubating released
  • 2008-05-07 Apache UIMA 2.2.2-incubating released
  • 2007-12-19 Apache UIMA 2.2.1-incubating released
  • 2007-10-08 New committer: Jörn Kottmann
  • 2007-08-23 Apache UIMA 2.2.0-incubating released
  • 2007-03-14 Apache UIMA 2.1.0-incubating released
  • 2006-12-07 Establish UIMA Sandbox
  • 2006-10-05 Project accepted by the Incubator PMC
  • 2006-08-23 Project proposed to the Incubator PMC

Project info

  • link to the project status file (Committers, non-incubation action items, project resources, etc)

If the project website and code repository are not yet setup, use the following table:

item type reference
Website www
Mailing lists dev
private (PPMC)
Bug tracking JIRA
Source code svn
Mentors jukka Jukka Zitting
rubys Sam Ruby
coar Ken Coar
Committers mbaessler Michael Baessler
cwiklik Jerry Cwiklik
eae Edward Epstein
tongfin Tong Fin
twgoetz Thilo Goetz
bhavani Bhavani Iyer
joern Jörn Kottmann
alally Adam Lally
burn Burn Lewis
schor Marshall Schor
tommaso Tommaso Teofili

Incubation status reports

Incubation work items

Project Setup

This is the first phase of incubation, needed to start the project at Apache.

Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the project to be incubated

date item
2007 02 07 Make sure that the requested project name does not already exist and check to be sure that the name is not already trademarked for an existing software product.
N/A 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.
N/A If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
2006-10-27 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.

Interim responsibility

date item
2006-10-05 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2006-11-03 Subscribe all Mentors on the incubator PMC and general lists.
legacy Give all Mentors access to all incubator CVS modules. (to be done by PMC chair)
2006-10-27 Tell Mentors to track progress in the file 'incubator/projects/uima.html'
date item
2006 11 02 Check and make sure that the papers that transfer rights to the ASF have been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2007 02 01 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

date item
N/A Check and make sure that for all code included with the distribution that is not under the Apache license, the ASF has the right to combine with Apache-licensed code and redistribute.
2007 02 01 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.

Establish a list of active committers

date item
2006-11-03 Check that all active committers have submitted a contributors agreement. Is required by ASF process.
2006-11-03 Add all active committers in the STATUS file. See above.
2006-11-03 Ask root for the creation of committers' accounts on


date item
2006-11-03 Ask infrastructure to create source repository modules and grant the committers karma.
2006-11-03 Ask infrastructure to set up and archive Mailing lists.
2006-11-03 Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira).
2006-11-02 Migrate the project to our infrastructure.

Project specific



These action items have to be checked for during the whole incubation process.

These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
  • 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.)
  • Are project decisions being made in public by the committers?
  • Are the decision-making guidelines published and agreed to by all of the committers?

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?

Project Specific



Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • If graduating to an existing PMC, has the PMC voted to accept it?
  • If graduating to a new PMC, has the board voted to accept it?

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks?