OK, thanks Bertrand. My recollection of the maturity-model discussion was that it is about an ideal state and not some gate, and that projects would always be correcting their state toward that defined in the model. I confirm that the current document simply characterizes what the state is for a mature project.
I see no statement anywhere that a TLP, or a graduating incubator project, must pass through a maturity assessment. It would certainly be useful for a podling to conduct a self-assessment of its maturity before requesting graduation. It would also be useful for an operating TLP to assess itself with respect to the model, especially if there are concerns in that regard. I am neutral on how this fits into graduation criteria for podlings. However, if it is used for gating purposes, I think that needs to be made very clear by the IPMC lest it just lead to more randomizing of the podling seasoning process. In particular, mentors need to be on board with respect to their responsibilities. I can also imagine a graduation going forward (just as releases can) with certain items remaining to be addressed post-graduation. I note that, at the moment, there is no direct reference to the Project Maturity Model at the <https://www.apache.org/dev/project-requirements> draft nor at the Incubation Policy, <https://incubator.apache.org/incubation/Incubation_Policy.html>. I can also imagine a TLP using (or being asked to use) the project maturity model as a checklist in assessing their current state in a report to the Board. Are these the kinds of applications that folks have in mind? -- Dennis -----Original Message----- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Wednesday, August 5, 2015 00:44 To: Incubator General <general@incubator.apache.org>; dennis.hamil...@acm.org Subject: Podlings and the ASF maturity model (was: Reform of Incubator...) Hi, On Wed, Aug 5, 2015 at 12:24 AM, Dennis E. Hamilton <dennis.hamil...@acm.org> wrote: > ...I understand the maturity model to be something to aspire to and that > Apache Projects > will always be working toward it. I mean TLPs, not podlings, although > podlings should be > aware of it and also aspire to it... I don't see why podlings should be different here, once they are about to graduate. Why can't we define our incubation process as a way for podlings to learn to operate according to that maturity model [1]? This would allow us to use the maturity model [1] as a checklist for graduating podlings - do you see anything in there that shouldn't be required from a podling that's about to graduate? -Bertrand [1] http://community.apache.org/apache-way/apache-project-maturity-model.html --------------------------------------------------------------------- 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
