July Reports (see ReportingSchedule)
- Continued work on the code, working towards a 0.1.0 release
- Added two new committers to the project (Stephen Duncan and Garrett Rooney). Stephen is still in discussions with his employer regarding his CLA.
- Rob Yates' ICLA has been received and account set up
- Jira has been set up
Upayavira says "Felix progresses well as a community, increasing in maturity, and I believe that Felix is nearly ready to graduate. In preparation for that we have been going over the relevant issues: auditing licensing of code and libraries, porting non-ASF services onto ASF hardware (a Confluence wiki) and improving our public website."
- Stephane Frenot was added as a committer.
- Defined and accepted Felix community roles and processes document.
- Working with Maven community to get OSGi packaging features into the Maven core with the involvement of Jason van Zyl and Peter Kriens.
- Announced "Felix Commons" initiative for bundling common libraries for use in the OSGi framework.
- Working on and nearing completion of various graduation tasks, such as license verification.
- iPOJO project contribution which uses byte code instrumentation to enable POJOs to be used in an OSGi environment and to simplify OSGi development.
- Event Admin standard OSGi R4 service implementation committed along with bridges for UPnP, Wire Admin, and User Admin.
- Managed OSGi framework using JMX committed.
- Committed major updates to the OSGi Maven plugin to simplify bundle packaging by auto-generating bundle metadata with the involvement of Peter Kriens.
- Many improvements to core Felix OSGi framework, such as auto-detecting which core packages to export based on the current execution environment.
Several OSGi-related presentations at ApacheCon EU from Felix community members.
- Migrated Service Binder to kxml2 to avoid licensing issues with kxml1, thanks to community member Jan Rellermeyer.
- Need further investigation of MX4J licensing; it appears to be a derivative of the Apache license.
- Need further investigation of javax.microedition licensing.
- Ensured that all source code has appropriate license headers
The Harmony project continues to grow in both community and code.
On the community side, our mail list traffic continues to increase, with an all-time high of 1495 messages on the dev list in June. As of this writing, there are 895 messages so far for July. These numbers do not include any commit or JIRA traffic. Content of the list is fairly healthy, concerned with the technical aspects of both our virtual machines as well as the class library. Recent donations are increasing the diversity of participation in terms of individuals, with the majority of new faces participating in and around the virtual machine donation from Intel. Mail list traffic on the ppmc list is very low, and with the exception of one issue related to a contribution, pertains only to new committer and ppmc member discussion and votes. We have added 4 new committers, have several identified as potential, and have recently voted to add committers to the PPMC (although they haven't been notified as of this moment).
On the technical side, we have been fortunate to continue to receive code from 3rd parties, primarily Intel. These donations represent code that was intended for Harmony but due to a combination of internal "process" backlog at Intel, as well as a sensitivity to the rate at which the community can digest and adopt the code, not all code was donated at once. We are very sensitive to ensuring that after a donation happens, any development on that continues in the project, and we constantly look for ways to enable people to help. We have recieved significant additions like Swing/AWT/Java 2D for the classlibrary, as well as the "DRLVM" modern virtual machine, which now gives us about 81% coverage of the Java 1.4 API (estimated at 78% of the Java 5 API, our target), as well as a VM to run that with modern garbage collection and JIT.
We are currently working through the details of using public-domain code from Doug Lea for the "java.util.concurrent" package. This is the 'reference implementation' for this package, and used by Sun, among others. We wish to use this code (as it's considered the best implementation as well as the only one available to us), and further build a bridge between our community and the community surrounding this code (mainly the JSR-166 expert group, and organizations like us that use it...)
We are waiting for things to move in the new Santuario TLP. Not much progress otherwise.
There has been no progress since the last report. This project should really be officially marked as dormant.
Lucene.Net continues to progress. Recently Lucene.Net 1.9 RC1 Final was released. In addition, Lucene.Net 1.9.1 Beta is released. Work is underway to release Lucene.Net 2.0 Beta by end of July. Folks are beginning to discover Lucene.Net and activities on the project from posting questions and code fixes are beginning to show some signs of life. However, things are still slow in terms of participation. Lucene.Net can use some publicity and exposure which I intend to start doing by asking to create a link to Lucene.Net on the main Jakarta Lucene web page as well as by creating a Wiki page for Lucene.Net.
Major new developments in Roller 3.0. Working in the roller_3.0 branch, Allen Gilliland and Dave Johnson have been making extensive changes to Roller's blog/page rendering system. Roller 3.0's new features are:
- Completely new URL structure, with redirection for old URLs
- Completely rewritten/refactored page/feed rendering system
- View renders are pluggable
- Made progress towards static rendering
- All new set of page models and macros
- Multi-language blog support, based on new URL structure
- Front-page of Roller is now a blog with optional site-wide features:
- Planet page model and planet display macros
- Site-wide model supports listing of new users, new weblogs, hot weblogs and other community oriented queries.
- Macros for diplaying A-Z user and weblog directories
Licensing issues may be behind us. Dave Johnson worked to satisfiy ASF licencing and packaging requirements and as a result of this work, we made our first Roller release (2.3) on ASF infrastructure:
- Licence headers in every file
- Changed to org.apache package names for all Java code
- Removed all LGPL code from release (Hibernate, JSPWiki, Jazzy, etc.)
- Created a Roller Support project on Java.Net for non-ASF Roller goodies such as LGPL/GPL licensed themes, plugins and other downloads.
New APP draft #9 support. The IETF released Atom Publishing Protocol (APP) draft #9 and Dave Johnson updated Roller's APP implementation to support this new draft. APP is an "experimental" feature in Roller and is turned off by default.
Movement on replace-Hibernate front. Craig Russell has put together some proposals for implementing both JPA and JDO backends for Roller -- so that we can eventually replace our dependency on Hibernate. We nominated him for committer status to make it easier for him to contribute, but the voting process is still dragging on.
Multi-side patch contribution A Norwegian company LinPro has submitted a large patch for mutli-site blogging. It looks like a very interesting and valuable new feature but thus far nobody has had time to evaluate the code.
Community building efforts. Dave Johnson presented a talk on Roller at ApacheCon EU 2006, designed to inspire and educate new users, developers and contributors. The talk was well attended. Dave will present a similar talk, but completely updated for Roller 3.0 at ApacheCon US 2006.
The OpenEJB project has begun it's migration into the Incubator. Primary activities are setting up infrastructure and establishing a list of active committers. Items completed so far:
- Status page created and published to Incubator website
- Lists established and in active use
- Most CLAs are in, more coming
- Account created for Daniel Haischt
XAP made good progress since June 2006 status report. The main activities and results are:
Discussed and gathered community feedback from both XAP dev list as well as general incubator dev list about IRC meetings. As a result, decided not to pursue general IRC activites unless specific requirements are met (The content of IRC is to be limited to educational purpose only; some committers are willing to volunteer to provide education and orientation and Q&A);
- Continues to update the project with bug fixes, samples, web site fixes, etc;
- Discussed at the XAP dev email list and made decisions to focus more on the Dojo toolkit;