incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martijn Dashorst <>
Subject Re: [graduation] Maturity model-based assessment of Groovy for its graduation
Date Sun, 18 Oct 2015 08:48:19 GMT
-1 on requiring all projects to do this exercise. It is not policy,
and frankly as a volunteer organization we can let the communities
themselves determine whether this is something they want to spend
their time on.

I thought we were a community for/over code, not a bureaucracy for/over code.

If/when a community finds itself in a hard spot, perhaps *then* it is
valuable to assess the maturity model, to see how/what can be improved
upon. But requiring this of all projects? With a deadline too?


On Thu, Oct 15, 2015 at 12:14 PM, Emmanuel Lécharny <> wrote:
> Le 15/10/15 11:46, Bertrand Delacretaz a écrit :
>> Hi Incubator PMC,
>> FYI I have started an experiment at
>> ,
>> using our maturity model to evaluate Groovy before its mentors suggest
>> its graduation (which should happen very soon).
>> So far this has helped uncover a few issues that we (at least I)
>> hadn't noticed otherwise. Nothing major, but interesting, and I think
>> it can be useful for the IPMC and Board once they have to decide to
>> graduate the podling.
> That's an interesting exercise !
> Having read the document Betrand has completed for Groovy, I do think
> that an audit of all the existing TLP should be done in the next month
> to check if all the iterms are correctly fullfiled. I suspect we would
> be surprised...
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Become a Wicket expert, learn from the best:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message