-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? Martijn On Thu, Oct 15, 2015 at 12:14 PM, Emmanuel Lécharny <elecha...@gmail.com> wrote: > Le 15/10/15 11:46, Bertrand Delacretaz a écrit : >> Hi Incubator PMC, >> >> FYI I have started an experiment at >> https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc , >> 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: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
