[geeklog-devel] eWeek story on Open Source CMS

Dwight Trumbower dwight at trumbower.com
Thu Jan 23 10:43:20 EST 2003

> > 1)  Easy install
>Yeah, we have already started down this path with Jason's script

Is it easy without the script for those people that are using a shared host 
with no shell?

I think it is, I didn't have to chmod on to many folders.

> > 4)  Lack of version control??
>This is a bit fuzzy for me.  What do they want to version?  Stories?
>Documents? (I suppose I should read the article when I'm done with this)

A true CMS has version control on the stories, articles, and anything 

> > 5)  Too rapid release schedule making keeping up to date hard
>RedHat took an interesting approach.  They have the desktop stuff, right.
>TI is updated like every 5 months or so.  Then with Advanced Server they
>have a much longer release cycle. Could we do something similar?

Double edge sword for those that want/need more features. The key is to 
have an easier upgrade path.

 > 7)  Workflow apps

>Eewwww, that could get nasty.  Do we really want to get in the business of
>workflow?  If so, I admit I know nothing about implementing such systems
>and I would need help digging up such requirements.

Sounds like a plug in to me. Workflow has too many definitions from people. 
Workflow systems that I have worked with in the past are way to complex to 
even try to compete.

dwight at trumbower.com

More information about the geeklog-devel mailing list