I concur, and similarly pushed back just a few days ago on another suggestion of such "policy".
Not really sure that an ASF-wide metric is appropriate (ie. all communities are different, and freedom to set their own path is important), but there is definitely value in some in the model. It can with provide insight/review, and critical thinking about a community. Cheers, -g On Thu, Oct 15, 2015 at 7:21 AM, Jim Jagielski <j...@jagunet.com> wrote: > If we are to use the maturity model as the guideline regarding podling > graduation, then certainly the model should be voted on and approved > by the membership as *the* model for the ASF, right? > > Basically, it looks to me that the model is proposing and creating policy, > and this is something that needs to be done 'correctly', if you get my > meaning. > > > On Oct 15, 2015, at 5:46 AM, Bertrand Delacretaz <bdelacre...@apache.org> > wrote: > > > > 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. > > > > -Bertrand > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
