|Deletions are marked like this.||Additions are marked like this.|
|Line 87:||Line 87:|
|(project add text here)||Chukwa is a distributed log collection and processing system built on top of Hadoop.
It is a former Hadoop subproject. Bill Graham has officially granted committer access. Jiaqi Tan has accepted invitation of becoming Chukwa commiter, and pending infrastructure to setup committer access. Chukwa mailing lists have been moved into incubator.apache.org.
Chukwa 0.5 is in the process of migrating data storage layer to HBase for faster read/write random access. Chukwa Agent has been improved with new REST API for controlling Chukwa Agent operations.
|Line 128:||Line 131:|
|a discusion regarding how to continue with the project. Etch has definitely||a discussion regarding how to continue with the project. Etch has definitely|
|Line 147:||Line 150:|
|Note from Martijn Dashorst:||Note from Martijn Dashorst (Niclas Hedhman concurs):|
|Line 151:||Line 154:|
|Signed off by mentor: dashorst||Signed off by mentor: dashorst niclas|
September 2010 Board reports (see ReportingSchedule).
These reports are due here by Wednesday, 8 September 2010 so that the Incubator PMC can relay them to the board.
Your project might need to report even if it is not listed below, please check your own reporting schedule or exceptions.
Please remember to include:
- The "incubating since" info.
- The project's top 2 or 3 things to resolve prior to graduation.
- A short description of what your project's software does.
The Signed off by mentor: is for Mentor(s) to show that the Report has been reviewed.
= Aries = Aries will deliver a set of pluggable Java components enabling an enterprise OSGi application programming model. Aries entered incubation on September 22, 2009. There are currently no issues requiring IPMC or Board attention. The following sub-components are actively being developed: * Application * Subsystems * Blueprint * JPA * JNDI * Transaction * Quiesce * Samples There continues to be a vibrant community as shown by the activity on the mailing list this year. We have recently completed our 0.2-incubating release. This is our second release since entering incubation. This release is in support of Geronimo 3.0 which uses Apache Aries. The OSGi Enterprise Compliance Tests have been run against Blueprint, JMX, JNDI and transactions modules and the results have been published to the aries-dev mailing list and are available from the Aries web site Top 2 or 3 things to resolve before graduation: * Build community [done] * Create a release [done] * Address project scope concerns raised during acceptance vote Signed off by mentor: kevan = BeanValidation = Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * First release of artifacts - Done * Grow the community and committer base - ongoing * Decide on graduation target of TLP or subproject - TBD Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? * None at this time. How has the community developed since the last report? * New committer Matt Benson has started working on a branch to upgrade to commons-lang v3. How has the project developed since the last report? * 0.2-incubating was released on August 20th. Signed off by mentor: kevan = Bluesky = BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. The Summer vacation ranges from July-September, a brand new semester has begun, meanwhile some developers graduated and some fresh developers come. We used to develop RealClass with Anjuta which generates many useless files both hard to maintain and probably voilate ASL. I've convey my opinion in dev list and tried to transplant Tserver to QT, and it works and cost me little time. Some of the developers are also interesting in it, we will discuss the next step in dev mailing list. *transplant Tserver's interface from GTK to QT; *Test QT version Tserver and found out it works well; next step: * Discuss starting a branch of transplanting RealClass on dev mailing list. * Gradually transplant and commit source code. Signed off by mentor: = Chukwa = Chukwa is a distributed log collection and processing system built on top of Hadoop. It is a former Hadoop subproject. Bill Graham has officially granted committer access. Jiaqi Tan has accepted invitation of becoming Chukwa commiter, and pending infrastructure to setup committer access. Chukwa mailing lists have been moved into incubator.apache.org. Chukwa 0.5 is in the process of migrating data storage layer to HBase for faster read/write random access. Chukwa Agent has been improved with new REST API for controlling Chukwa Agent operations. Signed off by mentor: = ESME = Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * A new committer - Imtiaz Ahmed H E - has joined the team * Final preparations for Release 1.1 with 77 completed JIRA issues! * Planning for Release 1.2 The following items are planned for the next reporting period: * Completion of Release 1.1 * Development work on Release 1.2 Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project * Another Apache release Signed off by mentor: bdelacretaz, dkulp = Etch = Preliminary board report for Etch due to being late: Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. The activity in the Etch project was very low in the last months. This led to a discussion regarding how to continue with the project. Etch has definitely suffered from the fact that Etch's initial committer team at Cisco was dismantled. This summer the project got its first non-ex-Cisco committers. The mentioned discussion showed the will of some of the committers to drive the project more actively. We want to publish release 1.1 during the next report period. Technically the release package should be ready. A discussion on whether to include the new C binding in this release or the next one has been started. This project definitely needs more drive and more action from the committers to become a viable Apache incubator project. We are willing to do more to make it an active project again. Top issues currently are: * publish release 1.1 * update the web site and documentation * setup a build server on apache's hudson * task planning for release 1.2 Note from Martijn Dashorst (Niclas Hedhman concurs): The mentors proposed to stop the incubation of Etch due of lack of community momentum. The actions put forward by the new committers give some hope that Etch might have a future, so we are going see if the community gains some momentum. As a technology Etch is viable, as evidenced by its use in BMW and other production sites. Our concerns are mostly that the developer community has been dead for over a year with just one (large) commit. Last week did show increased activity, we're going to see if this continues to increase and a viable community arises. Signed off by mentor: dashorst niclas = Hama = Hama was accepted into Incubator on 20 May 2008. Hama is a distributed scientific package on Hadoop for massive matrix and graph data. Recent Activity: * We designed the User-Interface primarily for BSP programming. * We made a Job Client, Job Manage System for BSP computing framework. Currently, it works on local system, but we're working hard for distributed system. * We made an BSP examples, e.g., Pi Estimator, Serialize Printing The following is planned for next reporting period: * We'll freeze the features and release a beta when all issues for 0.2 version are fixed. Before this project can graduate we need to encourage more participation in the project and grow the community. Signed off by mentor: brett = Kato = Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * While Oracle has expressed a continued interest in the JSR-326, there has been no change in the podling's status since the last report in June. * As in June, the project is effectively paused until Oracle's involvement in the Kato podling has been clarified. The credibility of the standard relies on there being more than one major Java VM vendor involved. The following is planned for next reporting period: * To be determined once Oracle's involvement has been established. Before this project can graduate we need to encourage more participation in the project and grow the community. Signed off by mentor: ant rdonkin = Lucene Connector Framework = === Description === Apache Connectors Framework is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. Apache Connectors Framework also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. Apache Connectors Framework has been in incubation since January, 2010. It has recently been moved from a planned subproject of Lucene to a planned top-level project. === A list of the three most important issues to address in the move towards graduation === 1. A final top-level-appropriate name choice for the project needs to be confirmed 1. Nightly builds and javadoc need to be set up, and a release process needs to be defined 1. The first official release needs to be executed === Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? === 1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web connectors properly. === How has the community developed since the last report? === We have had quite a lot of use of the software from most areas of the world, and offers of contribution of connectors as well. ACF now has several regular contributors, in addition to its dedicated user base. The name changes we are undergoing will likely inconvenience many of these users, which is why this is a critical issue to resolve promptly. A book is also planned and will be written over the next nine months. === How has the project developed since the last report? === Plans for a first release have been executed almost completely. Better tests have been added, although not for proprietary connectors. An API has been added to aid integration support. Tree reorganization has taken place to assist with Maven integration. Online end-user documentation is complete. A quick-start example, based on Jetty and Derby, has been written and should assist novice users in getting set up quickly. Signed off by mentor: Grant Ingersoll = Lucy = Lucy will be a loose port of the Lucene search engine library, written in C and targeted at dynamic language users. Lucy was voted into the Incubator on July 22, 2010. Issues for Incubator PMC or ASF Board: * There are some potential licensing issues that are currently being clarified with legal-internal. The results will have an impact on the starting code base for Lucy and ultimately a significant impact on the podling's momentum. These issues should be closely watched. Progress since the last report: * Mailing lists created * Initial Website created: http://incubator.apache.org/lucy/ * Audit of existing KinoSearch code base for Software Grant has begun. * Legal issues regarding usage of Perl C API header files provisionally resolved (LEGAL-79). Signed off by mentor: mattmann, hossman, upayavira = NPanday = NPanday allows projects using the .NET framework to be built with Apache Maven. NPanday allows .NET projects to be converted into Maven projects thus allowing them to fully utilize the other technologies driven by Maven. NPanday has been incubating since August, 2010. The development of NPanday has not yet started in Apache since we are still waiting for the Infrastructure to be fully setup. We still need to finish our importing of the source code from codeplex as well as the information from the issue tracker. There has been a continuous discussion for the plans of NPanday 2.0, some of the major tasks consist of support for .NET 4.0 and VS2010. NPanday Infrastructure Established: * Established mailing lists NPanday questions; firstname.lastname@example.org (subscribe by posting to email@example.com) NPanday development; firstname.lastname@example.org (subscribe by posting to email@example.com) NPanday commits; firstname.lastname@example.org (subscribe by posting to email@example.com) * Established the committer accounts for the committers from codeplex There are no issues for the Incubator PMC or board at this time. Signed off by mentor: = Nuvem = Apache Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. Nuvem was accepted for Incubation on June, 2010. The Nuvem Project is slowly getting started. The project will be featured at a JavaOne 2010 Session (all demos will be from Apache Nuvem) S314011 - Developing composite applications for the Cloud using Apache Tuscany Mark Little wrote an article about the Nuvem project and how it might relate with libCloud and Deltacloud. http://www.infoq.com/news/2010/08/apache-nuvem Signed off by mentor: = OODT = OODT is a grid middleware framework for science data processing, information integration, and retrieval. OODT is used on a number of successful projects at NASA's Jet Propulsion Laboratory/California Institute of Technology, and many other research institutions and universities. A list of the three most important issues to address in the move towards graduation 1. Port OODT code and license headers into ASF license headers 2. OODT contributions from at least 2 other organizations besides JPL 3. At least one OODT incubating release, hopefully in the first few months Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? The OODT community voted in a new committer, Cameron Goodale on July 15, 2010. There have been several contributions from individuals from other organizations, notably the contribution of OODT@Apache logos in OODT-17 by Paul Vee from CHLA, the work on OODT XMLPS from David Kale of CHLA in OODT-29, as well as use cases contributed by Dr. Bruce Barkstrom (in OODT-28). We've also had some more JPL'ers join the mailing lists (Paul Zimdars), as well as another NASA contributor, Mark Foshee from Marshall Space Flight Center. Dan Crichton has been invited to give a keynote at ApacheCon NA. How has the project developed since the last report? OODT was voted into the Incubator by the IPMC on January 22, 2010. Development has progressed at a rapid pace. Chris has input 2 releases into JIRA (0.1-incubating and 0.2-incubating), and currently 18 of the 23 issues scheduled for 0.1-incubating have been completed. Of the remaining 5, 2 of the issues (OODT-3 and OODT-15) are basically finished. OODT-29 (reported by David Kale from CHLA) proposes to contribute a configurable XML product/profile server add on to web-grid (which was imported in OODT-27 by Chris Mattmann) based on Chris Mattmann's existing handler being deployed at CHLA, originally developed on the EDRN project. The remaining 2 issues both involve cleaning up license dependencies (one for the pushpull component in OODT-22 and another for clearing the profile/product server dependency on jacorb in OODT-25). We are *this close* to wrapping up the 0.1-incubating release. We even have a release manager: David Woollard has volunteered to push out the release, with guidance from Chris Mattmann. Probably the most visible development to report is that OODT@Apache now has an official website! http://incubator.apache.org/oodt/. Sean Kelly led the way, with contributions from Chris Mattmann and Andrew Hart and Paul Vee in OODT-16/OODT-17. Signed off by mentor: mattmann, jerenkrantz = RAT = RAT is a Java library that scans files for known licenses and reports files that lack any of them. Three frontends to said library exist in form of a command line client, an Ant task and a Maven plugin. RAT entered the Incubator in January 2008. RAT 0.7 incubating has been released at June 30th. After the release of RAT 0.7 a discussion of what a matching graduation target for RAT could be started. It seems that most users of RAT think a TLP would be the best fit. Development activity on RAT is very low, a total of six people have commited 59 changes in 2010 - only two people performed more than five commits. At least twenty of the total commits were due to the release process of 0.7. Hyrum Wright is working on a Python based reimplementation of RAT's ideas under the name Mouse inside a lab http://svn.apache.org/repos/asf/labs/mouse/ Signed off by mentor: = River = Apache River is a distributed computing architecture, based on the JSK Starter Kit Source code donated by Sun Microsystems, for the Jini Specification. While generally referred to as a Service Architecture, it might be more easily explained to those familiar with Dependency Injection as a Protocol Independent, Distributed Dependency Injection Architecture, suited to both hardware and software. Instead of depending on Protocols directly for communication, everything is abstracted behind a Java interface, allowing protocols and implementations to be swapped freely, programming languages other than Java can also participate. River has been appointed an additional mentor and has seen much increased activity on the mailing list in recent weeks and months. The next release 2.2.0 is scheduled for December, although some discussion on whether this is a major release or not continues. The Incubator PMC and Apache River PPMC have approved one new committer for the project, the votes passed in August. Current development efforts are still focused on a java.security.Policy Provider with the following features: * Dynamic Grants at Runtime, based on CodeSource, Code Signer Certificate chains , ProtectionDomain or ClassLoader. * Dynamic Revoke of Grant's at Runtime Reviewing newly donated code updates and patches, including: * New CodebaseAccessClassLoader and associated changes * New StreamServiceRegistrar Interface and other additions * New ConcurrentDyamicPolicyProvider Additionally: * Work is being performed on TaskManager by our newest committer * Increasing the test coverage, build process and Ant vs Maven work is ongoing * Entry-level documentation is starting to appear We are experiencing increasing interest on our developer mailing list. 3 most important issues: 1. Code review and acceptance of newly submitted patches. 1. Streamline the build and test process. 1. Get our new committer svn accounts set up and grow our developer pool. Signed off by mentor: Benson Margulies, Niclas Hedhman