January 2007 Board reports (see ReportingSchedule).

The following projects still need to add a section below:

Remove yourself from the above list once you add your report.


Agila was retired this quarter with only the retirement of the mailing lists outstanding (http://issues.apache.org/jira/browse/INFRA-1056).


Project name - CXF

Description - SOA enabling framework, web services toolkit

Date of entry - August, 2006

Top three items to resolve -

  1. Diversity - Active commiters are 90% IONA people 2. Growth of community - related to diversity, we have not yet had the opportunity to add additional commiters. The traffic on the dev list is "steady." With milestone 1 out, we are beginning to attract users. Traffic on the user list is now growing. 3. Not enough documentation or work occuring on the wiki.

Community aspects:

Code aspects:


Felix is an implementation of the OSGi R4 service platform.



Licensing and other isses


FtpServer is an implementation of RFC959 and related protocols.


Code and documentation


Graffito is a framework for content-based applications, especially in portlet environments. Graffito entered incubation on September 20, 2004.

Top three items to resolve before graduation:

  1. Build a self-sustaining community 2. Create an incubating Graffito release 3. Move the JCR mapping component to the Jackrabbit project

There hasn't been much activity in the Graffito project since the last report. A discussion on what to do with the project that still hasn't reached "critical mass" after over two years of incubation is currently taking place. The perceived complexity of the project is seen by many as a barrier to start using or contributing to Graffito. Splitting the project into more manageable component projects was raised as one potential approach to reviving the codebase and project community.


Heraldry is a project to implement the OpenID digital identity specification.

Despite a single large block checkin recently, there is almost no activity on the heraldry-dev list. Also files previously checked in retain LGPL license headers. This has not been corrected despite requests from the mentors.


Lucene.Net is a port of the Java Lucene to C#. The API, algorithm and index are cross compatible.



Code and documentation


NMaven develops plugins and integration for Maven to make building and using .NET languages a first-class citizen in Maven.

Incubating since: 2006-11-17

This is the second monthly report for this podling.

Dan Fabulich (listed on original proposal) had his account created and was added to the committer list.

Healthy discussion taking part about design on the dev@ list.

No new committers to date.


UIMA is a component framework for the analysis of unstructured content such as text, audio and video.

UIMA was accepted for incubation on October 10, 2006

Top 3 things to resolve before graduation:

  1. Complete code transition to Apache, do a release with all IP issues cleared
  2. Attract diverse, active committers
  3. Do a migration tool to enable migration to the Apache version

UIMA's incubation status file is here: http://incubator.apache.org/projects/uima.html

Some recent activity:

We expect that we will need some assistance in doing our first release, to verify we're following the rules properly. We will start by using our mentors, and then ask the incubator PMC to review the proposed release.


The Apache Qpid Project provides an open and interoperable, multiple language implementations of the Advanced Messaged Queuing Protocol (AMQP) specification

Date of entry to the Incubator : 2006-09

Top three items to resolve before graduation

  1. Defining a policy for adding new committers 2. Understanding the details between JCP and announce compliance 3. Making sure we are comfortable with the working relationship between Qpid and the AMQP Working Group.

Our STATUS file needs to be updated wrt this report, which will be done in the comming weeks as we add our first group of new committers.


The whole project has not gone through release review and the license files and notices need to be checked for all languages and components.

During the next period we plan on improving the stability of all language variants. Working towards a standard interoperability test suite and improved test code coverage of the whole code base. To this end we would like to get all the languages passing each others tests. We will also be pushing forward official JMS compliance certification for both brokers. Would like to create a release of the full code set.


We've been very busy with new feature development for Roller, but we have also spent time preparing Roller for graduation and now that we've got an Apache web and wiki presence, two of the last items on our checklist, we feel that we're just about ready to call for a vote. More about that later. For now, here's some status on our accomplishments since our last report in July 2006:

Roller 3.0 released. We detailed the new features of Roller 3.0 in the last report. They include a completely new rendering system with a new URL structure, new template models/macros, better multi-language blog support and a new blog-based front page. We released Roller 3.0 on November 7, 2006. http://rollerweblogger.org/wiki/Wiki.jsp?page=Roller_3.0_WhatsNew

Roller 3.1 development. Following Roller 3.0, we developed another major new release of Roller. The major new features are full-support for weblog tagging, a better rich-text editor based on Xinha, full-preview and bulk-delete of comments. We've made three release candidate releases and with RC3 we're just about ready to make the final release. http://rollerweblogger.org/wiki/Wiki.jsp?page=Roller_3.1_WhatsNew

Established Roller web presence at apache.org. We have now established a web site for Roller at apache.org. Keeping with our community traditions, this site will be a simple front-page that links into a wiki where actual content will be created and updated. http://incubator.apache.org/roller/

Established Roller wiki space at apache.org. We have also started to migrate wiki content from the old Roller wiki to the new wiki site at apache.org. We chose Confluence because we want the wiki to serve as a tightly controlled content management system (similar to the way we were using JSPWiki before). http://cwiki.apache.org/confluence/display/ROLLER

We have almost completed a JPA implementation of Roller back-end. The new implementation is passing about 95% of the back-end unit tests and we are actively working on getting it ready to test and compare against our current Hibernate implementation.

As part of our community building efforts we presented talk on Roller at ApacheCon US 2006 and have submitted multiple Roller-related proposals to ApacheCon EU and JavaOne 2007.