I agree & will sign off on the report


Sent with Good (www.good.com)


-----Original Message-----
From: Ross Gardler 
[[email protected]<mailto:[email protected]>]
Sent: Monday, April 23, 2012 10:07 AM Eastern Standard Time
To: [email protected]
Subject: Re: May reports due in ten days


Sorry, I meant to add a caveat to my backing of the outline report
below - I want at least one other mentor to agree this is the right
approach.

Ross

On 23 April 2012 15:05, Ross Gardler <[email protected]> wrote:
> Excellent, we seem to all feel the same way.
>
> So in summary I believe this board report should say:
>
> - we are diverse enough to graduate, although we are a small community
> - a more regular release schedule aligned with that of Apache Rave
> (which uses Wookie) may help with community development
> - graduation should help attract new contributors
> - we will seek approval to graduate during the next quarter, after the
> 0.10 release which is imminent
>
> I'm out of time now, can someone else put it together and I'll sign it off.
>
> Ross
>
>
> On 23 April 2012 14:55, Franklin, Matthew B. <[email protected]> wrote:
>>>-----Original Message-----
>>>From: Ross Gardler [mailto:[email protected]]
>>>Sent: Monday, April 23, 2012 4:50 AM
>>>To: [email protected]
>>>Subject: Fwd: May reports due in ten days
>>>
>>>Board report due:
>>>
>>>In February we said "Wookie has a small, reasonably active community,
>>>however, the majority of
>>>that activity is focussed around one or two individuals."
>>>
>>>We also said:
>>>
>>>"as it stands we could probably graduate as we meet
>>>the minimum criteria (5 committers from 3 organisations). We recognise that
>>>some IPMC members would suggest graduation at this point might help
>>>accelerate community growth. We intend to discuss this within the
>>>community
>>>over the next quarter whilst also seeking to expand our community."
>>>
>>>However, we've pretty much failed to discuss this. This is not a good
>>>sign. None of us have had the time to drive this important issue.
>>>
>>>Don't get me wrong, I'm not suggesting there is a fundamental problem
>>>here. I'm just saying we need to crack on with it. In my opinion our
>>>incubator status is holding us back. Furthermore, Rave has graduated
>>>and if we are not careful our incubation status will hold Rave back
>>>too.
>>>
>>>I know from my own conversations with Wookie users that the
>>>"incuabting" label is holding some people back (although it may just
>>>as well be a convenient excuse). I propose that we undertake to
>>>graduate in the next quarter. To do this we really need to address the
>>>issues we identified last month:
>>>
>>>  - [DONE] 0.9.2 release using an improved and simplified release process
>>>  - Developer outreach activity (see above)
>>>  - Improve communication about Wookie
>>>  - ASF Widgets demo
>>>
>>>So, some questions/ideas:
>>>
>>>Matt can you help Wookie get to the point of doing regular releases,
>>>preferably synced with Rave. I don't mean Rave depends on a Wookie
>>>making a new release, I mean we aim to have a new Wookie release out
>>>two weeks before the next Rave release is due.
>>
>> +1.  I think getting on a regular release schedule will be a huge boost.  
>> From what I have seen, you are all doing really good work, but we just 
>> aren't' getting that out the door on a regular basis.  I can definitely help 
>> the team accelerate this.
>>
>>>
>>>Developer outreach - we should undertake to update the tutorials.
>>>Perhaps we need to focus more on the creation of widgets as a "simple
>>>step" in, if these widgets can run stand-alone (without Wookie) this
>>>will attract more people, however, we need to consider whether this is
>>>changing the make-up of what the Wookie project is. It might be better
>>>to do that in an associated apache-extras project.
>>>
>>>Previously we discussed making it easy to create widgets that can be
>>>usefully reused in the Apache CMS. The trademarks people are, for
>>>example, looking at solutions for sponsor visibility. Concom need a
>>>way of getting information about upcoming ASF events onto peoples
>>>sites. It seems to me both of these are similar use cases. Can we
>>>build them as templates?
>>>
>>>Ross
>>>
>>>---------- Forwarded message ----------
>>>From: Jukka Zitting <[email protected]>
>>>Date: 22 April 2012 12:55
>>>Subject: May reports due in ten days
>>>To: general <[email protected]>
>>>
>>>
>>>Hi,
>>>
>>>It'll soon be time for the podlings reporting in May [1]  to start
>>>drafting their reports.
>>>
>>>When doing so, please consider the review results from February [2]:
>>>
>>> IP clearance: Amber
>>> Release trouble: Clerezza, Stanbol
>>> Low activity: Ambari, Nuvem, PhotArk, SIS, Wink, Zeta Components
>>> Low diversity: Airavata, Droids, VCL, Wookie
>>> Ready to graduate: Jena, Lucene.NET, NPanday, OpenNLP
>>>
>>>Has the situation in your podling changed over the last three months?
>>>If not, what's your plan for improving the situation?
>>>
>>>For example, I notice that Clerezza has made a release, but Stanbol
>>>still needs one. Also, Lucene.NET and NPanday are yet to graduate. Did
>>>something come up to prevent progress, or have you just not gotten
>>>around to it yet (which BTW is fine; much better than having bigger
>>>issues)?
>>>
>>>And to any projects in the "Low activity" category that still aren't
>>>seeing increased activity: Do you have a good reason to expect
>>>activity to pick up, or should we consider retiring the project?
>>>
>>>[1] http://wiki.apache.org/incubator/May2012
>>>[2] http://wiki.apache.org/incubator/February2012
>>>
>>>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
>
>
>
> --
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective http://opendirective.com



--
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com

Reply via email to