incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject Incubator Board Report October 2009
Date Tue, 20 Oct 2009 16:09:09 GMT
The Incubator is running smoothly, with nothing requiring the Board's
attention at this time.

There is a vote underway to graduate the Click project as a TLP.  Lucene.NET
has been voted on by the Incubator PMC and the Lucene PMC to transfer to a
Lucene sub-project.

As was discussed in last month's report, the Aries project (OSGi-related)
has now been accepted for Incubation, and reported (below).  The Geronimo
project is already working with and contributing to the Aries project.


= Ace =

Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.


 * Angelo van der Sijpt accepted our invitation to become a committer, after
contributing various patches related to a new Web UI.
 * Toni Menzel contributed patches to migrate to a customized, Pax Runner
based launcher and integrate the Web UI in Apache Felix Web Console.


 * The GWT based Web UI is now fully functional. A lot of work has gone into
 * An Apache Felix Web Console plugin was created so the ACE UI can also be
displayed inside that console.
 * Target artifacts are now built by Pax Runner, allowing us to easily use
any OSGi framework implementation to run the software on.
 * The configurator we use can now update configuration data on the fly.
 * Fixed a lot of integration tests run in our continuous build. A few bugs
still remain.

Licensing and other issues:

 * None at the moment.

Things to resolve prior to graduation:

 * Make a release.
 * Grow the community some more.

= Aries =

Aries will deliver a set of pluggable Java components enabling an enterprise
OSGi application programming model.

Aries entered incubation on September 22, 2009. This is our first board

There are currently no issues requiring IPMC or Board attention .

All infra resources have been set up (svn / site / mailing lists) very
quickly. The svn area has been organized with a single trunk for now, though
we still need to settle the discussion about components lifecycle and the
svn layout. IBM has contributed some code that has been imported into svn
and the JNDI modules have already been imported into trunk. Both Geronimo
contribution (OSGi Blueprint Services) and ServiceMix contribution (OSGi
Transaction Manager) have been imported into trunk.

On the community side, we've already voted 3 additional committers (Adam
Wojtuniak, Alan Keane and Niclas Hedhman) who had expressed their interest
in joining the project just after the acceptance vote on the proposal was

There is a lot of discussions and activity on the mailing lists.

Top 2 or 3 things to resolve before graduation:

 * Build community
 * Create a release
 * Address the project scope concerns raised during acceptance vote

= Bluesky =

BlueSky has been incubating since 01-12-2008. It is an e-learning solution
designed to help solve the disparity in availability of qualified education
between well-developed cities and poorer regions of China.

What we've completed in the last month:

 * Instead of using ARTS, we replace it simply by basic soundcard write
 * Solve all the legal issues lies in RealClass system and upload whole
source code of the four components to Apache SVN repos;
 * update the incubation status page:
   BlueSky wiki:
   BlueSky official website:
 * Remove Hibernate module from MersMp system;

top 2 or 3 to resolve prior to first release:

 * Use doxygen to generate API documents of RealClass system
 * Replace Hibernate module with other library compatiable with ASL

= Chemistry =

Apache Chemistry is an effort to provide a Java (and possibly others, like
JavaScript) implementation of the upcoming CMIS specification. Chemistry
entered incubation on April 30th, 2009.

There are currently no issues requiring board or Incubator PMC attention.


    * No notable community changes.


    * Development continues at a steady pace, mostly driven by Florent
Guillaume and Gabriele Columbro.
    * A full 0.62/0.70 CMIS AtomPub binding TCK contributed and maintained
against the spec by David Caruana
    * The codebase is currently split to two branches, targeting different
draft versions of CMIS.


    * Chemistry is planning to use as a Maven
deployment target

Issues before graduation

    * Stabilize the general interest into a sustainable development
    * Make sure that all licensing details conform with Apache policies
    * Create an Apache release of the Chemistry codebase

= Empire-db =

Empire-db is a relational data persistence component that aims to overcome
the difficulties, pitfalls and restrictions inherent in traditional Object
Relational Management (ORM) approaches.  Empire-db is on the Apache
Incubator since July 2008.

After we had completed development activities on release 2.0.5 in July we
were hoping to get the release accepted by our mentors the Incubator PMC
within a couple of weeks. Unfortunately we first faced the problem that due
to vacation time we were not able to get a mentors vote on our PMC. With
recommendation of one of your mentors we then decided to move on to the
IPMC. Again we did not get many responses at first, but finally we found
some reviewers who discovered some incomplete or inconsistent documentation
issues and raised some concerns about the content of the distribution files
and maven artifacts. After we had corrected these issues and after
presenting a new release candidate to the IPMC new issues came up that had
not been raised before and in the end it took us 6 lengthy iterations before
we finally got our release accepted by the incubator PMC. After the approval
of Empire-db 2.0.5 the new release was published in the Maven repository and
on our website. Now that the new project structure has been established and
approved we hope that the release process of our next release will run a lot
smoother and quicker.

Meanwhile new plans have been made for our next release where intend to
provide a code generator that allows generation of the data model class
files from an existing database. For this a new subproject and the
corresponding JIRA tasks have already been set up. As such a suggestion has
been raised by one of our users, We are hoping to get new users involved in
our development team.

The project's top 3 things to resolve prior to graduation:

 * Grow a larger community
 * Roll out a second maven-based release

= Imperius =

Imperius has been incubating since November 2007.

Imperius is a rule-based policy evaluation engine based on the CIM-SPL
language from Distributed Management Task Force (

In September, CIM-SPL was ratified as a DMTF standard. See

In September, Sun made an interim build of Imperius available as part of its
Open Solaris effort.  The build can be found at

In September, IBM made their Policy Management Library based on Imperius
available on its alphaWorks site at

There has been some forward progress in the Imperius community in the past 3

After discussion, a number of bugs were fixed with an en masse commit.
There has also been progress towards an initial release by the community. A
release candidate was created. Problems were found with this and are being

In general, communication within the community continues to be limited and

Things to resolve prior to graduation:

 * Create an Apache release
 * Grow the community

= JSPWiki =

JSPWiki has been incubating since September 2007.

JSPWiki is a JSP-based wiki program.

Development on the trunk has picked up again after the summer, with focus on
areas: improving the quality of the JCR back-end, completing the
migration of the MVC presentation layer, and stabilizing the trunk now that
the JCR back-end is in place. Progress on all fronts continues. Over the
quarter, for example, unit test compliance has risen from the low 80s to
nearly 99.5%.

Of the 27 items on the graduation checklist, 18 are complete. Two of the
items are documentation related: writing the charter and IP process
The most significant remaining task is to release a 3.0.0-incubating-alpha1
With the increasing stability of the trunk, an alpha release in the near
term looks
increasingly likely. All other remaining checklist items are purely ASF
process and
infrastructure related.

The developer list currently has 86 members, a minor increase from 83; and
user list has 187 members, an increase of nine people.

= Olio =

Olio is a web 2.0 toolkit to help developers evaluate the suitability,
functionality and performance of various web technologies by implementing a
reasonably complex application in several different technologies.

The developers are working on a second release - 0.2. This release features
more alignment between the different implementations, performance
enhancements, code cleanup, bug fixes etc. This will be the first  binary
release for the Java implementation.

Even without a kit release, the Java implementation already has several
users. Olio is continuing to gain users and being used for diverse purposes.

There are 30 subscribers to the user list and 30 subscribers to dev.

There are over a hundred JIRA issues filed, and continuous activity toward
closing them (about 26 open currently)
Graduation From Incubation:

Diversity of committers is the primary issue with the project - we still
need to work on recruiting more committers from different

= Shiro =

Shiro is a powerful and flexible open-source application security framework
cleanly handles authentication, authorization, enterprise session management

Shiro has been incubating since June 2008.

We are very excited to report we have added Kalle Korhonen as our first new
committer since joining the incubator.  This marks a big project milestone
for us as we continue to grow our community.

There remain a few project infrastructure inconsistencies resulting from
our previous name change as described in this email thread:

Resolving these inconsistencies are a high priority and should be resolved
as soon as possible.

An issue of how Shiro is configured was the largest issue impeding our first
Apache release.  That issue has been largely resolved and once finalized,
we should be able to focus on our first Apache release.

The project team is not considering graduation at this point, as the code is
not ready for an Apache release. Once IP clearance is complete, we'll
attempt our first incubator release.

The status is being maintained at

= Socialsite =


= Tashi =

Tashi has been incubating since September 2008.

The Tashi project aims to build a software infrastructure for cloud
computing  on massive internet-scale datasets (what we call Big Data). The
idea is to  build a cluster management system that enables the Big Data that
are stored in  a cluster/data center to be accessed, shared, manipulated,
and computed on by  remote users in a convenient, efficient, and safe

Development activities have included a communication layer rewrite, the
introduction of an EC2 compatibility layer, a bridge that allows the use of
Maui as a scheduler for Tashi, patches for HVM booting in Xen, DNS updates,
using RPyC on Python 2.4, the SQL backend, the updateVm RPC, and the client
utility's output, fixes to and an expansion of the VM statistics collection
code in the Qemu backend.  Additionally, a notes field was added to the host
definition, a syslog handler was added for logging, the scheduler was
modified  to reduce the number of repeated messages, and the documentation
for setting up  a single machine and configuring DHCP and DNS servers was

The project is still working toward building a larger user and development
community.  We have recently been contacted by some potential users from
Taiwan  HP, as seen on the -dev list.  Additionally, two developers have
increased the  quantity of patches submitted in this quarter, expanding the
number of  developers working on the project.  The upcoming tutorial at
SC'09 [1] is  drawing near and we expect to draw in more potential users at
the event.

Items to be resolved before graduation:

 * Prepare and review a release candidate
 * Develop community diversity (currently Intel and CMU committers)


= Traffic Server =

The last month has been focusing on code cleanup and build system changes.
The Traffic Server project was accepted into the incubator in July 2009, and
we're still actively working on getting the community built up and to get
ready for an Open Source release of TS.

The Yahoo! team has worked on the following code cleanup tasks in
preparation for the code migration:

 * All Coverity issues (that are relevant) have been fixed.
 * All code that we are not Open Sourcing (at this point) has been removed.
 * We have eliminated all Yahoo! proprietary code, cleaned up comments, and
unnecessary attributions.
 * Build system has been reworked / improved, and the cleaned up code now
builds and run.
 * We have eliminated a few licensing issues (there was nothing there that
would prevent us to push the code to SVN, but our legal wanted this to be
eliminated before code push).

In addition, we have completed the following incubator tasks:

 * SVN area has been created (in preparation for code push),
 * Confluence Wiki has been created, and documentation migration has begun, .

Outstanding Incubator tasks include:

 * We're working on a final sign-off from our (Yahoo!) Legal Department,
which is currently holding us back from pushing the code. The goal here is
to assure that we have full distribution rights to all code that we push to
Apache SVN.
 * Migrate project code to ASF infrastructure.
 * Get the Trademark issue resolved (see below).
 * Finish the ASF copyright and license attribution in all source files
(this is partway done).

Also, we'd like to bring up again the proposal that we made during the
incubator process for how to deal with the Traffic Server trademark. Our
preferred option is the following (from Chuck Neerdaels and our legal dept):

* The preferred option is to provide ASF with a letter of assurance stating
that we own all right, title and interest in and to the TRAFFIC SERVER mark
and the four active registrations and that we will not take any action
against ASF or any of its licensees during the life of these registrations
{and we'd express our intention of letting them lapse and expire]

* If this is acceptable to ASF, then that is what we'll do. If not, the
other alternative, which is more elaborate, is to assign all rights for the
Traffic Server trademark to the ASF.

= Thrift =

Thrift is a software framework for scalable cross-language services
development. It combines a software stack with a code generation engine to
build services that work efficiently and seamlessly between a variety of
programming languages. Thrift entered the Apache Incubator in May 2008.

 * Release candidate is still outstanding -- review has continued but the
release has not been finalized
 * Lots of general iteration and bugfixing activity

Generally, things are in a similar state as last quarter. There is plenty of
activity in JIRA and on the mailing lists, but we need to finalize our
release candidate and get it officially out the door.

= UIMA =

UIMA is a component framework for the analysis of unstructured content such
as text, audio and video. UIMA entered incubation on October 3, 2006.

Some recent activity:

 * New committers added: Burn Lewis and Tommaso Teofili,
 * Work almost complete on 2.3.0 release
 * New integration with other Apache projects (such as Lucas, Tika Annotator
and UIMA-AS Camel Driver - integrations with Apache Lucene search, Apache
Tika and Apache Camel to drive UIMA AS processing).
 * The Configurable Feature Extractor, including documentation, was
refreshed, and will be included in the next release.
 * The next sandbox release is more than doubling the number of pre-done
UIMA components that are available with the framework.
 * IBM announced a "grand challenge" effort to have a computer compete live
against humans on the popular (in the USA) TV game, Jeopardy! in answering
open-domain questions, (not connected to the internet), in real time - and
that this system is being built upon UIMA and UIMA-AS (see ).
 * building improved: Maven use optimized using parent POMs and RAT, static
jar binaries removed from the build process
 * code quality improved: wide use of generics, stale code deprecated
 * UIMA-AS has been graduated out of the Sandbox as an add-on package.
 * The Cas Editor has been graduated out of the Sandbox and is now part of
base UIMA.
 * academic UIMA workshop (see with strong participation
from UIMA's users list community

Items to complete before graduation:

 * UIMA is ready to graduate, and plans to start the graduation process
after the current release activity is finished.

= VXQuery =

The VXQuery Project implements a standard compliant XML Query processor. It
has been in incubation since 2009-07-06.

September activities:

 * created project home page
 * some code additions
 * some progress on CCLAs (still not done)

Completed setup steps:

 * JIRA/Wiki set up
 * SVN access for initial committers set up
 * Initial codebase submitted to SVN
 * Mailing lists set up
 * All ICLAs and most CCLAs in place
 * Incubator status page set up
 * project home page set up

Immediate goals:

 * Get all CCLAs in place
 * Fix mailing list issues

Top 3 issues before graduation:

 * Complete podling setup
 * Build community
 * Create a release

= Wookie =

Apache Wookie(Incubating) is a project to create open source software for
adding widgets to your applications.  It has been in incubation since July

 * No issues currently require IPMC or Board attention
 * All ICLAs and CCLAs in order to import incubator code to ASF repository
  * Code import process started via INFRA-2273
  * Paul Sharples account created
 * Widgets/Wookie Meetup meetup in London (13th Oct)
 * OpenSocial/SocialSite/Wookie meetup at ApacheCon
 * JIRA Activity is increasing and patches are starting to arrive

Items for next reporting period:

 * Remove GPL dependencies
 * First Apache release

Items to be resolved before graduation:

 * Complete podling setup
 * Create a release
 * Develop community

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message