Sorry, my comment was too brief. 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 was commending the structure and clarity of the maturity model as a basis, not about it being somehow held to podlings as a graduation yardstick or anything else. I was responding in the context of Bertrand's comment, Creating a release checklist in a structured text format sounds like a good start anyway, so we can start with that ... . that used the maturity model format as a suggested form. - D -----Original Message----- From: jan i [mailto:j...@apache.org] Sent: Tuesday, August 4, 2015 10:37 To: general@incubator.apache.org; orc...@apache.org Subject: Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from the Apache Incubator) On 4 August 2015 at 18:46, Dennis E. Hamilton <orc...@apache.org> wrote: > +1 on how to start, with the maturity model as exemplar, is an outstanding > idea. Thanks. > > (I even have a poddling in mind for stress-testing it.) > It is clear to me, that incubator offer many advantages...but our current overweight to control everything is seen (and are) a negative effect, anything that can reduce that is good. I think the maturity model is good, but to used with care. If I think of the same podling as Dennis, that would clearly be a test done too early. rgds jan i. > > - Dennis > > -----Original Message----- > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: Tuesday, August 4, 2015 05:57 > To: Incubator General <general@incubator.apache.org> > Subject: Re: Reform of Incubator {was; [DISCUSSION] Graduate Ignite from > the Apache Incubator) > > Hi Daniel, > > On Tue, Aug 4, 2015 at 1:15 PM, Daniel Gruno <humbed...@apache.org> wrote: > > On 2015-08-04 13:01, Bertrand Delacretaz wrote: > >>... IMO the Incubator PMC can very much own this checklist, and I > >> volunteer to contribute to creating it... > > > If interested, I would very much like to work with you on perhaps turning > > this into a sort of 'online compliance check' where podlings could > upload a > > tarball or some such, and the service would scan it for compliance, go > > through the checklist, and report back which elements are compliant and > > which are not... > > Wow, that's more ambitious than what I envisioned but I know your are > able to do that ;-) > > Creating a release checklist in a structured text format sounds like a > good start anyway, so we can start with that and if you and others > want to turn it into an online analysis service that would be > fantastic. > > -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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
