October 2007 Board reports (see ReportingSchedule).

These reports are due to the Incubator PMC by 10 October 2007


Project name - Apache CXF

Description - SOA enabling framework, web services toolkit

Date of entry - August, 2006

Items to resolve before graduation:

Community aspects:

Code aspects:


Project name - Apache FtpServer

Description - Java based FtpServer

Date of entry - March, 2003

Progress since last report

* Only minor development efforts since last report due to commiter time limitations, mostly focused on fixing bug reports and feature requests which are coming in at a steady pace. More people seems to use FtpServer now that activity is steady on the project. Voted in a new commiter, Clint Foster. He is currently in progress of setting up his account and get going with the practical details. * Niclas Hedhman added as a much needed mentor to the project. * Continous builds are in the works using the vmbuild1 server, with the aim of producing snapshots which has been repeatably asked for

Top three items to resolve

1. Growth of community - we still need more active members 2. Getting snapshot builds published automatically by the build server (minor details left to finish) 3. Getting s stable release out, need more active members to have good review





RCF is a rich component set (ajax-style) for JSF. The RCF Wiki has been created and all committers are now set. We started discussion on the OpenSource efforts, how to manage it, since we need to provide a migration path for current users. We are waiting for an import of a current code drop into the repository.



Project name - Apache Lucene.Net

Description - Lucene.Net is a source code, class-per-class, API-per-API and algorithmtic port of the Java Lucene search engine to the C# and .NET platform utilizing Microsoft .NET Framework.

Date of entry - April, 2006

Progress since last report - We have seen good activities in the past three months on the mailing list (both the dev and user). Unlike in the past, where I was taking care of all fixes in the code in preparation to a release, I have seen considerable patches submitted by the community to resolve open issues in Lucene.Net 2.1 work. This is very encouraging and I would like to suggest to the community to vote on adding one of the active patch submitter as a committer.

Code aspects - Code is very stable with current "beta" version of 2.1 which we expect to release in the next few weeks.

Community aspects - We have good followers and the past three months have shown good commitments for submitting patches.

Top three items to resolve -

1. Growth of community - while this has been improving, we still need more active members, specially those who submit patches.

2. Release Apache Lucene.Net 2.1 and start working on 2.2 / 2.3.

3. Vote in a new committer.