Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: null

December 2009 Board reports (see ReportingSchedule).

These reports were due here by Wednesday, 9 December 2009 so that the Incubator PMC could relay them to the board.


Your project might need to report even if it is not listed below, please check your own reporting schedule or exceptions.

Please remember to include:

  • The "incubating since" info.
  • The project's top 2 or 3 things to resolve prior to graduation.
  • A short description of what your project's software does.
  • The Signed off by mentor: is for Mentor(s) to show that the Report has been reviewed.


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

Aries entered incubation on September 22, 2009.

There are currently no issues requiring IPMC or Board attention.

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.

The following sub-components are actively being developed:

  • Application
  • Blueprint
  • JMX

There has been a lot of activity on the mailing list this month indicating a vibrant community is being built.

Top 2 or 3 things to resolve before graduation:

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

Signed off by mentor: bdelacretaz, gnodet, dims, kevan


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:

  • last round check of first release preparation, issues of compile scripts;
  • all the scripts and documents are committed, official website was updated correspondingly;
  • Announced the first round vote of release of RealClass of BlueSky, but failed due to deficiency of understanding release procedure;

top 2 or 3 to resolve prior to graduation:

  • According to the opinions on RealClass@BlueSky first release which reverbate from dev-mailing list, we'd improve and start the release vote as soon as possible;
  • Once the first release is made, we'd move fast to the next version's transfering on the base of our prototype;
  • Community development is always under concern though it is not realized because of some complex reasons. However, i'd be sure we could do better when the development of the next version is on its way;

Signed off by mentor:


Cassandra is a distributed storage system providing reliability at a massive scale. Started incubation: 01/2009. Opened to community in 03/2009.

Past action items:

  • Get 0.4.0 release out. Done. (And 0.4.1, and 0.4.2)

Other notable activity:

Next steps:

  • Get 0.5.0 release out. (Beta1 was released a couple weeks ago; Beta2 is being voted on now.)
  • Graduate

Signed off by mentor: ant


Clerezza was accepted in the incubator on November 27th, 2009.

We are setting up the podling, waiting on our mailing lists, there are no issues requiring board attention at the moment.

Signed off by mentor: bdelacretaz (champion)


Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context.

ESME entered the incubator in 2008-12-02.

The following items have been performed since the last reporting period

  • Activity on the mailing list has increased dramatically
  • The Apache wiki is full of content and used widely
  • We have at least 4 new contributors adding code on a daily (almost) basis.
  • Professional performance tests have been assisting us to find memory problems
  • Use of Apache Hudson for daily builds
  • Started defining the Jira items necessary for a first release
  • Great deal of media attention - based on Chatter announcement from SalesForce
  • Collaboration with various Apache-external groups (#ubimic, akibot, etc.)
  • Collaboration with OFBiz regarding integration of ESME into the application
  • Users from various enterprises are using ESME in test installations

The following items are planned for the next reporting period:

  • Work on new UI
  • Hopefully, our first release

Top 2 or 3 things to resolve prior to graduation

  • Move all collaboration to the esme-dev mailing list
  • Increase community involvement in the project
  • Multiple Apache releases

Signed off by mentor: bdelacretaz, gianugo


Etch was accepted into Incubator on 2 September 2008. We had our first birthday!

Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages.

This last reporting period saw little activity (0 commits, 0 releases). We're finding it hard to regain our momentum after the dissolution of our team. James and Scott are using etch in their current projects, and Youngjin would like to pick up the c-binding. What we lack is the organizational energy to get things moving.

Release 1.1 is ready but needs some administrative polish before it is *done*.

Release 1.2 is next in the pipeline.

Our continuous integration build problem will only be solved by one of us hosting it at our new gigs. James and Scott are looking into this.

Outstanding items:

  • More community.. we have been Cisco-centered with just a few nibbles outside of Cisco. Things are definitely changing with members employed or so to be employed in different places. Building a stronger community remains our key task. We wish we knew how.

Signed off by mentor: dashorst


Hama has been incubating since 19 May, 2008. It is a parallel matrix computational package based on Hadoop Map/Reduce.

Recent developments:

  • We implemented BSP(Bulk Synchronous Parallel) library on top of the Hadoop.
  • We were re-architecting the computing engine based on BSP to solve a problem of performance and locality of sub-blocks in distributed system.

Required before graduation:

  • Recently, the community and patch contribution is increasing. However, we need more committer/reviewers who are capable of proofing algorithm.
  • We need more documentation (We are preparing to submit a paper to the USENIX) and education about linear algebra and graph algorithm.

Signed off by mentor: brett


HISE has entered incubation on November 6, 2009. HISE provides a deployable component ready to interpret human interactions defined in xml files, as specified in WS-Human-Task 1.0 Spec. It also exposes a taskOperations Web Service for tasks management.

HISE is still in the setup phase, although that's almost done. All initial committers now have an account, the repository and issues manager has been setup. The only missing piece left are mailing-lasts, for now we're using ODE's development list when necessary.

Signed off by mentor: mriou


Kato was accepted into the Incubator on 6 November 2008.

Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API

Recent Activity:

  • The project is working towards making a milestone 1 release. Currently working through release candidates using a multi-staged audit process as suggested by Robert Burrell Donkin.
  • The JSR specification document has been accepted as an Early Draft Review and the review period has passed.
  • The Technology Compilance Kit (TCK) has been running against the hprof and CJVMTI implementations of the API.

The following is planned for next reporting period:

  • Our first release of the RI, demos and TCK.
  • The 1.0 release of the RI in concert with the Final Draft Review (FDR) of the JSR.
  • Finalization of RI and JSR.

Before this project can be graduated we need to produce a usable implementation of the API and more useful tools to encourage adoption and participation of a much needed community.

Signed off by mentor: ant


Libcloud is a unified interface into various cloud service providers, written in python. Libcloud joined the Incubator on November 3rd, 2009. Most of our activity since joining the incubator has been around migrating our existing code and community to the ASF.

  • All but one developer account has been created.
  • All iCLAs from pre-existing contributors have been submitted.
  • libcloud git repo has been migrated to ASF SVN.
  • libcloud mailing list has been migrated to ASF.
  • We are holding a libcloud meetup/dinner in San Francisco on Thursday, December 10th. See the mailing list if you are interested in joining!

We are actively working on a release, which we hope to happen early 2010.

Signed off by mentor: ant


Log4PHP is a logging framework similar to Log4J, but in PHP. The project entered incubation in 2004, retired and restarted again on 2007-07-04. The project got some community feedback, which is good, but not enough for graduation.

  • Christian Hammers has been elected as new Committer
  • The Log4PHP team created 3 release candidates. We are currently voting on them and will bring the proposed release on the incubator list soon
  • Update 13-12-09 - Today Log4PHP made its first release since being in the Incubator for over 4 years!! A truly great effort to get this far, well done team!

Signed off by mentor: jim, GavinMcDonald


OpenWebBeans is an ASL-licensed implementation of the JSR-299: Contexts and Dependency Injection for the Java EE platform which is defined as JSR-299.

OpenWebBeans entered the incubator in October 26, 2008. The following items have been made after the last report

  • We have passed JSR-330 TCK
  • We have increased our community
  • We have voted for graduation
  • We have been updating our code base using final specification
  • We begin to work on JSR-299 TCK
  • We have created a documentation project using docbook

Belows are the next steps;

  • We will try to graduate as TLP
  • We will release the M4 version.
  • We will integrate with the Apache Geronimo
  • We will fully implement specification
  • We will work on JSR-299 TCK

Signed off by mentor: kevan


A number of patches have been (belatedly) applied and elections of some contributors new to RAT but well known to the ASF are in progress.

The issue of final destination would probably be best solved by the creation of a new TLP with a charter slightly wider than just RAT to allow the development of other similar auditing tools useful to the Apache infrastructure.

Signed off by mentor:


River is aimed at the development and advancement of the Jini technology core infrastructure. Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems which are adaptive to change. River has been incubating since December 2006.

Work on the test suite and other parts of River has continued and there is continued talk about doing the AR2 release. The active development community is still rather small.

Next steps before graduation (no changes since last report):

  • AR2 Release
  • Change com.sun.jini.* namespace to org.apache.river.*
  • Reduce barriers to entry for new developers.
  • Increased committer participation.

Signed off by mentor: jukka


Apache Shindig is an OpenSocial container and helps you to start hosting OpenSocial apps quickly by providing the code to render gadgets, proxy requests, and handle REST and RPC requests. Apache Shindig entered the incubator 2007-12-03.

The following tasks have been completed since the last reporting period.

  • Multiple licensing issues have been cleaned up and we have successful RAT tests in place.
  • Successful release of shindig 1.1-BETA5 on 11/24/2009, we now have multiple committers that can cut releases.
  • Approval of two new commiters.
  • Created distribution area with KEYS and our 1.0.0 and 1.1-BETA5 releases.
  • Updated Website

The following items are planned for the next reporting period:

  • Start graduation process.
  • Official 1.1 release.

Signed off by mentor:


Stonehenge has been incubating since December 2008. Stonehenge a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practices and interoperability by using currently defined W3C OASIS standard protocols.

Since the last report in August, the Stonehenge project has been making progress towards, and clarifying the scope of an M2 release with improvements to the first sample application centered on both a unified configuration system, and a claims-based security model. As part of the efforts towards an M2 release, a Sun Metro based implementation of the StockTrader sample was added to the trunk.


Since the last report, about 2 new developers have joined and actively contributed code in the form bug fixes and new functionality, as well as documentation. Apache Stonehenge was demonstrated at the NYC .NET Developers Group, the NYC Connected Systems User Group, ApacheCon, and Microsoft's PDC 2009.


Progress has been steady towards an M2 release. There is on-going work on a claims-based security system that adds a passive and active STS in select implementations of the StockTrader sample application. Interoperability testing is currently underway on this new functionality. As documentation is a key part to this project we've completely revampted out CWiki site to accommodate future samples. Currently there are 19 open JIRA issues marked as M2.


As mentioned in the August 2009 Report M3 would consist of either adding more interoperability features to StockTrader or implementing new sample applications. The latter is currently the focus, and the community is focusing on creating "micro samples" for many common WS-* scenarios, with the goal being around creating implementations with low barriers to entry. Discussions are in progress about testing frameworks and scenarios of interest.

Graduation Map

  • Grow community around new claims based stocktrader implementations just added
  • More thorough documentation that empowers developers to replicate interoperability scenarios demonstrated
  • Demonstrate full interoperability between existing components, and release

Signed off by mentor:


Subversion entered the Incubator on November 7, 2009. Subversion is a version control system.

Mailing lists have been migrated to ASF infrastructure. As of Dec. 10th, the development mailing list has fully migrated over with the old dev@ list being shut down. A users@ list has been created on ASF infrastructure and is being used, but there are a number of published references to the old users@ address, so we are still discussing that transition - that should be complete within the next month. No progress has been made to backfill archives, though some discussion has occurred. (Backfilling of archives is not required for graduation.)

The Subversion project has merged its source code history into the One True Repo at The old repository on has been put in read-only mode, and all new development is happening on Most, if not all, active Subversion contributors have filed their ICLAs, and are continuing development on the new infrastructure.

The most recent RAT report for Subversion shows only 70 unknown licensed files, down from more than 200 a couple of weeks ago. Work continues on either removing inappropriately licensed files from the distribution tarballs or adding licenses to files found deficient.

The community plans to create a new patch release, Subversion 1.6.7, before the end of the year. Although this release will be made under the old license (to avoid having to relicense mountains of code on the release branch), the release process will be observed and monitored by the Incubator PMC as part of the podling's progress toward graduation.

The podling remains optimistic that a rapid progression to graduation is possible in the next month or two.

Signed off by mentor: GregStein, jerenkrantz