A bit of a different format for BathCamp in June. We’ll be cage fighting.
No.
Actually, it’s a sort of follow on from our previous BathCamp – a comparison of as many CMS systems as we can get people to talk about.
Obviously any comparison of CMS system is heavily caveated with an “it depends…” but nonetheless we think it’ll be interesting to hear from people talking about the good, the bad and the ugly of the systems they use.
The format of the talks will be “5 things I love about this CMS and 5 things I hate”, followed by time for questions and general CMS-like banter.
We’ve got the following lined up:
WordPress
Drupal
Expression Engine
Plone
PyroCMS
Perch
Umbraco
Defacto
17. Love #2
Buildout
Deployment, versioning, build, etc
18. [buildout]
extensions = mr.developer
parts =
productdistros
instance
zopepy
# Change the number here to change the version of Plone being used
extends =
http://dist.plone.org/release/4.2b2/versions.cfg
versions = versions
sources = sources
# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
http://dist.plone.org/release/4.2b2
http://dist.plone.org/thirdparty
# Add additional eggs here
eggs =
PIL
collective.cookiecontrol
# Reference any eggs you are developing here, one per line
# e.g.: develop = src/my.package
develop =
src/collective.cookiecontrol
20. ZODB
• Released in late 90’s -- yeah we’ve been
doing NoSQL since before your CMS was a
glint in your creators eye
• Transparent object persistence
• Full ACID-compatible transaction support
• Pluggable storages
77. Legacy Code
• When you’ve been around over a decade,
you accumulate a lot of code. The world
moves on
• Major refactoring going on Zope 4 = -20%
code