incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject December 2011 Incubator Board Report
Date Fri, 16 Dec 2011 05:55:43 GMT
We've all been aware that the Incubator has been growing more than
graduating, over the years.  Last month, Sam started a discussion regarding
being more proactive and pushing projects out of the nest, basically one way
or another, after a year.  A real issue is pushing out those really ready to
graduate, and doing the garbage collection on those that are already dead
(and may have even voted to terminate).  In-between are those projects that
are struggling to achieve critical mass, but are active with who they do
have involved.  The response from mentors of various projects was quite
encouraging, both in specifics and in concept, and hopefully we'll start to
see a wave of TLP requests, following ACE, Bean Validation, and Empire-DB.

Meanwhile, Apache DeltaSpike -- a collection of JSR-299 (CDI) Extensions for
building applications on the Java SE and EE platforms -- was voted for

There has also been excellent discussion about pruning and clarifying
Incubation rules and process, to be more streamlined and minimal.

With respect to the monthly board report, since the last report (and since
the schedule change), we've changed how reminders are processed, and hope to
be well on the way to cleaning up the problem where the wrong projects were
listed and reminded.  There were still a few glitches for this month, but
hopefully they're resolved for next.  Brett Porter, Dave Crossley,
Upayavira, Jim, and others have contributed to the efforts, and are well
deserving of continued thanks.

Even so, and despite an extra day and reminder, neither HISE nor KATA
reported.  Wave did take advantage of the time to report.


Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Community Development:
* active discussion on mailing lists and on JIRA tickets
* three new contributors have submitted patches this month
* logo voted upon

Project Development:
* made progress towards releasing 1.3.5 (now on candidate 10)
* incorporated lessons from failed release candidates into redesign of
release process for trunk
* fixed bugs / tested code / added documentation


Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

 * Incubating since 30 August 2011.
 * Picked CTR instead of RTC.
 * Development proceeding actively. (129 jiras fixed so far, 15k of java)
 * Should have first end to end test working soon.

Issues that must be addressed before graduation are:
 * Making a release
 * Attracting users and developers
 * Increase diversity of developers outside of Hortonworks


Amber has been incubating since July 2010. Amber is a project to develop a
Java library which provides an API specification for, and an unconditionally
compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications.
OAuth is a mechanism that allows users to authenticate and authorise access
by another party to resources they control while avoiding the need to share
their username and password credentials.

The most important issues that must be addressed before graduation are:

 - Clarify status of code grant
 - Attract users and developers
 - Generate a release

The Incubator PMC / ASF Board should be aware that:

 - Community activity is relatively low
 - We need copyright signoff from University of Newcastle

How has the community developed since the last report

 - New users / devs show up on the mailing lists both contributing patches
and asking for guidance/release

How has the project developed since the last report

 - The old trunk has been moved to a branch amber-0.10 which reflects OAuth
0.10 spec
 - The new trunk is being updated to latest 0.22 spec version
 - Versions of artifacts have been aligned to the supported OAuth
specification supported
 - Discussion about preparing for an initial release is ongoing


Any23 is defined as a Java library, a Web service and a set of command line
tools to extract and validate structured data in RDF format from a variety
of Web documents and markup formats. Any23 is what it is informally named an
RDF Distiller.

A list of the three most important issues to address in the move towards

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need
to be aware of?

Yes, there has been ongoing work to bring the Any23 codebase to Apache SVN.
The final stages include loading the code dump to the Apache test repos,
there will then be a short time for the dev/committer team to review it,
before loading it to the real repos. A time frame for this has been set at
around a week.

How has the community developed since the last report?

Since our last report there have been no new committers. Development has
also not been tremendously active however when the code migration finally
completes this should improve.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

As the code import has not yet been finalized, most of the project activity
has been off-site, this includes changes to the codebase. There has been
some interest from the Apache Nutch community to get an Any23/Nutch plugin
operational, for details see NUTCH-1129. In addition there is now a healthy
Jenkins nightly CI build running for the project. Issues in the short term
are to discuss Paolo Castagna's points regarding the integration of more of
the 'semantic web' projects which exist at Apache.


Bean Validation was accepted into Incubator on 1 March 2010.

The Bean Validation project is an implementation of the Java EE Bean
Validation JSR303 specification.

There are no other important issues open before a possible graduation.
The project has agreed to seek status as a TLP, and has agreed by an
vote on its readiness to graduate [1].  The primary task outstanding is the
completion of a charter.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware

 * none

How has the community developed since the last report

 * Mailing list and JIRA activity are extremely quiet.  We attribute this
to the nature of the podling, being but an implementation of a
and the level of achievement of conformity to that specification.

How has the project developed since the last report

 * we have upgraded to and continue to pass the latest available version of
the JSR303 TCK.
 * we continue to track the progress of the JSR303 spec for the future.



Bigtop is a project for the development of native packaging and stack
tests of the Hadoop ecosystem.

Bigtop entered incubation on June 20, 2011.

Primary issues blocking graduation:
* Need for increased diversity and additional committers.

Issues which Incubator PMC and/or ASF Board might need/wish to be aware of:
* Due to limitations in available platforms on Apache Jenkins
infrastructure and need for VM spin-up/spin-down for tests, we are
working directly with OSUOSL on build/test setup.

Community development since last report:
* Community meetup held Nov 8th, with mentors and committers alike
* Gave talks on Bigtop @ApacheCON 2011
* Bigtop was on the agenda of the HBase meetup on Nov 29th.
* Started a regular Bay Area Bigtop meetup/class:

Project development since last report:
* 0.2.0-incubating released
* Added deployment code (puppet) to the project
* Work on the Bigtop stack based on Hadoop 0.22 has started
* Work on the Bigtop stack based on Hadoop 0.23 has started
* Used Bigtop to validate Zookeeper 3.3.4 and 3.4.0 releases
* Used Bigtop to validate HBase 0.92 RC
* Used Bigtop to validate Hadoop 0.22 RC and Hadoop 0.23 release
* Additional component project (Mahout) added.
* Supported platforms voted on.
* Next release of Bigtop has been voted on
* Increased the # and scope of integration tests


Project Status

Infrastructure migration still underway; the only major sticking point is
that GIT is crucially important for our community and workflow. Additionally
we have voted to rename the project to "Cordova".

We are contributing to the CouchDB project documentation that descibes use
and, more importantly, the cutting of Apache releases from Git
infrastructure. Our goal is to bring our project to that infrastructure, and
we recognize its our resonsability to ensure the goals of legal and
community at Apache do not suffer for it.

A request to participate in the Git alpha testing has been made to
infrastructure. All mentors supported this request.

The name "Callback" was suboptimal for findability, and worse, authored
documentation relating to the JavaScript interfaces found in the project.
Cordova was the street of the old Nitobi office wherein the PhoneGap project
was conceived and has some community precident in another related tooling
project. Discussion was positive, and the vote nearly unanamious. We now
need to address infra to engage the rename work (and probably send em a
bottle in thanks for being a pain the ass).


* Community is growing with documentation traffic, and downloads, up.
* The mailing list has been super active with new community members.
* Jira embraced however we are still getting issues logged on Github.
Committers are using Github as a funnel to capture issues, still, and
manually moving them to Jira once vetted.
* Renaming needs to be promoted.

Community Objectives

* Migrate to the name Cordova and update the community appropriately.
* Continue to assist in documentation effort for CouchDB use of Git.


* 1.2.x, Oct 31


* 1.3.x, Dec 12 (this will not be an Apache release)
* 1.4.x, Jan 30
* 1.5.x, Feb 27
* 1.6.x, Mar 26
* 1.7.x, Apr 30
* 1.8.x, May 28
* 1.9.x, Jun 25
* 2.0.x, Jul 30


Chukwa is an open source data collection system for monitoring large
distributed systems. Chukwa is built on top of the Hadoop Distributed File
System (HDFS), HBase and Map/Reduce framework and inherits Hadoop's
scalability and robustness. Chukwa also includes a ?exible and powerful
toolkit for displaying, monitoring and analyzing results to make the best
use of the collected data.

* Completed migration to use HBase as data storage
* Updated documents for architecture, programming guide and quick start
* Preparing for Chukwa 0.5.0 release
* Migrated from ant build system to maven build system to reduce site
deployment overhead.

Chukwa depends on Apache Hadoop. More specifically, it requires a
stable version of Hadoop that supports append/sync. Since joining the
incubator, we have been unable to roll a release because these
requirements were not met. Now that there is a stable version of
Hadoop that supports the features we require, we expect to roll a
release presently, attract contributors, and set the project back on
track for graduation.


(incubating since Dezember 2011)

DeltaSpike will consist of a number of portable CDI extensions that provide
useful features for Java application developers. The goal of DeltaSpike is
to create a de-facto standard of CDI-Extensions that is developed and
maintained by the community.

There are currently no issues requiring IPMC or Board attention.

Since DeltaSpike entered incubation on December 7, 2011, we have
accomplished the following:

1. Setup of mailing-lists and confluence Wiki space.
2. Setup of JIRA project
3. Started initial discussions
4. Assist GIT documentation for CouchDB and other GIT users (like ourself).

Upcoming major goals:

1. Finish setup (e.g. GIT repository)

Top 2 or 3 things to resolve before graduation:
1. Build community
2. Create at least one release
3. Create Documentation


(incubating since October 2011)

Apache DirectMemory is a multi layered cache implementation featuring
off-heap memory management (a-la BigMemory) to enable efficient
handling of a large number of java objects without affecting jvm
garbage collection performance.

A list of the three most important issues to address in the move
towards graduation.
1) Ensure branding requirements are met (still to be worked out)
2) Ensuring IP is cleared (closed: all initial code has committed by
Raffaele Guidi, which has completed the IP clearance and donation process)
3) Understanding process/decision making guidelines (new committer process
is ok, release process still yet to be worked out)

Any issues that the Incubator PMC or ASF Board might wish/need to be aware

- We lost one mentor (still not too bad, we have others but we will miss

How has the community developed since the last report

- Two more people have asked for inclusion in the team as committers up on
the mailing lists
- Tasks and proposals contributed by non-committers

How has the project developed since the last report.

- Healthy activity on 3rd parties integrations such as Apache Karaf
(complete with an ad-hoc module) and Apache Commons JCS (still in progress
with help from the JCS team)


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.

- We did some progress to implement the Etch binding-cpp runtime. Basic
framework parts like the OS abstraction layer, collection types, runtime
components are already done.
- The initial content for the new Apache Etch website has been completed and we plan to do
the transition while the next few days (voting has still to be done).
Technical Etch documentation will be converted afterwards (Docbook PDF and
- We fixed some bugs in the C, Java and C# bindings
- All issues for our next release are resolved and we started to prepare the
release packaging and voting process
- Open issues towards graduation were identified and we started a discussion
on our mailing list about this
- The new PPMC and Committer Martin Veith could be acquired

future tasks:
- Bug fixing
- Technical documentation in the Docbook format
- Further development on the binding-cpp
- Community development
- Solve open issues towards graduation


Apache Flume is a distributed, reliable, and available system for
efficiently collecting, aggregating, and moving large amounts of log data to
scalable data storage systems such as Apache Hadoop's HDFS.

Flume entered incubation on June 12th, 2011.

=== Progress since last report  ===

 * Flume trademark inquiry has been resolved. Flume will retain its name as
an Apache project.
 * Flume PPMC voted in two new committers - Prasad Mujumdar and Mingjie Lai
 * Active development is going on in FLUME-728 branch.
  * FLUME-728 branch has gone through two milestones - "NG alpha 1" and "NG
alpha 2". A total of 50 issues have been fixed in these two milestone.
  * A release is being planned for 1.0.0-alpha-1 based on this branch.
 * An inaugural Flume Meetup was held in New York on November 9, 2011 which
was attended by 40 users and developers.

=== Issues before graduation ===

 * Create Flume web site.
 * Make an incubating release.
 * Grow the community size and diversity.


Gora is an ORM framework for column stores such as Apache HBase and Apache
Cassandra with a specific focus on Hadoop.

A list of the three most important issues to address in the move towards

   1. Fix failing module tests within the Jenkins CI build
   2. Update both project site and wiki documentation with specific emphasis
on Hbase, Cassandra and SQL modules as well as the release process
   3. Write tests for Cassandra module as this would provide an additional
layer of consistency to the project. This is fundamental before a
0.2-incubating release.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware

   1. The Gora PPMC recently voted to extend an invitation to Ferdy Galema,
he has however noted that he is on holiday and will not be able to accept
until his return.
   2. The community plans a 0.2-incubating release soon, and it will likely
coincide with the graduation VOTE that Chris Mattmann, champion for Gora,
will put forth.

How has the community developed since the last report?

With the addition of Ferdy Galema, as stated above there has also been
interest from one of Ferdy's colleagues and additionally Keith Turner who is
working on the Accumulo (Apache Incubator) project. Keith's intention is to
build a gora-accumulo store which would add significantly to Gora.

The project is currently VOTE'ing on its graduation, at this thread: So far community response looks good. If the VOTE
passes, we'll head over to general@incubator
and raise the VOTE there. If all is well on that VOTE, we're targetting a
January 2012 resolution to the board.

How has the project developed since the last report?

Gora was voted into the Incubator by the IPMC on September 26, 2010.

Gora 0.1.1-incubating was successfully released on 24 September 2011 which
displays that the project has made 2 releases since entering the incubator.
Additionally a Jenkins CI build has been established and work is on way to
firstly fix the broken tests, before working to improve overall code test
coverage. In particular the modular nature of the project meant that
developers have decided that a Maven build was more appropriate than an
Ant/Ivy implementation.


Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
computing framework based on BSP (Bulk Synchronous Parallel) computing
techniques for massive scientific computations.

== Top 2 or 3 things to resolve prior to graduation ==

 * Grow the community size.

== Issues for the Incubator PMC or ASF Board ==


== Community development ==

 * Increased committers divergence.
 * Accounts were created for two new committers.

== Project development ==

 * Many new features (Counters, Combiners, I/O interface, YARN module) are
 * Some bug and performance issues are fixed.


HCatalog is a table and storage management service for data created using
Apache Hadoop.

The most important issues in moving the project to graduation are expanding
the community of developers.

Since the last report we have:
* We have made our first release from incubator.
* Continued feature development, adding two major new features (added a new
datatype binary and hbase integration).
* Added a new committer Francis Liu (Yahoo!)

Currently there are 75 subscribers to the user list and 70 on the dev list.
There were 60 and 59 respectively last report (September 2011).

Signed off by mentor: gates




Isis is an ALv2 licensed implementation of the Naked Objects pattern. It is
based on contributions of the original Naked Objects Framework along with a
number of sister projects that were developed for the book "Domain Driven
Design using Naked Objects " (pragprog 2009).

Isis was accepted into the Incubator in 2011, September 7th.

Project Development

* Ongoing work on new json viewer, implementing the spec
* Enhancements to sql object store
* Enhancements to core (metamodel, support for multiple viewers in single

Community Development

* the work on json viewer has brought spawned an independent open source
* Reasonably active mailing list; first "real" problem/change request raised
(and fixed)
* Presented lightning talk at CodeKen 2011 conf.
* Reworking site to improve the messaging (to go live in next relesae)
* To support the new site, an example online app demonstrating Isis is now
live at

Top 3 Issues to address in move towards graduation

* Improve the "marketing message" to bring in more users
  * see mailing list thread about this
* Make Isis more accessible
  * online demo, better archetype
* More orchestrated blogging/publicity from existing community
  * (initial guidelines in the Isis wiki,

None of these issues requires Board attention.

New Releases

* Next release expected this month (Dec 2011)


Apache Kalumet is a complete platform to administrate
data center. It covers the operating system tasks,
middleware provisioning, etc.
Kalumet entered incubation in September 2011.

Community Developement:
The Kalumet community has been setup.
Several discussions introducing Kalumet have been made
during ApacheCon.

Project Development:
The codebase has been turn to be Apache compliant, including
renaming of the package name to org.apache.kalumet, update
of the comments, update of README, NOTICE, etc files.

The trunk is now operational and some tasks are in progress (
add support of JBoss 6/7, improvement on the VFS file manipulator,

Some cleanup on the "old" codebase have to be done, especially

Web Site/Communication Development:
The Kalumet community voted a logo:

The website creation is in progress (firstly using Confluence Wiki
and Maven site plugin).

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
None so far.

Signed off by mentor: jbonofre, olamy



Lucene.NET (We missed our Nov report, so we are reporting for Dec)

Lucene.Net was accepted into the Apache Incubator in February 2011.
Originally it was a sub project of the Lucene Project.

Lucene.Net is a port of the Lucene search engine library, written in C# and
targeted at .NET runtime users. Lucene.Net has three primary goals:
* Maintain the existing line-by-line port from Java to C#, fully automating
and commoditizing the process such that the project can easily synchronize
with the Java Lucene release schedule.
* High-performance C# search engine library.
* Maximize usability and power when used within the .NET runtime. To that
end, it will present a highly idiomatic, carefully tailored API that takes
advantage of many of the special features of the .NET runtime.

Recent Activity:

* Lucene.Net 2.9.4 was officially released Nov 29th, 2011
* Build scripts were created
* New incubator website utilizing the Logo from the StackOverflow contest

Current Activities:

* Preparing Lucene.Net 2.9.4g (Generics version of 2.9.4) for release in
* Began porting Java Lucene 3.0.3
* Began porting Java Lucene 4.0

Long term goals:

* Have a nearly fully automated process to convert Java Lucene to C#. (This
has been a goal, but we are discussing if this is truely the best idea of
the project)
* Release Lucene.Net 3.0.3 (port of Java Lucene 3.0.3)
* Have a new .NET version of Lucene utilizing .NET constructs and idioms

Graduation thought:

* One of the mentors (Stefan Bodewig) has indicated he wants to start
pushing for graduation.



ManifoldCF 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 repository
connectors includes Documentum (EMC), FileNet (IBM), LiveLink
(OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS
file systems, CMIS repositories, RSS feeds, and web content. Output
support includes Solr, MetaCarta GTS, and OpenSearchServer.
ManifoldCF 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.

ManifoldCF has been in incubation since January, 2010. It was
originally a planned subproject of Lucene but is now a likely
top-level project.

--A list of the three most important issues to address in the move
towards graduation--

1. We need at least one additional active committer, as well as
additional users and repeat contributors
2. We need the current committer base to each broaden their commits
to new areas of the project
3. We'd like to see long-term contributions for project testing,
especially infrastructure access

--Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
be aware of?--

All issues have been addressed to our satisfaction at this time.

--How has the community developed since the last report?--

Talks on ManifoldCF were given both at Apache Eurocon 2011 in
Barcelona and at ApacheCon NA in Vancouver.  Both were well-received.
We have not signed up any new committers, however, this quarter,
although we've received interest from people towards contributing
especially in Vancouver.

Based on the feelings of our mentors, we have postponed further talk
of graduation, due to the still-not-well-distributed number of commits
among our committer base.

--How has the project developed since the last report?--

An 0.1 release was made on January 31, 2011, and a 0.2 release
occurred on May 17, 2011.  Another release occurred on September
20, 2011.  A fourth release is planned for December 15, 2011, and will
significant new features, including full support for HSQLDB and a new
Alfresco connector.


MRUnit - a library to support unit testing of Hadoop MapReduce jobs.

MRUnit entered incubation on March 8th, 2011.

* Still looking to develop a broader community.
* Contribution document rough draft completed.
* Release document draft created and used.
* Release 0.5.0-incubating has been announced.

Issues before graduation
* Grow the community size and diversity
* Make another incubating release

Licensing and other issues
* none - MRUnit was originally a subproject of Hadoop


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.

We are now in the process of releasing NPanday-1.4.1-incubating and at the
same time developing NPanday-1.5.0-incubating, which will come with azure-
and silverlight support as well as quite extensive core refactorings
removing historical burden.

We are also happy to report that our community continues to gain new people
in terms of patch contributors and reporters on issues.

The top priorities towards graduation are:

* regular release
* guide regular patch contributors towards becoming committers
* improve engagement of existing committers

There are no issues for the Incubator PMC or board at this time.

Signed off by mentor: Dennis Lundberg (dennisl)


 * Openmeetings is a free browser-based software that allows you to set up
instantly a conference on the web.

 * A list of the three most important issues to address in the move towards
graduation are:
    1) Migrating infrastructure
    2) Code Audit (Apache RAT is now integrated which should help us)
    3) Packaging first incubator release

 * A question for PMC: Should we start a demo server on Apache, so people
can benefit from communication?

 * Community status: 1 contributor joined, talked to the open source task
management system on integration.

 * We shipped a pre-release bundle 1.9.0, see release notes:


# OpenOffice (was

* OpenOffice entered incubation 2011-06-13.

OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms.  Its localizations support 110
languages worldwide.

* Most Important To Address:

1) Completion of the IP-review portions of the incubation checklist

2) A Successful Podling Release

3) Increase size and diversity of the active development community

* Issues for IPMC or ASF Board Awareness


* Community Development Progress

Since our last report we have voted in 11 new Committers.

We have created a new ooo-marketing list.

We voted to change the name of the product from to Apache

The volunteers of the legacy user support forums have joined
the project and their forums are now hosted by Apache.

With assist from legal-discuss (special thanks to rdonkin and rubys) we now
have a much better idea of the license and notice requirements of source and
binary releases.

* Project Development Progress

Dev focus has been on IP review and replacement of copyleft dependencies.

Buildbot now doing nightly Linux builds.  Windows is in-progress.

Working on final pieces of infrastructure migration.

Working on notification of users for shutdown of email


A suite of tools focusing on the comprehension and auditing of
software distributions. Entered incubation 2008-01-06

 * Added David Blevins as a new committer.
 * Various new people are making contributions.
 * Issue tracker and mail lists are attended to.

 * 15 November 2011 - apache-rat-incubating-0.8 released.
 * Improved the download facility.
 * Initial contributions of a new tool, Tentacles, to download all the
 archives from a staging repo, unpack them and create a little report of
 what is there.
 * Commenced improvement of branding.

Current and next steps:
 * In process of choosing a suitable project name.
 * In process of deciding project scope and description.
 * Commenced the search for a project chair.

Issues before graduation:
 None. We seem to be getting there.

Apache Rave is a new web and social mashup engine. It will provide an
out-of-the-box as well as an extendible lightweight Java platform to host,
serve and aggregate (Open)Social Gadgets, W3C Widgets and services through a
highly customizable and Web 2.0 friendly front-end.

Rave entered incubation on 2011-03-01.

Current Status:
  * Releases
     * Two additional releases (0.4-incubating & 0.5-incubating) have been
released since the last report
     * A 0.6-incubating release is currently being voted on on the dev list
  * Community Growth
     * Rave committers & PPMC members have attended multiple events to meet
and engage additional community members
     * The ApacheCon Rave meetup & hackathon were well attended
     * The Rave community is actively engaging projects that are building on
or leveraging Rave
     * Jasha Joachimsthal was voted in as a new PPMC member in November
     * Sean Cooper was voted in as a new committer and PPMC member in
     * Dev mailing list is saw increased traffic from new users/contributors
     * A community request (Sakai project) for a git mirror was honored:
Rave is now also available from
  * General
    * A preliminary integration with Apache Wookie is now provided with the
0.6-incubation release (pending), full integration (bundling Wookie) is
slated for the next release
    * The commit rate remains high (~75 commits / month)
    * Website documentation is steadily improved and extended
    * A presentation about Rave, focusing on Apache, community and
collaboration, was given by Matt Franklin and Ate Douma at ApacheCon 2011
November 11th
Next steps:
  * Continue to build up awareness of Rave and grow the community
  * Further collaboration and coordination with Shindig and Wookie
  * Further modularize Rave to support extending and customizing for end
  * Keep up the pace for the monthly release schedule, working towards a
0.7-incubating release by end December 2011

Issues before graduation:
  * Complete 1.0 release
  * Expand the community/user base


S4 (Simple Scalable Streaming System) is a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data.

S4 entered incubation on September 26th 2011.

* Infrastructure issues
- we are waiting for an answer to our proposal for using an apache git
repository instead of converting our existing code base from git to svn.
This proposal was in response to a call by the infra team for joining
the git testing program.
- we have a volunteer to help with the Python scripts required to be able
participate in the git testing program. His name is Ajaybabu Kalangi.

* Other issues before graduation
 1. Migrate code from github to Apache infrastructure and make an
initial release on Apache with the current code (version 0.4 = version
0.3 + checkpointing + bugfixes)

2. learning and applying Apache's procedures (consensus), and
defining/adapting development workflows for the project

3. Complete the current work on the new version (0.5), which is a major
refactoring in order to simplify concepts, API, and introduce new
features such as dynamic deployment and reliable channels

4. Grow the community

* Activity since last report:

1. started using the jira tracker: 30 tickets created and commented so far

2. redirected users and developers from former google groups forum to
apache's mailing lists

3. Migrated web site from to

4. Most of the development work has been focused on 0.5


A tool for efficiently transferring bulk data between Apache Hadoop and
structured datastores such as relational databases.

Sqoop was accepted into Apache Incubator on June 11, 2011. Status
information is available at

Progress since last report:
 * Sqoop web site has been created.
 * All license headers have been reviewed.
 * All Java packages have been migrated from com.cloudera.sqoop to
 * The first incubating release complete - version 1.4.0-incubating.
 * Sqoop PPMC voted in two new committers - Alex Newman and Jarek Jarcec
 * Work on next major release of Sqoop has started.
 * Inaugural meetup for Apache Sqoop held in New York on November 7, 2011.
It was attended by over 30 users and developers.

Issues before graduation:
 * None


Incubating since: Dec-2010

Description: Wave is a real-time communication and collaboration tool. Wave
in a Box
(WIAB) is a server that hosts and federates waves, supports extensive
APIs, and provides a rich web client. This project also includes an
implementation of the Wave Federation protocol, to enable federated
collaboration systems (such as multiple interoperable Wave In a Box

Most important issues are:
* Building up community.

There's a stable levels of community activity around development of Wave in
a Box (WIAB). Also, there are a number of WIAB based projects like Kune and
CollaDi with their maintainers taking active role in discussions and

Project development:
 - Migrated the code to Apache SVN.
 - Updated to a new version of Jetty server.
 - Reduced the memory footprint of WIAB.
 - Bug fixes + small improvements.

Zeta Components

Apache Zeta Components are a high quality, general purpose library of loosly
coupled components for development of applications based on PHP.

Zeta Components was accepted into Incubator on May 25th, 2010

What has been done:

* Bug fixes (e.g. multibyte fixes in template component)
* Cleanup of test system
* Planning of actions for creating a release candidate.
* Alpha release targeted before Christmas.

What is still in progress:

* Build system discussions
* Bugfixing for release

What needs to be done:

* Making a release
* Look at ways to increase developer diversity and activity
* Find a new mentor to replace grobmeier.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message