Re: [Cfengine-develop] Development plan / meeting

[Hugo Gayosso]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Luke A. Kanies" <address@hidden> writes:

> Design to stay within cfengine as much as possible; if we find that
> people are doing things like autogenerating cfengine code, we need
> to figure out why and address the design decisions that are forcing
> that.  I find it remarkable how many people generate cfengine code,
> and how many people consider cfengine a basic building block but
> wouldn't consider using it as their main framework.

I think this is a very important issue, but on the other hand in
cfengine's web page it says:

"Cfengine is designed to be a part of a computer immune system,"

which implies that it is a building block, not a framework, so maybe
the goal of cfengine should be something like this:

"cfengine is designed to be the framework for a compute immune
system".

Which would imply that if we want to build a compute immune system we
will have cfengine as the framework and other tools will provide help,
let's say use 'tripwire' for file system security/integrity, 'snort'
for intrusion detection, etc.

But we need to define what exactly we want cfengine to be, then start
working from there.


> > Many "complaints" are just not thinking straight.
> 
> I agree, but many complaints are also because cfengine makes certain types
> of operations far more difficult than they need to be.

Either more difficult or different, which I described in a previous
message as the "cfengine way".


> I think it would be very worthwhile for some of us to spend time
> combing the list archives and figure out what people consistently
> have to workaround, and then find ways to design those problems out.

I have had this same idea so I could provide some help there, but I
think we need to define exactly what is 'cfengine' or what we want it
to be as I asked a few paragraph before.


Greetings,
- -- 
Hugo Gayosso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+Yo4FMNObVRBZveYRAvlyAKCEFUiFexWLGOigS092RyZnHlN+ZwCfdnuG
8p+6p1xXLsJs13aN454yUvo=
=i877
-----END PGP SIGNATURE-----