incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject June 2011 Incubator Board Report
Date Tue, 14 Jun 2011 15:35:52 GMT
The Incubator PMC now totals 143 members, with some additional requests
(joining and a resignation) pending.  Recent changes include Peter Royal and
Phil Steitz (pending) dropping off; and Shane Curcuru, Srinath Perera,
Nicolas Lalevee, Marvin Humphrey, Michael McCandless, Nigel Daley, Tommaso
Teofili, Yegor Kozlov, Leif Hedstrom and Steve Loughran joining the PMC.

Certainly the biggest thing in the Incubator this month is the arrival of for Incubation. is going to need significant
help and guidance, with an emphasis on liasoning with other, external,
projects such as LibreOffice.  There is very significant concern regarding
how this project will relate to the rest of the ecosystem,
and those will need to be carefully addressed.  One of the first challenges
for the project will be deciding its scope.  If it is going to try to be the
old, essentially an Apache Licensed "coopetitor" to the
downstream forks; or if it is going to focus on common technologies, release
vanilla binaries for key platforms, and let the downstreams take the primary
role in delivering end-user binaries.  Other issues with respect to may challenge our infrastructure.  There may also be IP
(patent and trademark) issues to address.  But the lengthy and diverse list
of Mentors should be aware of and preparing to address all of the issues.

Despite's arrival, and its well than 1000 messages swamping
the mailing list, there was more activity than just that one topic.

BigTop, a project for the development of packaging and tests of the Hadoop
ecosystem, is proposed for Incubation.

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

Sqoop -- a tool designed for efficiently transferring bulk data between
Apache Hadoop and structured datastores such as relational databases -- was
voted to enter Incubation.

There is nascent discussion regarding moving Alois and BlueSky to dormant



Airavata is a software toolkit currently used to build science gateways but
that has a much wider potential use. It provides features to compose,
manage, execute, and monitor large scale applications and workflows on
computational resources ranging from local clusters to national grids and
computing clouds.

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

   1. Finish the security paper work needed to import donated code with
cryptographic dependencies.
   2. Engage the community by document existing design, drafting detailed
JIRA tasks defining smaller goals.
   3. Remove incompatible license dependencies and implement over ALV2
compatible libraries.
   4. Simplify the build process and provide simple to use cases.
   5. At least one Apache Incubator release.
   6. Develop a strong community with organizational diversity and well
aligned with existing ASF projects as outlined here:

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

No, not at this time.

How has the community developed since the last report?

The interactions to date have been focused on development, and getting the
project started.

How has the project developed since the last report?

Airavata was voted into the Incubator by the IPMC on May 7, 2011.

Suresh Marru is pushing forward on the Airavata website. There is also work
going on related to this to define a new Apache Airavata logo. In addition,
Suresh led a development roadmap discussion.



The ALOIS project team wrote an private e-mail to it's mentors shortly after
the last report. They have told us that due to personal reasons they cannot
keep this project alive and there will be no project activity in near
future. We have agreed to wait until the June 2011 comes up. So far there is
no change in project activity or interest, no e-mails and even no more
private messages. After this report the Incubator-PMC needs to discuss about
moving this podling to attic. (Christian Grobmeier)

In addition to Christian's report, I'd like to mention that we didn't find
any interest in the project outside of our small group, although we did
quite a lot requests off list. If there would be someone to take over the
project, we would be happy to give a helping hand at the start. (Urs Lerch)



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
 * Perform successful Releases - Done
 * Grow the community and committer base - stale at a medium level
 * Decide on graduation target of TLP or subproject - TBD

The BVAL community is still discussing about the 3 possible graduation
 * Graduate as TLP
 * Graduate as part of Apache Commons
 * Graduate under the Geronimo TLP

The codebase is mature and stable, thus there is not much development effort
going on atm. Otoh this means that there are not many developers working
actively on BVAL.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
 . None at this time.

How has the community developed since the last report?
 . No new committers.

How has the project developed since the last report?
 . 0.3-incubating was released on 2011-02-04.



This project did not report.  The Incubator PMC will begin discussion to
move the project to dormant status.



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 got a larger contribution of a UDP Binding from BMW Research / Itestra
via Jira. It enables Signals (~ Publish/Subscribe for Properties) and UDP
Broad- and Multicasting of Etch messages, as well as a proposal for a
mechanism of handling multiple etch client connections on the server via one
stack ("single session"). review is in progress.
- Michael and Holger joined the Apache Retreat in Knockree, Ireland and got
to know other Apache people.
- C++ Binding is currently in development (nothing to publish yet, but it
will come), and a new developer (Martin Veith) will join the Etch team at
BMW Car IT and will contribute code to the project
- fixed some smaller bugs in the C, Java and C# bindings
- transition to new CMS system is on its way, some more copying of existing
text/documentation has to be done
- we are looking forward to more contributions from BMW Research / Itestra
regarding Service Management in the future

future tasks:
- integrate contributed third-party code
- make CMS switch
- C++ binding



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. Port Gora code and license headers into ASF license headers.
   2. Develop a strong community with organizational diversity and with
infection into existing ASF projects like Nutch and Hadoop.
   3. At least one Gora incubating release

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

No, not at this time.

How has the community developed since the last report?

Ever since the 0.1-incubating release, it's been kind of quiet. We did have
a couple users (Yves Langisch, Joseph Vychtrle, Ioannis Canellos, and
Marshall Pierce) pop on, report some issues, and help out.

How has the project developed since the last report?

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

The 0.1-incubating release is out. We're currently working on a
0.1.1-incubating patch that includes an update to Gora-Hbase that will allow
us to upgrade our existing jars on Maven Central. Once we roll 0.1.1 (Chris
Mattmann will RM it), Nutch 2.0-trunk will upgrade to the Gora release
shortly thereafter.



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 ==

 * Invite new active committers

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


== Community development ==

 * Mailing list shows increased usage from previous report.
 * 'Chiahung lin' is actively involves in our community and research area of
hama fault-tolerant design.
 * 'Miklos Erdelyi' has contributed some performance improvements.
 * One of GSoC students, 'Thomas Jungblut' has excellently finished
implementing his GSoC project, and also has started to contribute major
parts in our project.
 * Steve Loughran has became a mentor

== Project development ==

 * We've made our first release under the Apache Incubator.
 * Switched from Ant to Maven.
 * Some new features are added e.g., web UI for job monitoring, examples,
messages bundle.
 * 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 and producing a release of the software.

Since the last report we have:
* Written install docs for the 0.1 release
* Fixed bugs we found that are blocking the 0.1 release
* continued development on new features for 0.2
* been accepted to present a talk on HCatalog at the upcoming Hadoop Summit

Currently there are 32 subscribers to the user list and 30 on the dev list.
There were 29 and 27 respectively last month.



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 2010, September 7th.

Project Development

 * Good documentation site is online now.
 * Working on an Isis incubator release
 * Currently voting on isis-0.1.2-RC4-incubating

Community Development

 * Active mailing list.
 * Frequent commits

Top 3 Issues to address in move towards graduation

 * Getting first release out to demonstrate credibility.
 * Ensuring existing committers all happy with transition to Apache.
 * support people who like to move from NO to ISIS

None of these issues requires Board attention.

New Releases

 * We are currently in the progress of voting on our first release.



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:

* There had been some discussion with Oracle regarding the future of JSR-326
in May this year, a definitive statement is expected from them in July.
* The question has been raised as to the future of JSR-326 and the Apache
Kato podling, the options being to keep both or continue only with one of

The following is planned for next reporting period:

* Decide in what form the podling should continue, if at all.

Before this project can graduate we need to encourage more participation in
the project and grow the community.

Sadly Kato seems still to be set on a holding pattern




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 connectors includes
Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy),
SharePoint (Microsoft), RSS feeds, and web content. 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

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

1. We need at least one additional active committer, as well as additional
users and repeat contributors
2. We may want another release before graduating
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?--

A book has being completed, and is becoming available in early-release form,
available from Manning Publishing.  We have signed up two new committers and
one new mentor.  We continue to have user community interest.  We've had a
number of extremely helpful bug reports and contributions from the field.

--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 is being considered.


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

MRUnit entered incubation on March 8th, 2011.

* MRUnit has started receiving contributions from users (2 significant
contributions thus far).
* Still looking to develop a broader community.
* Release and contribution docs under development.
* Eric Sammer doing a great job pushing development forward.
* Discussions about producing first MRUNIT release candidate.

Issues before graduation
* Create the MRUnit web site
* Make an incubating release
* Grow the community size and diversity

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



Apache OGNL is a Java development framework for Object-Graph
Navigation Language, plus other extras such as list projection and
selection and lambda expressions.

The project just joined the Incubator on April 26, 2011.

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

 - make at least a big release that shows to Commons PMC the
compliancy level of OGNL to Commons policies;
 - attract more users, at the moment only Apache Struts people are
interested because they heavily use OGNL;
 - attract more new committers, the only external contribution we got
was about the new OGNL logo.

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

 - no news about Marc Andrew Davidson's even if was requested twice;
 - not every PPMC member joined the private ML yet;
 - due to OpenSymphony dismissing, we need importing old issues to ASF jira.
We've been trying to contact someone from OpenSymphony to obtain an OGNL
Issue dump/XML backup

 * How has the community developed since the last report

Community is healthy and people participate to discussions, getting a
lot of suggestions from Commons PMCs, few members are very active, no
new committers yet

 * How has the project developed since the last report.

Codebase has been imported and committers started updating it
according to Apache Commons policies. Site is online and we got a new

We also have Jenkins and Sonar jobs.



OpenNLP is a machine learning based toolkit for the processing of natural
language text. It supports the most common NLP tasks, such as tokenization,
sentence segmentation, part-of-speech tagging, named entity extraction,
chunking, parsing, and coreference resolution. These tasks are usually
required to build more advanced text processing services.

OpenNLP entered incubation on 11/23 2010.

We started to integrate a couple of new features and will soon start testing
for our second release at Apache.
To solve our training data problem we created a proposal for an annotation
project which suggest to label
AL 2.0 licensable text documents with semantic annotations.

There is still good traffic on both the user and dev mailing list.

A list of the the most important issues to address in the move towards
 * Resolve potential IP issues around releasing training models
 * Establish open regression tests for the parser and coreference component
 * Identify and encourage new contributors on the path to committership



Rat is (still) a small and mature code base without a clear home at Apache
to aim for.

Unlike the last two quarters there has been some development activity with
commits by four different committers.  Some JIRA issues have been opened and
not all of them have been addressed by now.



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 and services through a highly
customizable and Web 2.0 friendly front-end.

Rave entered incubation on 2011-03-01.

Current Status:
  * The community has identified and completed the features for a 0.1
incubation release
  * Members of the community have reached out to Wookie do discuss alignment
  * Members of the community have reached out to Shindig to offer assistance
toward producing a Shindig beta release required for incubation release
  * The community is developing release guidelines and posting them to the
  * The community expects to propose a release vote for 0.1 incubation
release to the IPMC within the month
  * There were over 50 commits and 1 patch submission from the committers
and the community as a whole
  * Mailing list activity remains high

Next steps:
  * Continue to build up awareness of Rave and grow the community
  * Release 0.1
  * Identify issues for a 0.2 incubation release

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



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

Incubating since: Dec-2010

Most important issues are:
* Migrate source code from to SVN.
* Bug fixes and scaling/enhancing stability in preparations toward 1.0
* Implement WIAB functionality to import waves (deltas) from Google Wave

The Wave in a Box community exhibits a stable even if slow growth. The mail
list stays very active, new contributors emerge every month, WIAB demo
servers show constant growth both in active users and topics discussed.

Project development:
  - Issues migrated to the ASF Jira
  - Introduction of "shared per domain waves"
  - Improvement of search functionality performance.
  - Using Guice for servlet injection - which should facilitate using WIAB
modules for 3-rd party developers.
  - User and admin password robot agents.
  - Remote logging of client errors.
  - Numerous important enhancements to the client side architecture.
  - about 40 more changes and bug fixes.

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

View raw message