[Zope-CMF] Sneak preview - workflow

[seb bacon]

Shane,


> It can be hard to tell what's a core feature and what's not--but
> I think you're right, workflow is close to the core.

I find it all very confusing.  The distinction between core and
mantle (or something ;) seems to be crucial to the question of what to
keep and what to share, and I'm not even sure why, although I
instinctively understand.  

On the one hand:
> OSS is no longer an experiment for us.  It has been proven to work.

On the other:
> Essentially we intend to use CMF as the basis for most consulting
> engagements.  In fact, that's what drove the creation of CMF.

So, how do you decide what to keep to yourselves?  
Is there any kind of standard or is the decision ad hoc?  Has the fact
that you don't release all your code been proven to work, too? 
I'd be interested to know how many resuable product components DC have
developed which they haven't released, if you are able to tell us.  I
imagine they include things like PDF documents, Word Documents, etc,
things which the community have developed independently?

I think it's probably important in the interests of good communication
to make decisions like these as understandable as possible.  And as
simple to make as possible.

> I think pluggable, dynamic workflow is going to change the way products
> are written.  It's parallel to the "new religion" Jim has been talking
> about.
> 
> http://www.zope.org/Members/michel/Components/Components/NewReligion

I'll drink to that.  In fact I'm off down the pub right now. 

Cheers,

seb