Re: [Cfengine-develop] Development plan / meeting

[Mark Burgess]

> 
>> Anything else is open to discussion.
> 
> In the past few weeks, when users have said, "Can I do this", I've
> replied, "No but here's a patch to let you do it." I'm not sure this
> is the best way to manage the inclusion of features. How do we want
> to do it without formalising the process too much?
> 

We need a procedural checklist:

 - is it gratuitous functionality or of general interest?
 - is it convergent?
 - does it confict with existing code/principles?

I think cfengine needs to stay as small as possible. I agree that
many command-line options can now be eliminated. All tidying is 
useful.

A general principle:

 Don't give users what they ask for, give them what they need.

Many "complaints" are just not thinking straight.

M

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~