Differences between revisions 24 and 25
Revision 24 as of 2007-02-02 00:51:22
Size: 13102
Editor: YoavShapira
Comment:
Revision 25 as of 2009-09-20 23:07:13
Size: 13102
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

January 2007 Board reports (see ReportingSchedule).

The following projects still need to add a section below:

  • Ivy
  • JuiCE

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


Agila

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


CXF

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:

  • Lots of discussions about various topics (Reliable Messaging, tooling, etc...) occuring on the dev list.
  • Released milestone 1 in December. A bit late, but more feature were added and stability and number of bugs have been good.
  • Working with the Yoko folks about transitioning to CXF (from ObjectWeb Celtix)

  • Started working with the Geronimo folks to integrate with them.
  • Created a eclipse plugin/bundle of our code for the Eclipse STP project for them to integrate our code.

Code aspects:

  • Milestone 1 released, working on setting features for the next RC. (hopefully around March)
  • Started discussing some architectural changes, especially in regard to the tooling.


Felix

Felix is an implementation of the OSGi R4 service platform.

Community

  • The community is working toward incubator gradution.
  • Continued organization of the wiki (and generated web site), creating the subproject documentation section with new documentation on for various subprojects, including a placeholder for the Felix Commons initiative.
  • Voted Karl Pauls as Release Manager.
  • Community voted on and released Felix 0.8.0-incubator.
  • A Felix-related talk was given at ApacheCon 2006 in Austin, Texas.

  • We have seen an apparent influx of new community members based on some new faces being active on the mailing list and even a new contributor (Chris Custine).
  • Emil Ivov announced the 1.0-alpha1 release of SIP Communicator, a Felix-based multi-protocol instant messenger and SIP software phone.

Software

  • Felix 0.8.0-incubator approved by the Incubator PMC and is available for download.
  • Felix Commons initiative started in earnest with the goal of creating bundles out of popular open source libraries, headed by Enrique Rodriguez. John Conlon submitted several POM files for various libraries and Felix Meschberger and Tim Moloney have also expressed interest in doing so.
  • Several patches from Felix Meschberger improving the framework's ability to be used in embedded use cases, particularly issues surrounding framework shutdown and clean up.
  • Created a new Maven 2 plugin for creating OSGi bundles, which uses the BND tool from Peter Kriens. This plugin is quite a bit different than the existing plugin, but the goal is to try to merge the two if possible.
  • Major patch to iPOJO by Clement Escoffier.
  • Initial prototyping of "require bundle" functionality complete in Richard Hall's sandbox, work has begun to transition to trunk.
  • Patch submitted by Chris Custine to implement bundle manifest header localization.
  • Patch submitted by Kamen Petroff to allow additional imports to be specified for the old Maven plugin.
  • Rick Litton worked with the Eclipse community to get their extension point mechanism working on Felix, this effort will continue as bundle localization and require-bundle capabilities are added to Felix.

Licensing and other isses

  • Committed latest OSGi Alliance source code, which is the official release licensed under the Apache license.
  • Committed OSGi Alliance Foundation source code (licensed under the Apache license), which provides stubs for javax.microedition.io, so that we can compile everything again.
  • A patch from Felix Meschberger for the URL Handlers service was put on hold since it was not clear if their were any licensing implications as a result of its inspiration from Equinox code. The patch/functionality is targeted to be resolved for the 1.0.0 release.


FtpServer

FtpServer is an implementation of RFC959 and related protocols.

Community

  • Voted to add new commiter, Dave Roberts. Actually CLA registration and account setup still in progress
  • The mail traffic on the dev list has increase the last couple of months, probably due to more active development again
  • But, we still don't have a large community backing FtpServer. More active communication about the project might be needed.

Code and documentation

  • Migration to Maven 2 complete
  • Integration with MINA almost complete. When done, MINA will be the default choice for socket handling. Our old code will remain to support FTP and FTPS on Java 1.4 platforms
  • We are getting close to a sufficiently complete code for doing a first milestone release soon.
  • Documentation has been migrated to the Confluence wiki. We expect this will make our documentation easier to maintain and up-to-date.


Graffito

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

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

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

Incubation

* Lucene.Net has been under incubation since April 2006

Community

* An active, but a small community exists. The challenge has been to bring in folks who are willing to contribute to the code beside myself.

Code and documentation

* The code base continues to develop and new releases are being made. Recently Lucene.Net 2.0 "final" was release as well as Highlighter.Net 2.0 and Snowball.Net 2.0. In addition, for each of those components, there corresponding MSDN style documentation is also release.


NMaven

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

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:

  • The UIMA Sandbox has been populated with some example annotators
  • A person new to the project, Jörn Kottmann, has written an Eclipse plugin he wants to contribute - we're going through the steps to bring this into the UIMA Sandbox. He has submitted a software grant, and we're awaiting it's acknowledgement (as of Wednesday, Jan 10)
  • We expect to do a release next month, and have been working to get all the little details needed for this completed.

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.


Qpid

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.

* Any legal, cross-project or personal issues that still need to be addressed?

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

* Latest developments.

  • Since entering into incubation we have had one release of the java code base (M1).
  • We have migrated our build system from ant to maven.
  • Development has been moving forward. with improvements in memory footprint management passing the JMS TCK in with the java broker.
  • Addition of .NET client
  • Contributions from 5+ non committers
  • The creation of the first draft of Web site
  • General progress on all models in the code base

* Plans and expectations for the next period?

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.

Roller

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.


January2007 (last edited 2009-09-20 23:07:13 by localhost)