Differences between revisions 25 and 26
Revision 25 as of 2006-10-23 10:58:48
Size: 11645
Editor: Upayavira
Comment: purely whitespace stuff for Wicket
Revision 26 as of 2009-09-20 23:07:14
Size: 11645
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

October Reports (see ReportingSchedule)


Agila

Entered incubation in February 2005.

Nothing new on Agila for quite a while. All activity has been transfered to Ode. The Jakarta PMC as voted to retire the project.


AltRMI


CXF

Project name - CXF

Description - SOA enabling framework, web services toolkit (Celtix and XFire merge)

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." 3) Demonstrations of apache processes - working on a milestone 1 release, etc...

Community aspects:

  • Jason van Zyl resigned as Mentor. We have three other mentors, but may be bringing a forth on board.
  • Setup two "spaces" on confluence to hold developer docs (and the project home page) and user docs. We'd like to encourage more people to help out there.
  • Voted to start deploying periodic SNAPSHOTS to the maven2 snapshot repository to help other projects like yoko, geronimo, servicemix, etc... take dependencies on and integrate CXF
  • Voted to officially name the project CXF instead of CeltiXfire

  • PPMC setup and functioning, process started to get other non-active commiters more involved.
  • Have reached out to Geronimo folks to help "pick their brains" about the required features for better JCA support.
  • Started working with the Yoko project to get them to update from using Celtix to CXF.

Code aspects:

  • Getting close to finalizing the code for milestone 1. Most required features are now working.
  • Some performance testing was done. Some performance problems were identified and fixed.
  • Working on defining what the final kits will look like. (what is included, what the user is expected to already have, etc...)
  • Started discussing some architectural changes, especially in regard to the tooling, for after milestone 1.

Licensing:

  • Had some discussion at ApacheCon about the rhino/js jars that are NPL and what to do with them. Still somewhat unresolved.


Felix

Community

  • Proper wiki/web page created by Marcel Offermans and Ronald Spierenburg.
  • Manuel Santillán, Jose L. Ruiz, and Juan C. Dueñas added as committers for their work with JMX and OSGi (i.e., JMood).
  • Didier Donsez added as a committer for his long-time work around OSGi and Felix.

Software

  • Contribution of the JMood project for another approach to JMX/OSGi integration from Manuel Santillán, Jose L. Ruiz, and Juan C. Dueñas.
  • Contribution of extensive set of example code from Didier Donsez.
  • Contribution of log service implementation from Dale Peakall.
  • Major framework enhancements to the Felix framework around security from Karl Pauls.
  • Specification compliance improvements for the framework around native library loading by Arnaud Quiblier and Richard Hall.
  • Work on implementing the framework resolver algorithm using a generic capability/requirement model was committed into Richard Hall's sandbox; work continues on try to modify this new resolver to support require-bundle.
  • Continued enhancements to iPOJO from Clement Escoffier.
  • Work on a Maven-based testing harness for Felix by Alex Karasulu.

Licensing and other isses

  • Attempt for gradution was post-poned to concentrate on creating a release that addresses any and all outstanding obstacles for release.
  • Removed javax.microedition.io dependency for the time being until a proper licensed version is available from the OSGi Alliance.


FtpServer

Development on FtpServer is slowly progressing. Currently the focus is mostly on filling the gaps when it comes to automatic testing.


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:

  • Upgrade to the latest license header and copyright notice policy
  • Create an incubating Graffito release
  • Move the JCR mapping component to the Jackrabbit project

Graffito activity has increased noticeably since the last report, especially due to interest from within the Jackrabbit community. New bug reports and patches are also being contributed.

  • Jukka Zitting was voted in as a new mentor for the project. He will accompany Raphaël Luta in that role.
  • Given positive feedback from both communities, we are evaluating options for moving the JCR mapping component from Graffito into the Jackrabbit project. This would expose the component to a wider JCR developer community and a larger audience of potential users.
  • There has been renewed discussion on producing incubating releases of the Graffito components
  • Edgar Poce has been working on a related JCR-based wysiwyg portlet prototype, using the Graffito mailing list for design discussions, but the implementation approach differs from the Graffito portlet model, so at least for now the tool is not being integrated into Graffito


Harmony

Entered incubation in May, 2005. Apache Harmony is primarily focused on the creation of an independent, compatible implementation of Java SE 5.

The project has voted to ask to graduate from the Incubator, and is currently discussion the topic with the Incubator PMC.

Progress continues in both code and community:

Community

  • The project has added 6 new committers
  • The project has added 3 committers to the PPMC
  • Diversity continues to increase in participants
  • Pure development list traffic hit a record of 1961 message with a combined volume of JIRA and commit messages of 2851
  • The ApacheCon technical session and BOF on Harmony were reasonably attended

  • Our interaction with the Yoko community has been constructive in terms of community - they elected a Harmony commmitter to be a Yoko committer - as well as technology (see below)
  • We have the support with the external MX4J project to "gently fork" their codebase as the foundation for our JMX 1.2 extentions as required by the Java SE 5 spec

Technology/Other

  • The project is in the process of updating it's license headers in the codebase. The classlibrary and DRLVM virtual machine have been updated, with the rest still in progress.
  • Classlibrary coverage has reached 94%
  • DRLVM is stablizing and running at a reasonable level of performance
  • We've incorporated the binary milestone from Yoko as our implementation of CORBA, and will update with their release when that happens
  • We've accepted several tool contributions (javah, javap) and expect to produce a JDK snapshot complete with javac, javap, javah, rmic and keytool
  • JBoss now "runs" on Harmony (for certain values of "runs")
  • MX4J as source (it has the Apache License) will be integrated into the project codebase as the starting point for our required JMX implementation in the classlibrary.


Heraldry

While progress has still been a bit slow, some good milestones have been reached in the past month.

  • Majority of commiters from initial proposal now have accounts
  • Project page updated as well as now linked to from the Incubator's website
  • Code contribution of the Ruby identity provider has been made
  • Yadis test code has been checked in
  • Ruby OpenID plugin has been contributed

We're also now very close to having the OpenID and Yadis libraries contributed to the project, just waiting on two or three more accounts to be created.


JuiCE


Lucene4c

The project is dormant. Will probably shut things down for good at ApacheCon.


Lucene.Net

Lucene.Net continues to grow. Recently Lucene.Net 1.9.1 "final" was released. In addition, Lucene.Net 2.0 is now in "beta". The mailing list is seeing more traffic with questions, bug reports and enhancement requests. In September, Jeff Rodenburg was added as a committer to Lucene.Net. And finally, a new logo Lucene.Net logo was added to the incubation site (http://incubator.apache.org/lucene.net/)


Roller


Wicket

Project name - Wicket

Description - Web development framework focusing on pure OO coding, making the creation of new components very easy

Date of entry - October, 2006

Top three items to resolve -

  • 1) Remove a LGPL date picker component from Wicket-extensions

    2) Work out how community is going to manage releases (e.g should we release current maintenance branches at SourceForge? 1.2.3->SF, 1.3->ASF, 2.0->ASF) 3) Settle into ASF context more

Community aspects:

  • All bar one of Wicket's SourceForge committers have come over to Apache

  • About to vote in our first new committer since starting incubation
  • PPMC is starting to explore setting up project guidelines, for example should committer votes be done in private/public; should all committers be on PPMC or not)

Code aspects:

  • Working on completing 1.2.3 release - last release to be done at SourceForge - before 1.3 development starts. 1.3 likely an ASF release

  • Work continues steadily on 2.0, also expected to be an ASF release

Licensing:

  • Need to remove/resolve a LGPL dependency in Wicket-extensions on a date picker component

Infrastructure:

  • All ICLAs are signed, all accounts created, and all karma granted (still need to get ICLA from one chap who didn't come to ASF, and to can for other contributors that may need one)
  • Subversion repository successfully imported into ASF repo by Graham Rooney (many thanks). All development work is now taking place in ASF repo.
  • dev, private and commits email lists moved to incubator. All development work is happening on these lists
  • user list remains on SourceForge for the time being (while development settles in. May move over to ASF once we've done a real ASF release).

  • Wicket Wiki (http://www.wicket-wiki.org.uk/wiki/index.php) has been ported across to Confluence (http://cwiki.apache.org/WICKET/)

  • JIRA has been set up and bugtracking is now happening there. A SourceForge->JIRA importer has been written, but not yet executed on Wicket issues.

XAP

XAP is a declarative framework for building, deploying and maintaining Ajax-based rich internet applications with the goal of dramatically simplifying Ajax application development. XAP entered incubation in May 2006.

Top three items to resolve before graduation:

  • Bring the codebase to a level that contributors can make contributions without significant pain;
  • Create a XAP incubating release with proper packaging and quality
  • Engage a higher level of community activity and contribution

Community

  • Various discussions on the XAP dev list on technical issues such as applicaiton initialization and DOM model;
  • Attended ApacheCon and gave a lightening talk on XAP

  • A session called "Introduction to XAP" was presented at AjaxWorld Conference and the upcoming Ajax Experience conference

  • Various third party expressed interest in learning more about XAP, but complained that not easy to get infomation and not easy to figure out what XAP code does.

Code

  • Achieved milestone 3: added more widgets and streamlined initialization
  • Various bug submission and JS unit tests submitted by Trevor Oldak
  • Update demo applications with improved performance
  • Working towards the next milestone: more widgets and some appealing demos to attract more developers

October2006 (last edited 2009-09-20 23:07:14 by localhost)