Wow, that came around quickly.
OK, here's a draft - its a lot wordier than usual as there has been some
specific questions raised on the incubator general list about how to get
projects graduating.
I don't want this report to sound at all "defensive" on this topic but rather
to encourage more ASF folks to pitch in and help us out and give us some good
ideas and suggestions - so if anyone can suggest a better form of words,
please do!
========
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
Wookie has a small but quite active community, and the main issue we would like
to address before graduation is to ensure we have more diversity in our
community. As it stands we could probably graduate as we meet the minimum
criteria (5 committers from 3 organisation), but we feel we need at least one
more active committer before we feel we're ready to graduate.
One strategy for this is to reach out to projects and teams already using
Wookie and encourage their developers to contribute back to the community. We
know several projects (both in commercial and academic sectors) that have been
conducting R&D activity using Wookie and we want to make sure we can bring in
both contributions from these projects and also welcome their developers into
our community.
However we feel that Wookie will only really become fully sustainable when
there is more uptake of the W3C Widgets/Native Web Applications specifications
into "real" systems and products. On this front we're active and visible in
W3C, along with PhoneGap/Apache Cordova (incubating) who also support W3C
Widgets (the W3C Native Web Apps Community have a co-chair who is a Wookie
committer and another who is a Cordova committer). Another strategy has been to
support integration in Apache Rave (currently preparing to graduate) as this is
a way to build our user base (and is also a great way to demo Wookie). Another
approach we're 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.
In any case, we can certainly do more to promote Wookie and generate interest.
Since November 2011:
* 0.9.1 release
* Received updated patch for oAuth support from community member
* Received documentation contribution for packaging Wookie as a portable
app on a USB stick
Next steps:
* 0.9.2 release using an improved and simplified release process
* Developer outreach activity (see above)
* Improve communication about Wookie
* ASF Widgets demo
Issues before graduation:
* build community/expand user base
On 30 Jan 2012, at 21:07, Ross Gardler wrote:
> Your board reports are due, Jukka on the IPMC has had a look through
> the last reports and has a few items he feels need to be addressed in
> this months reports for your project - see below
>
> If you've not already drafted your report you need to do so *now* - if
> your report does not cover the questions asked of your project below
> then time to edit it.
>
> If you have written a report I intend to review them soon, so please
> be sure to have them in the wiki ASAP
>
> Ross
>
>
> ---------- Forwarded message ----------
> From: Jukka Zitting <[email protected]>
> Date: 30 January 2012 17:32
> Subject: Questions for projects
> To: general <[email protected]>
>
>
> Hi,
>
> The deadline for podlings to submit their February reports is already
> in two days since the ASF board meeting is scheduled for Feb 15th.
>
> I spent a few moments reviewing the November reports and related
> information of all the projects scheduled to report in February
> (excluding new projects on monthly schedule). Here are a few questions
> or comments for each project. Hopefully they're helpful in focusing
> the February reports on key issues.
>
>> Airavata
>
> Only point 3 in your last report is a real graduation issue. How
> diverse is your community now?
>
> What happened with the release candidate mentioned in the last report?
>
>> Ambari
>
> How has CTR worked for you?
>
> I'm seeing a significant drop in list activity since December. What's up?
>
>> Amber
>
> Any progress on the graduation issues mentioned in the last report?
>
> What's the status with the mentioned "copyright signoff from
> University of Newcastle"?
>
>> Clerezza
>
> Have you made a release yet? If not, what's the blocker?
>
> Any other issues before graduation?
>
>> DeltaSpike
>
> How is the Git repository working for you?
>
>> Droids
>
> Any progress on getting more people to contribute?
>
> I'm seeing a significant drop in list activity since December. What's up?
>
>> HISE
>
> Result of the retirement vote.
>
>> Jena
>
> When can I vote on your graduation?
>
>> Lucene.NET
>
> When can I vote on your graduation?
>
>> NPanday
>
> When can I vote on your graduation?
>
>> Nuvem
>
> I don't see too much activity in the last five months. What's up?
>
>> OpenNLP
>
> Congratulations on graduation!
>
>> PhotArk
>
> I notice the discussions about a new direction. What's next?
>
>> SIS
>
> Do you have a plan for reviving the project?
>
>> Stanbol
>
> Still no release?
>
> Any other issues before graduation? Points 1b and 1c in your last
> report are not blockers for graduation.
>
>> VCL
>
> What's the status with the issue of university approval of the CLAs?
>
> How diverse is your currently active committer-base?
>
>> Wink
>
> Looks like you're discussing ideas to increase commit activity. Any
> concrete actions you're taking on this?
>
>> Wookie
>
> What's blocking you from graduating?
>
> How diverse is your currently active committer-base?
>
>> Zeta Components
>
> How diverse is your currently active committer-base?
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> --
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective http://opendirective.com
