May 2012 Board reports (see ReportingSchedule).

This report is CLOSED.

The trend of more podlings graduating than are coming in continues, which
is a good thing given the backlog of stuck projects the Incubator has
accumulated over the past years. This trend is also visible in the podling
categorization we've been doing since February. The number of podlings
in the rough starting/incubating/graduating categories has gone from
7/13/4 in February to 2/9/7 now.

Our recent focus on report review with active feedback to and dialogue with
the podlings has helped drive this progress. Until now this extra effort has
come from just a few individuals, but we're working on ways to make this
more sustainable by sharing the work for example by having IPMC volunteers
as "shepherds" who'll review specific reports in more detail. Initial results
seem promising.

While not designed to replace the existing mentor model, the extra reviews
have helped spot and deal with many cases where podlings have been in need
of extra help or just some gentle pushing ahead. We're looking at ways to
track mentor activity in order to better identify such cases before they
become too troublesome.

o Community

  There were no changes to the Incubator PMC since our last report.
  The IPMC currently has 158 members.

  The following podlings are requesting graduation to Apache TLPs:

  - Apache Hama
  - Apache MRUnit
  - Apache Giraph
  - Apache ManifoldCF

  The Incubator PMC recommends the board to accept the respective resolutions.

  The Zeta Components podling has retired due to low activity.

  The JSPWiki podling started a graduation vote, but it was withdrawn after
  concerns about the low project activity were raised. Based on feedback from
  general@, the community hopes to make another release and some other progress
  before restarting the graduation vote.

  There is an interesting thread on general@ about the sometimes vague
  boundary between redistributing upstream dependencies as standalone
  components or integral parts of an Apache product. The BigTop podling,
  where this issue came up, will hopefully summarize this discussion in more
  detail in their next report.

o Legal / Trademarks

  The retired Zeta Components codebase was migrated to GitHub where it
  retains the project name (without the "Apache" prefix) even though not
  much new activity is expected. The move was handled well, with
  trademarks@ in the loop.

  The Amber project has been stuck for a long time with an IP clearance
  issue that they have been unable to resolve by themselves. It seems like
  this issue could have been resolved one way or another already years ago
  with more mentor help, which unfortunately has been lacking.

o Releases

  The following incubating releases were made since our last report:

  - April 16th, 2012: Apache ManifoldCF 0.5-incubating
  - April 23rd, 2012: Apache Jena LARQ 1.0.0-incubating
  - April 28th, 2012: Apache MRUnit 0.9.0-incubating
  - May 5th, 2012: Apache Airavata 0.2-incubating
  - May 8th, 2012: Apache OpenOffice 3.4.0-incubating
  - May 9th, 2012: Apache Stanbol 0.9.0-incubating

  The Apache Mesos 0.9.0-incubating release is just hitting the mirrors
  after a lenghty release vote that failed to attract enough IPMC votes
  for quite a while.

o Infrastructure

  The Flex project is still blocked with its migration to ASF infrastructure,
  which seems to be a major contributing factor to the downwards trend seen
  in Flex list activity. A solution or at least some workaround is urgently

-------------------- Summary of podling reports --------------------

Still getting started at the Incubator (2 podlings)

  CloudStack, Syncope

  These projects are still getting started, so no immediate progress
  towards graduation is yet expected.

Not yet ready to graduate (9 podlings)

  IP clearance:  Amber
  No release:    Flex
  Low activity:  Ambari, Droids, Nuvem, Photark
  Low diversity: Airavata, DeltaSpike, SIS

  We expect the next quarterly report of projects in this category to
  include a summary of their actions and progress in solving these issues. 

Ready to graduate (7 podlings)

  Clerezza, Lucene.NET, NPanday, Stanbol, VCL, Wink, Wookie

  We expect these projects to graduate within the next quarter.


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

  1. The documentation is improving but still not par to ease barrier of entry.
     The code, documentation and JIRA issues have to be efficiently
     organized and managed to appeal to wider developer community.

  2. Develop a strong community with organizational diversity and well
     aligned with existing ASF projects as outlined here:

  3. Create a regular and predictable release process and schedule

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

  The community is very active averaging 150 dev list emails and 75 commits
  per month. Airavata community encourages cross pollination with other
  Apache projects and also reuses significant number of license compatible
  open source libraries. This has helped keep the focus, but delayed the
  releases with impasse on legal requirements. The delay in making a release
  had lost some developer momentum.

  The community is not yet significantly diverse but lately the interest is
  growing. The project is committed and very supportive to external users and
  is putting the effort on increasing diversity. The PMC has discussed few
  potential outreach venues and have proposed and engaged with 8 GSoC student

How has the community developed since the last report?

  No new committers or PPMC members elected in the last quarter. Three new
  users from the community are very active in the mailing list. Some have
  started to send patches and have potential interest.

  4 GSoC projects proposed on Airavata have been accepted. The students for
  these projects are Hasitha Aravinda, Yaroslav Porshnev, Milinda Pathirage,
  and Bhathiya Jayasekara.

How has the project developed since the last report?

  0.2-incubating release candidate (skipped 0.1-incubating numbering) was
  significantly improved in regards to license and notice complains. The
  Community Vote was successful with 5 PPMC and 2 mentor votes. The Vote
  in IPMC general list is ongoing.

  With the delay in release, the community has branched a 0.2 release and
  has made significant progress on the trunk. Many features have been added
  and ready for successive couple more releases.

  The community has actively responded to GSoC proposals and student
  questions resulting in few quality proposals.

  Community is voting for a wiki to increase focus on documentation and

Signed off by mentor: mattmann, rgardler, ate


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

  - Incubating since 30 August 2011.
  - 162 jiras fixed on trunk (0 added since Feb report) + 8 jiras fixed 
    on dev branch ambari-186
  - After having no commits since January, yesterday a new code base
    was contributed and checked in on dev branch ambari-186. Development
    is happening rapidly on the branch while the project discusses how
    to move forward. The current proposal is to continue development on
    the branch until it is usable and then call a vote to replace trunk
    with the code on the branch.
  - 8 new developers have contributed to the ambari-186 code base

Issues that must be addressed before graduation are:

  - Making a release
  - Attracting users and developers
  - Increase diversity of developers outside of Hortonworks

Signed off by mentor: omalley, ddas


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.

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

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

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

  - We need copyright signoff from University of Newcastle or some guidance
    on how to proceed.

How has the community developed since the last report?

  - Raymond Feng joined in as a mentor
  - 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

  - an attempt to clarify the legal issue is on going see LEGAL-134
  - Fixed a bunch of issues for aligning with latest OAuth specification

Signed off by mentor: rfeng


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


  We believe Clerezza will be ready to graduate soon. Currently discussions
  for a plan for community development are ongoing. Once a plan for community
  development has been defined we can discuss graduation. Documentation and
  tutorials are still in need of improvement and this may be addressed as
  part of the community development plan but we believe lacking documentation
  alone should not stand in the way of graduation.

How has the community developed since the last report:

  The cooperation with the Apache Stanbol project has been improved with
  two Stanbol committers becoming Clerezza committers.

How has the project developed since the last report.

  - We successfully released Clerezza (0.2-incubating).

  - Apache Wink has accepted a patch by a Clerezza developer. This presents
    an opportunity to replace our own JAX-RS implementation with Wink's.

  - Discussions about the release process and its documentation have taken
    place. We have identified possible problems with our version policy and
    release process when releasing only a subset of the modules Clerezza
    consists of. It is our intention to be able to make such releases. No
    conclusion has been reached yet.

  - A drop of activity in the second half of this quarter (after the release).
    This can be partially explained with the fact that many developers use
    Clerezza in other projects and the release caused a temporary shift in
    focus on those projects.

Signed off by mentor: bdelacretaz, rgardler


CloudStack is an IaaS (“Infrastracture as a Service”) cloud orchestration
platform. CloudStack has been in incubation since 2012-04-16


  Cloudstack just entered the incubator a couple of weeks ago. Since then,
  the mailing list has been setup  and discussions have started to migrate
  from the existing list to the ASF-hosted list, with several 'new names'
  participating including one of those 'new names' submitting a patch.
  Currently, the code repository and bulk of existing infrastructure is still
  hosted by Citrix, but the community is looking forward to getting that
  moved to Apache as soon as possible.

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

  1. The base level of infrastructure migration has begun but still has far
     to be finished. At present the mailing lists exist, but wiki, project
     website, source repository, bug tracker, etc still need to be brought
     up and migrated. In many ways we are blocked on further progress by
     lack of account creation for initial committers.

  2. Diversity of the contributor base still needs to be expanded - this was
     identified as an issue in the proposal, and remains one, though we are
     encouraged by a seeming uptick (we've been in incubation for less than
     a week, so trends are indeed difficult to identify at this point) in
     interest on the mailing lists from previously uninvolved individuals.

  3. The project needs a working process definition.  What is the review
     process for contributions, recommendations for engaging before writing
     large amounts of code, etc.

  4. The project is using source and binaries with a number of
     non-ASF-approved licenses.  This needs remediation.

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

  No issues that we are aware of at this point.

How has the community developed since the last report?

  There has been no previous report - so nothing to report here.

How has the project developed since the last report?

  There has been no previous report - so nothing to report here.

Signed off by mentor: brett, dkulp, jim


(incubating since December 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 our last report in February 2012, we have accomplished the following:

  - Finished the initial build structure
  - Finished the initial test-infrastructure
  - Finished migrating first core feature contributions from Seam3 and CODI
  - Started discussions about tools for our documentation and website
  - Started with the status page (based on
  - We received the Code grant from JBoss Inc for JBoss employee written
    parts of Seam3
  - We shipped the deltaspike-0.1-incubating and deltaspike-0.2-incubating

Upcoming major goals:

  - Finish test-infrastructure to allow in-container tests
  - Finish the setup for the documentation and the website
  - Work on the next features: deltaspike-security, deltaspike-jpa,

Top 2 or 3 things to resolve before graduation:

  1. Build community
  2. Create Documentation

Signed off by mentors: Mark Struberg (struberg), Gerhard Petracek, jim


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.

Tobias Rübner has been voted in and added as a committer and PPMC member.

Issues before graduation :

  Diversity is still an issue for the poddling. The addition of Tobias
  is a step towards remedying that.

Signed off by mentor: rfrovarp

Flex (extra report)

Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.

Summary: A large community is losing momentum as it waits for Adobe to
complete the source code transition and infrastructure.

Date of entry to the Incubator:  December 31, 2011

Top three items to resolve before graduation:

  - Resolve trademark donation or licensing
  - Complete code and bug database donation
  - Make at least one release

Is there anything that the Incubator PMC or ASF Board specifically needs
to address?

  The ASF legal team will have to agree to a custom Trademark licensing.
  Adobe is still finalizing its proposal for the agreement.

Are there any legal, infrastructure, cross-project or personal issues that
need to be addressed? (Are there any stumbling blocks that impede the podling?)

  Besides the trademark issue mentioned previously, the import of existing
  JIRA bugs is blocked by an issue with Apache JIRA's import utility. It has
  failed to import the data file supplied by Adobe. Infra has opened a support
  ticket with Atlassian, but the problem remains unresolved two months later.

Check that the project's Incubation Status file up to date.

What has been done (releases, milestones, etc.) since the last report?

  - The Flex compiler source code, including history, was imported into
    the SVN repository.
  - Additional localization resources have been donated.
  - Carol Frampton is working to create a release candidate.  We expect
    the initial RC's to be rejected as we finalize licensing and other
    policy issues.

What are the plans and expectations for the next period?

  Adobe expects to complete the transfer of the mustella test suite.
  We hope to get an initial release approved by IPMC.

Are there any recommendations for how incubation could run more smoothly
for you?

  Our mentors continue to be very helpful.

  We really need to get JIRA up and running.  I still would like the incubator
  to consider separate servers for projects.  Having to set up external
  servers as an interim is a lot of work and adds confusion when you want
  to move to a final server or url later and you could have migration
  issues if you didn't set up the server in a compatible way.

Signed off by mentor:


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:

  - Released 2.9.4g (generics version of 2.9.4) at the end of january

Current Activities:

  - Lucene 3.0.3 porting is nearly complete. We have some bugs to work out,
    and need to clean up our contrib projects a bit, but we hope to release
    that within a month or two.

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). UPDATE: We have done some more investigative work
    on this, but not much progress was made.

  - Parity with Java Lucene (4.0)

  - 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. UPDATE: Unfortunately, we have not made any
  progress on this - hopefully we can have a more conclusive update next
  check in. Our development/committers group is small, and work sometimes
  happens in bursts and then stalls - something we need to work on a bit.
  The team has started to be more vocal about the project, for example a
  blog has been added, and hopes to attract more contributors.

Signed off by mentor: bodewig


NPanday allows projects using the .NET framework to be built with Apache Maven.
NPanday has been incubating since August 2010.

NPanday had a lull of activity over the last few months as all the committers
had other things occupying their time. This has picked up again over the last
couple of weeks, with the renewed push for another release. There is still a
need to focus on a graduation plan, and to better promote the project among
the .NET and Maven communities as a result.

As reported last time, we continue to see small growth in users, and
occasional patch submissions, but haven't added a new committer in a while.

The top priorities towards graduation are:

  - work out a concrete plan towards graduation in the next quarter
  - encourage newer contributors to do so on a continuing basis.

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

Signed off by mentor: dennisl


Apache Nuvem will define an open application programming interface for
common cloud application services, allowing applications to be easily
ported across the most popular cloud platforms.

Nuvem was accepted for Incubation on June, 2010.

The Nuvem project is slowly seeing increase of committer activity and
mailing list discussions from external users or people interested in the

The project also had a GSoC project accepted and will have Dulini Atapattu
working on a Message Queue component for different cloud platforms.

Top things to resolve prior to graduation:

  - Increase the number of active committers.

Signed off by mentor: lresende


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.

PhotArk has a small community of contributors, mostly student, that need a
lot of attention in order to keep them active, and the lack of attention made
the community stale for a bit and we are starting to bootstrap it again
with some committers becoming active again, and other like myself freeing
up to be able to work on the project again.

The community have also decided to move the project direction to become a
hybrid HTML5/Cordova mobile application that aggregates images from
different photo sources such as: Flickr, Instagram, Facebook, etc. And
we will have two students helping on this project as part of GSoC 2012.

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. We need to make these contributors constantly active
  in order to think about graduation again, or recruit new contributors.

Signed off by mentor: lresende


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.

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

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

  The plan proposed here: seems to be going
  well and we are happy with the direction the project is headed.

Community progress since the last report

  No new PPMC members and committers added this quarter.

Project progress since last report

  Looking at just mailing list activity:
  went from 9 email messages in January 2012 to 32, 74 and 39 in Feb-April 2012

  We are participating pretty actively in GSoC and hoping to get 1 or 2
  students who are collaborating with the Apache OODT project as well
  for a joint effort.

  In addition, we've seen some good cross pollination between other (at
  the time) incubating projects like Jena and Any23, and TLPs like OODT.
  In Jena and Any23's case, there are active discussions and work going on
  to implement the W3C GeoSPARQL system using Apache SIS. After Andy Seaborne
  poked around on the mailing list, Chris Mattmann volunteered to implement
  it, and a subsequent thread has ensued.

  Chris started rolling an RC for Apache SIS 0.2-incubating, but got blocked
  on some packaging issues that Kevan Miller identified that needs to be fixed.
  Shouldn't be too difficult and we hope to have an IPMC VOTE on it within
  the next week or so.

  We have also started to regularly use the project wiki. You can find it
  here: Included on
  the wiki are links to all of our Incubator reports, along with 2 tutorials.
  The first one is a quick start guide that Ross Laidlaw improved and copied
  from the SIS README.txt file. The second demonstrates how to get Apache
  OODT and SIS connected to dump spatial information out of geolocated files
  in Apache OODT and to search them in SIS.

  Two newcomers to the community, Peter Karich, and Charith Madusanka have been
  contributing patches, issues, and working issues within SIS. Peter has been
  improving the speed of SIS's Quad Tree implementation, and Charith has been
  helping improve our demo.jsp file, our javadocs, and is now working on a GUI
  for SIS.

  SIS is actively being used and piloted by students of Dr. Ellis Horowitz and
  Chris Mattmann in USC's CSCI 572: Search Engines and Information Retrieval

  If we can add some new committers soon (which we expect), roll
  0.2-incubating, and then potentially get an 0.3 shortly thereafter, we
  think SIS will be well on its way to graduating and its own project.

Signed off by mentor: mattmann, kevan


Apache Stanbol is an open source modular software stack and reusable set of
components for semantic content management. Incubating since November, 2010.


  We believe Stanbol will be ready to graduate in the next few days: the
  issues mentioned in our previous report have been adressed, the release
  is being voted on (after six iterations of release candidates) and should
  be out in the next few days if all goes well. Community activity is steady
  and slowly increasing.


  No new committers or PPMC members since the last report, but steady activity
  on our lists from both existing and new members of our community.

  Two Stanbol committers have been elected as Clerezza committers, furthering
  ties between both podlings.

  A Stanbol GSoC project has been accepted, with Rupert Westenthaler as
  its mentor.

  Contribution of several EnhancementEngines based on LinguaGrid (NLP
  framework) by Alessio Bosca (STANBOL-583).

  Integration of DBpedia Spotlight ( with the
  Stanbol Enhancer, led by a new Stanbol contributor.

  Stanbol was presented in the Developer Track of WWW2012

Project activity:

  - Reorganization of the codebase for the release, the one binary dependency
    left that's not available in Maven Central has been moved to a separate
    -deps package for the release, as discussed on the incubator general list.
  - Content hub faceted search improvements.
  - New EnhancementEngine based on Apache Tika
  - TopicEngine (STANBOL-197) is now functional
  - Full LDpath support for the Entityhub Indexing tools (STANBOL-408).

Signed off by mentor: bdelacretaz, rgardler


Syncope is an Open Source system for managing digital identities in enterprise
environments, implemented in JEE technology. Syncope joined the incubator
on February 10th 2012.

Community Development:

  Older Syncope users-base is migrating to the new ASF infrastructure, a few
  new users joined, user@ ML activity is raising: currently 27 subscribers,
  including 4 archive / non human address.

  No new committers have been added.
  dev@ ML activity is high: currently 31 subscribers, including 4 archive /
  non human address.

Project Development:

  Commits activity is healthy, commits@ ML activity is high.

  Committers are working for finalizing the first final version

Web Site/Communication Development:

  The website is kept up-to-date on
  Status page is updated.
  It introduces Syncope and provide first content.

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

   None so far.

Signed off by mentor: elecharny, coheigea


VCL has been incubating since December 2008. VCL is a cloud computing
platform for the management of physical and virtual machines. It provides
comparatively easy and simple base line install with a end-user self
service interface.

New Committers

  The Apache VCL community recently added James O'Dell from California
  State University at Fullerton as a committer. We welcome James and look
  forward to his expertise and knowledge to help advance VCL project and

New PPMC member

  The Apache VCL PPMC recently added Aaron Coburn as a new PPMC member.
  The current PPMC welcomes Aaron.

Community Involvement

  - The Apache VCL community is a growing community with global interest
    from Education and commercial entities.
  - The community is fast to respond to user questions and discuss design
    ideas in a respectful manner.
  - We have seen cross project interest as through a contribution of a
    VCL driver to the Apache LIBCLOUD project.
  - There are community members that have expressed interest in becoming
    committers. They are working through their initial contributions. We
    look forward to hopefully bring them aboard.


  - Our next release has been delayed from our previous board report.
  - This 2.3 release is a very large release, including bug-fixes, support
    from kvm, VMWare vcenter, multi-lingualization, and approved
    contributions from the community.
  - We are in testing now and hope to generate a 2.3 release candidate in
    the next few days.

Top Issues Before Graduation

   Graduation work itself - As a community discuss graduation to determine
   if we are ready. If so proceed with starting the process.

Signed off by mentor: kevan, adc


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

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

Development list traffic and discussions are steadily, but low. We noticed a
little increase on the traffic with some users starting to provide patches and
request for a new release, which the community have started working on.

We are having a second discussion around project status
( and one option that was brought up was the
possibility of graduating as a sub-project of a TLP that have dependencies
on Wink (e.g. Geronimo and/or Tuscany). The community thinks that we will
have a better understanding of the direction we want to take by the next
report (in three months).

Activities since last report period :

  - Apache Wink 1.2 release being finalized in the project mailing list.
  - Website being migrated to Apache CMS and taking in consideration
    trademark requirements
  - Raymond Feng being recommended as a new PMC member

Planned Activity:

  - Continue discussion around project future

Top issues before graduation:

  - Increase the size/diversity of the active dev community

Signed off by mentor: kevan


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.

Progress since February 2012:

  - 0.9.2 release
  - Hoang Minh Tien added as Committer
  - Matt Franklin added as Mentor
  - Improved release documentation
  - GSoC student project

Next steps:

  - implement new release schedule (aligned with Apache Rave)
  - 0.10.0 release using new release process
  - start graduation process after release
  - ASF Widgets demo

Issues before graduation:

  - none


In our last report we identified our target for this period was to identify
ways to improve the diversity of the Wookie community.

Since our last report we added a new committer (Tien) and we are now diverse
enough to graduate (6 committers from 4 organisations), although we are still
a small community.

We feel that graduation of the project will also help attract new
contributors, and we will seek approval to graduate during the next
quarter, after the 0.10 release which is imminent.

As well as graduation, we have agreed that having more frequent scheduled
releases, coordinated with Apache Rave may also help with community

Matt Franklin has joined Wookie as a mentor and is active in helping with
this process.

We've also created a lot of detailed documentation on the release process
and are encouraging more committers take a turn at being release manager
to both test the documentation and to spread the experience of doing this
more widely.

Our first release under the new schedule will be 15th May.

Another approach we're (still) looking at is how we can use Wookie to deploy
widgets that relate to ASF processes and activities as a way of raising
awareness and interest; we've done some experiments with Widgets using the
Jira API as a starting point for a demonstrator and we may want to explore
this further.

We also have a GSoC student project with Wookie this year.

Signed off by mentor: rgardler, mfranklin, ate

Zeta Components

The project has decided to retire from the incubator. Code has mostly been
moved to github already. The question has raised to trademarks, if the
developers can still use their name.

Here is the vote:

Here is the vote result:

The reason is lack of activity.

Retirement tasks from the IPMC are still open

Signed off by mentor: grobmeier

  • No labels