It might be interesting to have a reworked set of metrics which we could apply on an as needed basis (perhaps once a quarter or once a year) to reassess maturity on an on-going basis. But I agree the current version (the wording at least) is very much geared towards graduation from incubation so we don't want how it is in the current form. I am also not keen to create more "overhead" work than needed so it might be best to wait until we can almost automatically collect a bunch of stats that could form the basis of the quarterly report to the board.
Paul. On Fri, Nov 20, 2015 at 5:33 AM, Bertrand Delacretaz <[email protected]> wrote: > Hi Pascal, > > On Thu, Nov 19, 2015 at 2:25 PM, Pascal Schumacher > <[email protected]> wrote: >> ...it's still available in the history e.g. >> https://github.com/apache/incubator-groovy/blob/576b3c5d6a7022ac4a8df1ef118666456ce627fb/MATURITY.adoc > > Of course, yes - I'll just copy its text to the "[graduation] Maturity > model-based assessment of Groovy for its graduation" thread on the > [email protected] mailing list, so it's available in those > archives. > > -Bertrand
