On 09/02/2011 14:19, Scott Wilson wrote:
Here's a draft of our report - any comments?
Looks great. I've added the following and signed off:
* build community - mentors are aware of people using Wookie but not as
part of the project community
** community members are organising an event for said users in March
For background here. Wookie is being used in a number of UK based
projects in various universities. One or two people have posted to our
lists but in the main this activity is happening in isolation. This is
not an issue with the Wookie community. It is normal on all projects for
people to work in isolation.
Our job is to reach out to these people and bring them into the project
itself wherever possible. To do this we need to work to understand their
needs and concerns. Having understood this we need to ensure that our
community is supportive of these needs.
To this end Scott Wilson and I are organising an event in late March to
start this ball rolling.
Ross
======
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 November 2010:
* agreed and documented the release process
* created scripts for creating release packages
* improved 18n and bidi support to conform with W3C Widgets P&C spec (97%
conformance!)
* created the first release candidate and invited testing of the release
by the community
* various bug fixes and improvements (improved IE support, fixing JPA
issues)
* some of the Wookie contributors connected with the OpenSocial/Shindig
community at an OpenSocial event in Utrecht
Next steps:
* complete release process for the first release
* deciding on issues and features to prioritise for next release, quite
possibly:
** investigation/implementation into replacement for direct web
remoting layer (possibly socket.io) - already started
** add oAuth support using Amber when they have a release available
Issues before graduation:
* complete first release
* build community/expand user base
Signed off by mentor:
=====
On 1 Feb 2011, at 14:00, [email protected] wrote:
Dear Wookie Developers,
This email was sent by an automated system on behalf of the Apache Incubator
PMC.
It is an initial reminder to give you plenty of time to prepare your quarterly
board report.
The board meeting is scheduled for Wed, 16 February 2011, 10 am Pacific. The
report
for your podling will form a part of the Incubator PMC report. The Incubator PMC
requires your report to be submitted one week before the board meeting, to allow
sufficient time for review.
Please submit your report with sufficient time to allow the incubator PMC, and
subsequently board members to review and digest. Again, the very latest you
should submit your report is one week prior to the board meeting.
Thanks,
The Apache Incubator PMC
Submitting your Report
----------------------
Your report should contain the following:
* Your project name
* A brief description of your project, which assumes no knowledge of the project
or necessarily of its field
* A list of the three most important issues to address in the move towards
graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
* How has the community developed since the last report
* How has the project developed since the last report.
This should be appended to the Incubator Wiki page at:
http://wiki.apache.org/incubator/February2011
Note: This manually populated. You may need to wait a little before this page is
created from a template.
Mentors
-------
Mentors should review reports for their project(s) and sign them off on the
Incubator wiki page. Signing off reports shows that you are following the
project - projects that are not signed may raise alarms for the Incubator PMC.
Incubator PMC
