August 2011 Board reports (see ReportingSchedule).

These reports were due here by Wednesday, 10 August 2011 so that the Incubator PMC can relay them to the board. The report is closed.

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:

Remember that this is a "text" report, so no markup please.

--------------------
Airavata

Airavata is a software toolkit which 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. Airavata is incubating since May 2011.

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

   1. Update web service implementations from XSUL to Axis2. Update security libraries and simplify the build process and provide sample use cases.
   2. Package, document and release at least one Apache Incubator release.
   3. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment

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?

Web designer Barbara Hallock was voted in a commiter and PPMC member for her contributions to the website design, logo and CSS contributions. The website is now live with her contributions. Lahiru Gunathilake an existing apache commiter from Axis2 & QPID projects has made significant contributions and provided 25+ patches to Airavata. He is voted in as a commiter and PPMC member. A new volunteer Patanachai Tangchaisin has been contributing to the various components of the project.

How has the project developed since the last report?

* Significant progress has been made towards a release. All components are organized within the svn adding project level and module level maven build profiles.
* Website is updated with documentation for build and eclipse development instructions.
* The default database in WS-Messenger and XRegistry is changed from mysql to Apache Derby. Derby is integrated as an embedded database to build and deploy as a maven profile. This porting has removed the incompatible license dependency on mysql-connector jar.
* WS-Messenger module is re-factored, packaged and tested. The messaging system clients are being worked on, this component needs to integrated with rest of the modules.
* XBaya module is cleaned up of unused legacy code, improved dependency management and simple test cases are tested through.


Signed off by mentor: rgardler, ate, mattmann

--------------------
Amber

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

How has the community developed since the last report

 - Some users have started asking for help or getting started guides on the mailing list

How has the project developed since the last report

 - Work has begun on updating the OAuth implementation
 - Discussion about preparing for an initial release is ongoing

Signed off by mentor: seelmann

--------------------
Bigtop

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

Bigtop entered incubation on June 20 2011

A list of the three most important issues to address in the move towards graduation:
* Create Bigtop web site. Item in progress. See ticket BIGTOP-9
* Make an incubating release.
* Grow the community size and diversity.

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

How has the community developed since the last report:
* Discussions have been started about how to organize the development (RTC vs CTR)

How has the project developed since the last report.
* Discussions have been started about how to organize our first release and what should it include.

Licensing and other issues
* Work to obtain CCLA from Cloudera including grant for existing Bigtop code from Cloudera GitHub repository is done.

Signed off by mentor: tomwhite, phunt

--------------------
Bluesky

The incubator community voted to retire the Bluesky podling. It will be closed in near future and reporting will stop with this period.

See here for the vote results:
http://s.apache.org/7oo

Some more context:
http://s.apache.org/4Q2

Signed off by mentor:

--------------------
Clerezza

(incubating since November 27th, 2009)

Clerezza is a framework and set of components designed to make it easy to build application for the semantic and the social web.

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

1. First release
2. Tutorial on how to build apps with clerezza

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

- No issue

How has the community developed since the last report

- Intense discussions on the process. When is code acceptable into trunk, when is it legitimate to veto changes with a -1 and what should the consequences be. As a consequence to these discussions a "contributing" page was added to the project site: http://incubator.apache.org/clerezza/contributing/

- Daniel Spicar accepted as new contributor.
- Registration of Apache Clerezza for an evaluation through OSS Award (http://www.ossaward.ch/)

How has the project developed since the last report.

- The code has been improved to a stage ready for release. Procedure for releasing the code base has been initiated. We are now very closed to a first release, already 3 release candidates have been presented for voting. Hoping that soon an acceptable one will be proposed.

Signed off by mentor: rgardler

--------------------
= Deft =

Deft is a non-blocking, asynchronous, event driven high performance web framework running on the JVM.

Deft entered incubation on July 8rd, 2011.


Project development

We are still working in the sandbox (https://svn.apache.org/repos/asf/incubator/deft/sandbox/). We have signed and sent the software grant and also received signed ICLA from the external contributors that submitted patches to Deft before the Apache incubation. A chairman is currently being voted. All (Github) issues have been migrated to Apache JIRA. We have already attracted some new contributors.

Most important issues to address
 * Finalize the sandbox work (almost done)
 * Converge the coding standards discussion (discussed on the dev ML)

Issues before graduation
 * Create Deft web site (or migrate deftserver.org)
 * Put together a first incubation release
 * Find new committers

Signed off by mentor: Mohammad Nour (mnour)

--------------------
Deltacloud

(Incubating since July 2010)

Deltacloud is a cross cloud abstraction API that allows management of resources (compute and storage) across different IaaS cloud computing providers using a single, open API. At present Deltacloud supports management of Amazon EC2, Rackspace, Gogrid, Rimuhosting, Terremark, RHEV-M, vSphere, IBM SBC, Eucalyptus, Opennebula compute resources, as well as Amazon S3, Microsoft Azure, Eucalyptus and Rackspace Cloudfiles storage resources.

The last three months have been characterized by ceaseless work towards our 0.4.0 release, which has now been posted as a release candidate.

We also voted three new committers in during that time.

We are in the process of preparing for graduation to a TLP under the Board; hopefully, a resolution will be posted before the August Board meeting.

Improvements/Fixes/Additions included in upcoming 0.4.0 release (and since the last report) include:

Server:
  * deltacloudd: new option --drivers to list all drivers
  * deltacloudd: new options --ssl, --ssl-key and --ssl-cert to
    enable HTTPS support
  * API entrypoint reports features in JSON
  * unify response behavior: any operation returning a 201 Created also
    sets the Location header to point to the new resource; ensure the
    status for an operation is the same regardless of output format
  * Add type to public addresses; type can be one of 'ipv4', 'mac', 'vnc',
    and 'hostname'
  * Complete overhaul of the HTML UI, now uses jquery-mobile
  * Response status for attach/detach storage is now 202 (instead of 302)
  * Response status for get/set blob metadata is 204 No Content
  * Response status for (un)register with load balancer is 204 No Content
  * The user_name feature now reports the permissible length of the name
    as the 'max_length' constraint
  * Add Date header to responses as per RFC 2616
  * New collection 'firewalls' for managing sets of firewalling rules
  * split server/config/drivers.yaml into individual files so each driver
    can be packaged separately; gives deployers better choice of what
    drivers they want enabled
  * Numerous bug fixes and improvements to the test suite
  * Drivers
    + Condor
      - new driver to run a simple cloud based on the Condor grid scheduler
    + EC2
      - Fix bug in reboot instance so that the details returned are those
        of the stopped instance, not some random instance
      - Support getting and updating blob metadata
      - support destroying images
      - support firewalls (security groups)
      - do not support user_name anymore; instance tagging is too fragile
        in EC2 to be used reliably for this
      - do not support registering an instance with a load balancer upon
        creation anymore
      - stream blob PUT to backend (requires thin)
      - support attaching EBS snapshot to instance upon creation (feature
        'attach_snapshot')
      - support elastic IP's
    + Eucalyptus
      - support firewalls (security groups)
      - support elastic IP's
    + Gogrid
      - when retrieving single realm, make sure we return the right one
      - correctly capture load_balancer params
      - report a listener if load_balancer has no instances
    + Mock
      - support destroying images
    + Rackspace
      - support destroying images
      - stream blob PUT to backend (requires thin)
    + RHEV-M
      - support creating and destroying images
      - report VNC address of instances
      - can use Audrey's confserver to fetch IP of an instance
    + vSphere
      - turns a VMWare vSphere installation into a cloud
      - driver stateless, state is stored in vSphere's data store in
        'deltacloud' folder
      - images are template VM's
      - single HWP, whose max_cpu and max_memory are based on available
        cpus and memory across all vSphere hosts
      - support data injection via user_data and user_iso (upload entire
        ISO image) For both, instance gets virtual CD-ROM with injected
        data

Client:
  * make authentication info for instances available
  * retrieve type and address for public addresses of an instance
  * deltacloudc: allow specifying bucket location when creating a bucket

Site:
  * Major rewrite of REST API docs, covers the entire API now
  * Add libdeltacloud API docs


Signed off by mentor:
Carl Trieloff (cctrieloff)

--------------------

= Droids =

Droids is an Incubator project arrived from Apache Labs. Droids entered incubation on October, 2008.

It's an intelligent standalone robot framework that allows one to create and extend existing web robots.

The last three months have been very productive and focused on our first official release. However a discussion on the general incubator list raised concern about the absence of binding votes of IPMC members. This leaded to abort the first release. In the last member meeting we selected one of our Droids committer as member and he subscribed now to the incubator PMC to have a binding vote as well.

Issues before graduation :

 * Do a release
 * IP clearance

Signed off by mentor: Thorsten Scherler

--------------------
EasyAnt

Work has started to clean up the work done by one of the initial committer of Easyant as he doesn't have provided its ICLA:
 - some work has been identified as containing no IP and will be kept.
 - some other work will be just removed, as it doesn't impact the functionality of Easyant
 - and some piece seems to have some IP issue and EasyAnt will probably not work without it. The developers have started a discussion about how to deal with a such delete, how could it be rewrote for instance.
This work is reviewed by the mentors.

The www.easyant.org site is now redirecting to incubator.apache.org/easyant

The developer community is not super active, but it is there and responsive to discussion like the management of the continuous integration, discussion about some design of some plugins, or discussion about debugging tools for Ant (discussion which has migrated on ant-dev).

Signed off by mentor: antoine, bodewig

--------------------
Flume

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.

Issues before graduation:

* Migrate mailing lists from Cloudera infrastructure to Apache mailing lists.
* Create Flume web site.
* Make an incubating release.
* Grow the community size and diversity.
* Licensing and trademark issues.

Community:

* Mailing lists:
 - flume-user@incubator is now fully active. flume-user@cloudera.org is read-only
 - flume-dev@incubator is nearly fully active, pending code import.
* Added two contributors.
* Discussion and voting about CTR / RTC.

Project developments:

* CCLA from Cloudera regarding license grant for existing Flume code from Cloudera has been received by ASF.
* Flume project imported to Apache Jira from cloudera.org Flume jira. (Thanks medthomas, gmcdonald!)
* Initial svn import completed (Thanks joes!)
* Initial inquiry into trademark status.
* Confluence Wiki space is started to get populated with resources and design information.
* An initial implementation of masterless acknowledgement announced.
* Proposals for next generation master being discussed.
* OpenTSDB connector availability announced.

Signed off by mentor: tomwhite, rgoers

--------------------
Giraph

Giraph is a large-scale, fault-tolerant, Bulk Synchronous Parallel (BSP)-based graph
processing framework that runs on Hadoop. Giraph entered the incubator in August 2011.

Project developments:

* Project status page created.
* Subversion directories created and authorization granted.
* Code grant received from Yahoo!
* Mailing lists created.
* Mentors all subscribed to private
* Jira created.
* Initial check on trademark status.
* Confluence wiki requested.

Signed off by mentor: omalley, mattmann

--------------------
HISE

(project add text here)

Signed off by mentor:

--------------------
Jena

Jena is a semantic web framework in Java that implements
the key W3C recommendations for the core semantic web technologies of
RDF and SPARQL.  Jena entered incubation in November 2010.


Progress since the last report:

The project uses the Apache-based developer list exclusively and is now encouraging users to use the Apache-hosted user mailing list by regular reminder and an automatically added a trailer on all messages on the old user list.

The Apache-hosted website is "under construction" in staging.  The project selected the Apache CMS and buildbot system. The design and navigation is done.  Next step is to populate the website with the content from the old sites.

One module, LARQ, is being used to learn about the Apache release process and the requirements it brings with it.

Important issues to address for graduation:

* Create a code base in Apache with legal clearance.

There are about 10 small contributions (a few line upto a single class file) across the whole codebase that that need to be resolved.  All are currently covered by BSD licences.

* Do a full release

Issues for the Incubator PMC or ASF Board:

None.

Technical development:

The new transactional native SPARQL storage systems, TxTDB has been advertised as a prototype snapshot. Some users have offered to help with testing.

Signed off by mentor: rgardler
--------------------
Kafka
(introduced to Apache incubator on Jul 4, 2011)

Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing.

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

   1. Package, document and release at least one Apache Incubator release.
   2. Develop a strong community with organizational diversity.

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?

Just get started. The mailing list is pretty active, including people other than the initial committers.

How has the project developed since the last report?

* Moved everything (svn, website, mailing list, jira, wiki) in Kafka to Apache. CCLA from LinkedIn filed with Apache.
* The end-to-end compression feature is almost complete.
* Received various patches from 3 different companies, including dynamic topic discovering for cross-cluster mirroing, mx4j support, .net client, etc.


Signed off by mentor:

Alan Cabrera

--------------------
Libcloud

(project add text here)

Signed off by mentor:

--------------------
Lucene.NET

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 & 2.9.4g are being worked on and tested. The 'g' stands for generics. The 2.9.4g version now uses .NET 4.0
* Prototyped build scripts with ncover, fxcop, style cop, nunit/mbunit, and sandcastle have been made.

Current Activities:

* New site design per new Lucene.Net logo. StackOverflow was gracious enough to put together a logo contest including footing the bill. The incubation site now shows the logo that was picked from the contest. http://incubator.apache.org/lucene.net/
* Working towards getting CI installed.
* The shingle filter was ported
* A simple faceted search contrib project was created.
* Develop a process to automatically (as much as possible) convert the Java Lucene code to C# (to maintain our line by line port)

Goals for graduation:

* Have a nearly fully automated process to convert Java Lucene to C#.
* 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

Signed off by mentor: bodewig

--------------------
NPanday

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.

We have successfully released NPanday-1.4.0-incubating. Now we are currently polishing off the NPanday-1.4.1-incubating.

We are also happy to report that our community has gained a lot of 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

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

* Pasindu Madubashana continue making progress on Data Services project as part of GSoC 2011
* Community continue small but active, with about 3 to 4 active committers + the new GSoC student.

Top things to resolve prior to graduation:

* Increase the number of active committers.

Signed off by mentor:

--------------------
ODFToolkit

The ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents. Unlike other approaches which rely on runtime manipulation of heavy-weight editors via an automation interface, the ODF Toolkit is lightweight and ideal for server use.

* ODF Toolkit entered incubation on Aug 1st, 2011.

* Most important issues to address.
  1) Moving the community from the ODF Toolkit Union to Apache and learning the Apache Way
  2) Growing the community, increasing diversity of committers
  3) Grants for the transfer of existing code, documentation etc to Apache
  4) Migration of existing things to Apache infrastructure, including code repository, website, mailing list, bugzilla and wiki.
  5) Successful podling release.

* 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
  Just getting started. After mailing lists are ready (INFRA-3809), we will start to discuss migration and new release. At the same time, we will invite the existing users to this new community and try to attract more new people join us.

* How has the project developed since the last report.
  None at this time. Just getting started.

Signed off by mentor: nick

--------------------
OGNL

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 joined the Incubator on April 26, 2011.

There are no other important issues open before a possible graduation. Actually the project is discussing its graduation into Apache Commons.

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

   - due to OpenSymphony dismissing, we need importing old issues to ASF jira. We finally contacted someone from OpenSymphony and obtained the huge Issue dump/XML backup, there is someone that is working on it, but due to security policy (the dump contains also users and password hashes), before importing it, an open-heart surgery is needed.
   - The software grant has been received

 * How has the community developed since the last report

   - Community activity decreased since codebase has been imported and polished.
   - Luc Blanchard has joined the committers lists (one of original authors of OGNL)

 * How has the project developed since the last report.

   - Codebase has been imported & polished, we are in the middle of a big refactoring stripping off generated code by JavaCC that was versioned in the SCM and modified.

Signed off by mentor: grobmeier, olamy

--------------------
Oozie

(project add text here)

Signed off by mentor:

--------------------
OpenNLP

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 almost finished the development for our next release (1.5.2) and second release in the Incubator and will start testing it soon.
The development team is still active and most of the changes have been done by four independent committers.
This week Boris Galitsky proposed on the mailing list to contribute a component for syntactic generalization which we will hopefully be able to accept.
Furthermore we started to work on tooling for an annotation project in our sandbox and hope to be able to attract new contributors through this effort.

A list of the the most important issues to address in the move towards graduation:
 * Establish open regression tests for the parser and coreference component
 * Identify and encourage new contributors on the path to committership

Signed off by mentor: Grant Ingersoll

--------------------
OpenOffice.org

* OpenOffice.org entered incubation 2011-06-13.

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

* Issues

Some challenges exist: Under SUN/Oracle, semi-autonomous single focus "projects" were the basis of structure of OOo, many would like a similar system to be used under Apache. By contrast a single overarching authority is proposed with oversight of the entire project by the (P)PMC.  Discussions are ongoing.

Discussions with regard to licensing, especially with regards to documentation, are continuing.

* Community development progress

As of 2011-08-06, 71 committers, 52 on the PPMC up from 56 and 49 at last report. Steps are continuing to bring onboard the last of the initial Committers who have not yet provided an ICLA.

208 people are subscribed to the ooo-dev list.  124 people have posted to the list of those 59 have more than 10 posts. 9 posters have more than 50 posts each.
User related queries or posts were virtually nil.
The shape and methodology of the Community Outreach is still in discussion.
An OOo blog has been initiated and is getting a high number of hits daily

* Project development progress

The grant from Oracle America, Inc for OpenOffice trademarks, logos, domain names has been received.

Work with Infra: OOo Mediawiki has been successfully moved onto Apache infrastructure. Some concerns relating to IP of materials on the wiki are still in the proces of resolution.

www.openoffice.org is now in an Apache sandbox and work is being done to recreate it in the Apache CMS

Signed off by mentor: grobmeier, Nóirín Plunkett, rgardler

--------------------
PhotArk

Apache PhotArk will be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities.

PhotArk was accepted for Incubation on August 19, 2008.

 * Umashanthi Pavalanathan elected as Photark committer
 * Subash Chaturanga continue making progress on "Face Recognition" project as part of GSoC 2011
 * Umashanthi Pavalanathan continue making progress on making Photark more "Social" as part of GSoC 2011

* Issues before graduation :
  * PhotArk started as a project with no initial code-base, and we have grown the community to the minimal independent committer size required for graduation and have been seeing slow but continuous interest in the project. The community started discussion graduation and based on mentors feedback we are going to recruit couple committers before we start the graduation process.

Signed off by mentor: lresende

--------------------
SIS

Apache SIS is a toolkit that spatial information system builders or users can use to build applications containing location context. This project will look to store reference implementations of spatial algorithms, utilities, services, etc. as well as serve as a sandbox to explore new ideas. Further, the goal is to have Apache SIS grow into a thriving Apache top-level community, where a host of SIS/GIS related software (OGC datastores, REST-ful interfaces, data standards, etc.) can grow from and thrive under the Apache umbrella.

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

Development progress has really slowed, and there isn't much mailing list activity. Nothing to
stop the project for (yet), but something to keep an eye on.

* Community progress since the last report

Development and mailing list activity have significantly slowed down.
This is a small core set of committers and community though. It would be
great to get some new blood and folks interested in the project.

I still believe that we should try and target a 0.2-incubating release with
a layer service and some basic integration with Apache Tika (a GDAL parser is
being worked on in that community with an eye towards integration into SIS).
Also we are looking at Apache OODT as a mechanism for geospatial storage and
persistence.

The ESRI interest mentioned in the last board report hasn't really gone anywhere.

* Project progress since last report

SIS was voted into the Incubator by the IPMC on February 21, 2010.

Development progress has been pretty much nil. Chris hopes to start work on the
layer service this quarter, but again, it would be great to have some new blood
here. Folks that are interested in geospatial services, data presentation, and
such would be much welcomed within the project.

Signed off by mentor: mattmann, greddin, kevan

--------------------
= Sqoop =

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 http://incubator.apache.org/projects/sqoop.html.

Progress since last report:
* CCLA from Cloudera regarding license grant for existing Sqoop code from Cloudera has been received by ASF.
* Source code has been migrated to Apache SVN.
* Apache Mailing Lists and JIRA for Sqoop are now in active use. The Cloudera Mailing Lists and JIRA have begun the process of being phased out.
* Development activities have started with two issues resolved and others under active development.

Issues before graduation
* Create Sqoop web site.
* Make an incubating release.
* Grow the community size and diversity.
* review all license headers (all contains Cloudera).
* change java package from com.cloudera.sqoop to org.apache.sqoop.


Signed off by mentor: Mohammad Nour (mnour), Olivier Lamy (olamy)

--------------------
Stanbol

Stanbol is a modular software stack and reusable set of components for semantic content management.
Entered incubation on 2010-11-15.

1. A list of the three most important issues to address in the move towards graduation.
 - make a first release (depends on a first release of Apache Clerezza to eliminate SNAPSHOT dependencies)
 - create demos showing the power of Stanbol to grow the community
 - improve documentation and web site to lower the barrier for new users

2. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
 - none

3. How has the community developed since the last report
 - Florent André was elected as a new committer
 - some new users showed up on the mailing list
 - Potentially new users from the CMS industry were attracted in a Stanbol hands-on session during a CMS community workshop organized by the IKS project in Paris (http://www.iks-project.eu/news-and-events/events/mycms-and-web-data-iks-community-workshop)

4. How has the project developed since the last report.
 - Code preparations for first release (solved incompatible license issues, license headers, release profile, etc.)
 - Added new component "FactStore"
 - Integration tests added to EntityHub
 - CMIS module added to CMS Adapter

Signed off by mentor: rgardler

--------------------
Stonehenge

(project add text here)

Signed off by mentor:

--------------------
VCL

VCL has been incubating since December 2008. VCL is a cloud computing platform for the management of physical and virtual machines.

Community Involvement

As stated in the previous report, the Apache VCL community continues to grow. We're seeing more people start to contribute to our online documentation and file JIRA issues. We're also starting to see more patches attached to JIRA issues.
We continue to see growing interest in the VCL project from a variety of locations.
We are currently working on growing the committers for Apache VCL project.
Releases

The Apache VCL 2.2.1 version was release on April 8th 2011 and addressed bugfixes and minor improvements.
Our next release Apache VCL 2.3 is on track and we are targeting late fall timeframe. New features planned include support for the KVM hypervisor which is to be contributed by the community. In addition to KVM, the committers will address server loads, and the improvement of cluster reservations.
Top Issues Before Graduation

Continue to increase contributors to establish a more diverse development community

Signed off by mentor:

Alan Cabrera, kevan

--------------------
Whirr

Whirr is a library for running services in the cloud.

Whirr was accepted into the incubator on 11 May 2010. Status information is available at http://incubator.apache.org/projects/whirr.html.

Progress since the last report (May 2011): We have made a fifth incubator release (0.5.0-incubating). We added three committers to the PPMC. We continue to get contributions from outside the initial committer base. Whirr was covered in two presentations at the end of last month at OSCON.

The Whirr PPMC and the Incubator PMC have voted for Whirr to graduate as a TLP (http://s.apache.org/ZbH, http://s.apache.org/Ebj).

Plans for the next period:
* Perform post-graduation steps.
* Do a sixth release.
* Encourage community growth.

Signed off by mentor: tomwhite


--------------------
Wink

Apache Wink is a project that enables development and consumption of REST style web services. The core server runtime is based on the JAX-RS (JSR 311) standard. The project also introduces a client runtime which can leverage certain components of the server-side runtime. Apache Wink will deliver component technology that can be easily integrated into a variety of environments.

Apache Wink has been incubating since 2009-05-27.

Notable Activity:

* New users are starting to post to the wink-user mailing list.

Planned Activity:

* JAX-RS 2.0 is starting up in the JCP.  May attempt to prototype/develop against the next specification to provide an eventual JAX-RS 2.0 compliant runtime.
* Work towards graduation.

Top issues before graduation:

*

Signed off by mentor: kevan

--------------------
Wookie

Wookie is a Java server application that allows you to upload and deploy widgets for your applications. Wookie is based on the W3C Widgets specification, but widgets can also be included that use extended APIs such as Google Wave Gadgets and OpenSocial.

Wookie has been incubating since 17th July 2009

Since May 2011:
     * Release 0.9 put out for vote
     * Published a new CMS website with more documentation
     * Explored with Apache Rave(incubating) community and Wookie community members idea of separate common "widget store" for handling metadata and discovery of widgets. Rough consensus was to develop separately for now, identify potential for merging later. Community members associated with two EU-funded projects (ROLE and ITEC) have been developing Wookie-based widget stores, and we hope to get their code submissions to kickstart this work.
     * Community members exploring Apache Amber (incubating) for oAuth support within Wookie

Next steps:
     * Finish 0.9.0 release and move onto a 0.9.1 release
     * Continue to work and liase with other projects
     * Create a new "widget store" sub-project, aiming to bring in code submissions from ROLE and ITEC projects

Issues before graduation:
     * complete first release
     * build community/expand user base

Signed off by mentor: rgardler, ate

--------------------
Zeta Components

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

What has been done:

- bug fixes

What is still in progress:

- getting a release
- one critical bug fix is still in review board waiting for comments/approval, it is necessary for the next release
- minor bugs that should be fixed for the release have almost all been fixed

What needs to be done:

- get reviews and commit the patch in review board
- get a release, really

Signed off by mentor: grobmeier

August2011 (last edited 2011-08-16 03:14:19 by NoelBergman)