> I'll be honest, I have no idea why they
> think they have to do it, but they do it.
I suspect it is because projects are motivated to graduate and believe
that one or more people on the IPMC with -1 their graduation if they
do not complete the model and put a check mark in every box.
I
Hi Bertrand,
On Mon, Sep 4, 2017 at 4:54 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:
> Hi John,
>
> On Fri, Aug 25, 2017 at 9:11 PM, John D. Ament
> wrote:
> > ...Its unfair for us to put some stake in the ground expecting podlings
> to
> > match up 100%
On Mon, Sep 4, 2017 at 4:34 PM, Jim Apple wrote:
> ...I think the current Model has a number of vague statements that are
> unlikely to be interpreted consistently without clarification. For
> instance "The project is open and honest about the quality of its
> code."..
On Mon, Sep 4, 2017 at 7:26 AM Shane Curcuru wrote:
> Bertrand Delacretaz wrote on 9/4/17 4:54 AM:
> > Hi John,
> >
> > On Fri, Aug 25, 2017 at 9:11 PM, John D. Ament
> wrote:
> >> ...Its unfair for us to put some stake in the ground expecting
> It's *very* helpful to have podlings consider their growth using some
> form of structured and consistent criteria, so IPMC (and board) can
> consider how different podlings see themselves compared to past podling
> history.
I think the current Model has a number of vague statements that are
Bertrand Delacretaz wrote on 9/4/17 4:54 AM:
> Hi John,
>
> On Fri, Aug 25, 2017 at 9:11 PM, John D. Ament wrote:
>> ...Its unfair for us to put some stake in the ground expecting podlings to
>> match up 100% on the questions. Many of the questions are subjective - is
>>
Hi John,
On Fri, Aug 25, 2017 at 9:11 PM, John D. Ament wrote:
> ...Its unfair for us to put some stake in the ground expecting podlings to
> match up 100% on the questions. Many of the questions are subjective - is
> the code easy to discover? respond to bug reports in a
Hi -
I think that the model is a good measure and the development of it was an
excellent example of the group dynamic in using a wiki. It is a list of best
practices. If a podling goes through the process then we ought to treat it as a
fair effort.
I think that it would be worth applying a
(changing subjects to avoid confusion in RocketMQ's discussion)
I've been pretty explicit about my disdain in the past over the use of the
Apache Project Maturity Model. The model describes an ideal world that all
projects should strive for, but I would be surprised if many projects
passed it.