incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject Incubator Report June 2008
Date Mon, 23 Jun 2008 18:29:41 GMT
The top two issues of discussion in the past month are textual revision(s)
to make it clearer that the Incubator runs the same as every other ASF
project: only PMC votes are binding, although we encourage everyone from the
broader community and the especially the PPMC to cast (non-binding) votes;
and (once again) issues with Maven.

The Maven problem is a tension between the need to distinguish between
Incubator artifacts and other ASF artifacts, compounded by the problem that
Maven doesn't do anything to authenticate any artifacts at all.  A couple of
approaches have been mooted.





Incubating since: 19 May 2008

Mailing lists, subversion repository, and JIRA setup was completed.

Software Grant Agreement (Initial code owners are chanwit and me) was sended
for the intial donation of Hama code from the google project.

ICLAs were sent, But We are still waiting for the arrival of CCLAs.




Pig is a platform for analyzing large data sets that consists of a
high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs. The salient property of Pig
programs is that their structure is amenable to substantial parallelization,
which in turns enables them to handle very large data sets.

Pig's infrastructure is in good shape. Several new features have been added
since Pig joined the incubator. This includes streaming, parameter
substitution, custom splits, better configuration management, improved
memory management, etc. 147 issues resolved since. Work in progress includes
addition of types and rework of the execution pipeline.

The community is growing with the addition of Pi Song as a new committer.

There is increased activity on the pig-dev mailing list with a number of

The project needs to improve its compliance with some standard Incubator
tasks, like updating the status file on a regular basis.

Incubating since: October 2007




River is aimed at the development and advancement of the Jini technology
core infrastructure. Jini technology is a service oriented architecture that
defines a programming model which both exploits and extends Java technology
to enable the construction of secure, distributed systems which are adaptive
to change.

A substantial amount of issues have been resolved (34 in total) with a small
number (18 in total) left for our second release. The overall participation
of committers has been improved and we have seen more discussion around
issues, although participation of non Sun committers is still not what it
ought to be. The need for an automated test environment is felt and the
workflow for JIRA should be adapted to facilitate our review then commit
policy which committers seem to do in practice.

Things that needs to be done before graduation:

the API in the com.sun namespace must be changed to org.apache, probably has
to await the incorporation of patches lingering around and after our
automated test framework is in place

overall participation of non Sun committers must increase and we should grow
our community by getting more people involved

Incubating since: December 2006

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

View raw message