On 20-May-06, at 2:05 PM, Ashok Hariharan wrote:
the 2.9 -> 3 transition is a concern...but there seems to be a
migration
path,
at least in the roadmap.
There is, but this is why legacy support is a problem. For example,
extensions I wrote for Plone 2.0 no longer work in 2.5. The patches
are minor, but they do require effort to track down the API changes.
The Plone community doesn't have the resources to finish their
migration and simultaneously keep legacy support stable. The way I
used to handle this was by running two instances all the time, one
stable and one bleeding edge. I had been off this for the past year
due to other priorities, but have started tracking again this month.
Unfortunately, this also means that a company using Plone for
projects can't do it as a one-off effort. The project moves too fast
for that to be feasible.
What do you mean by the Zope wall?
The learning curve. With Archetypes you may get to a point where
Archetypes no longer has the answers. You'll have to peek under the
hood, and for that, will need a fair understanding of Zope architecture.
Agreed...but, I am trying to explain that to people who havent really
worked with technology other than as users!
(one of the powers that be uses wordpress for an intranet blog....and
believes anything can be done on it...)
Lots of people use Movable Type as a full fledged CMS, so it may be
possible to do that with Wordpress too. You'll miss out on bells and
whistles like fine grained access control that true CMSes offer though.
--
Kiran Jonnalagadda
http://www.pobox.com/~jace
