[Zope-CMF] One or two products?
Chris Withers
chrisw@nipltd.com
Mon, 25 Nov 2002 16:59:18 +0000
Yuppie wrote:
> First I'll propose some definitions:
>
> CMFCore:
> - package (= Zope Product) of basic CMF modules
> - required by all other CMF packages
Yep.
> CMFDefault:
> - optional package
> - example implementation of CMF
> - the Dogbowl
Yes.
> - starting point for small projects and newbies
Nah, Plone seems much more common nowadays...
> CMF*:
> - optional package
> - implements special features or a complete cms
> - some of these packages may depend on others
Yep, although I really would like to see as few of these as possible, to keep
the installation burden to a minimum.
> I think CMF should be distributed as a set of Zope Products:
> - CMFCore
I think this should be labelled "The CMF"
> - CMFDefault
I'd prefer this to be called "CMFDemo"
> - other CMF packages maintained by ZC
> (That's just like it is. And yes, I'd also like to have DCWorkflow as
> part of this distribution.)
I think DCWorkflow belongs in CMFCore.
> But on the other hand, trying to use my definitions there is not much
> left for CMFDefault.
As it should be :-)
This is a list of CMFDefault imports:
>
<snip>
As far as I could see, all of those should have been in CMFCore.
cheers,
Chris