[Zope3-dev] Workflow Usecase

[Shane Hathaway]

Chris Withers wrote:
> Shane Hathaway wrote:
> 
>>First, you set up a version repository. 
> 
> 
> What's a version repository?

It's a Zope object that acts like a CVS repository.  You can check in 
objects, check out, update to a specific revision, etc.

>>the planned features.  Then you version all of your content (including
>>scripts, templates, etc.)  You set up three checkouts, one for each of
>>your stages (development, staged, and production).
> 
> 
> I think I need to know what a 'version repository' is for the above to make sense ;-)

Explained above.  To clarify further, a "checkout" in this sense is like 
a CVS sandbox, but sandbox is the wrong word since it implies people can 
change it at will.  Instead, people work in the development checkout and 
use a UI available from the development checkout to request that the 
objects be updated in the other checkouts.

>>You allow people to edit *only* in the development stage.
> 
> <snip>
> 
> A nice solution, but how would that stop people accidentally (or otherwise) deleting the
> object that was in production?

You just don't provide a way to do that.  You only give people access to 
the development stage.  From the development stage, users have access to 
a UI that lets them request changes to the other stages, but you control 
that access using something like workflow.

Shane