[Zope-CMF] Re: [dev] CMF 1.5 roadmap?

Chris McDonough chrism at plope.com
Tue Feb 24 12:41:14 EST 2004


I'd like to see Archetypes in there.  The reason I'd like to see it in
there is because:

a) It works very well and is quite stable, very well-written,
well-maintained, just generally a good piece of software all-around.
b) It already works with plain CMF.  You just need to plug it in to the
repository and maybe tweak a couple of things like stylesheets.
c) The authors (Ben Saller and crew) seem to be OK with it going in to
the core
d) I'd like to see people rally around CMF rather than balkanizing into
smaller groups.  It'd be good to take stock of work that other folks
have done and allow folks to share their respective burdens by
consolidating.  The Zope community is still too small for balkanization
to work in the long run IMHO.

I'm not sure if any of these reasons are compelling, really, and I can
understand why it might be more advantageous to leave Archetypes out of
the mix politically and practically.  That said, I think there's an
opportunity for consolidation here without much pain, and I think
Archetypes is tremendously useful and takes an substantial amount of
pain out of writing CMF applications.

There are some problems with this:

- CPS Schema is a competitor, and the CPS guys might have issues
  with it.

- Zope 3 Schema is a competitor.

- There really should be a representative equivalent of
  CMFDefault-written-with-Archetypes to make it clear how
  to write CMF applications with Archetypes.

- Dunno if there are any licensing/religious issues
  between the two camps (Ben & ZC, really) yet.  Doesn't
  seem like there are: Archetypes is BSD.  It would be up to
  Ben to choose to relicense it under the ZPL.

- C


On Tue, 2004-02-24 at 11:03, Tres Seaver wrote:
> yuppie wrote:
> 
> > The latest Zope releases look quite good, Zope HEAD seems to become 
> > stable again, Plone 2.0 and CPS 3.0 are in release candidate stage and 
> > even the sun is shining today. But something is missing: CMF 1.5.
> > 
> > What needs to be done to put the next CMF release on the track?
> 
> We need to do a scoping exercise:
> 
>    - Are there features not yet implemented for which we want to hold up
>      the release?
> 
>    - Are there "blocking" bugs in the collector?
> 
>  From that, we make a release plan.
> 
> My ambitions for the release have waxed and waned.  At this point, I 
> would like to include CMFActionIcons in the release, and add an 
> Epoz-friendly skin which uses both action icons and Epoz.  I haven't 
> thought about collector issues.
> 
> Anybody want to bid for other features?  Claim particular bugs?
> 
> Tres.




More information about the Zope-CMF mailing list