[Chandler-dev] fluid and unconstrained requirements

[Prajwal Kaflê]

I'm sure you guys read both a lot of negative and positive things about
Chandler. My purpose is not to bring out any negative feelings but to just
ask have an open discussion.

I was reading some blogs about Chandler and the overlapping theme in a lot
of them seem to be like the one I read below. Is there any validity to it?
What have we done to address it?

 <http://www.manageability.org/blog/stuff/chandler-failure>
 "My suspicion is that not beginning with a stable and static substrate, in
an environment with fluid and unconstrained requirements, is a recipe for
disaster."
http://www.manageability.org/blog/stuff/chandler-failure
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20080229/48da9404/attachment.html