+1 with the understanding that there is the usual flexibility between policies and practices, consistent with the spirit and principles of the ASF for Apache Projects.
And, to be fair, I think TLPs should also self-assess on a periodic basis as an accountability of the PMC, nudged as necessary by the Chair (not to do it as much as to direct the PMCs eyes to the ball). I can also imagine the maturity model items being used on an exception basis, only reporting maturity-model deviations and how they are being addressed as part of a report to the Board. - Dennis -----Original Message----- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Thursday, August 6, 2015 00:28 To: Incubator General <general@incubator.apache.org> Subject: Re: Podlings and the ASF maturity model (was: Reform of Incubator...) On Thu, Aug 6, 2015 at 8:46 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > ...the maturity model shouldn't be a set of gating criteria, but that the > podling should self-assess its position and to what degree, as well as how, > each point is handled. Yes, many of the points are non-negotiable, but > don't claim that all are... So you would see the maturity model as one element of the Incubation graduating checklist, with self-assessment from the podling and its mentors? I like the idea. -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
