The page template file selected for this page cannot be found on the server.

Please contact the system administrator
open source and open source cms products

Hooray for Open Source! Even better, hooray for Open Standards! And no, they are not the same thing.

Open Standards, can be read as open protocols, and Open Source can be read as open code.

Apache webserver is Open Source code, that benefits from the Open Standard, HTTP. However the proprietary (non Open Source) webserver Microsoft Internet Information Services (IIS) also benefits from the Open Standard, HTTP.

Again, the Open Source Web Browsers
Firefox and Mozilla benefit from the Open Standards of HTML, CSS, XML and JavaScript. So too, do the proprietary Web Browsers, Internet Explorer and Apple's Safari.

Komodo CMS itself is built utilizing Open Source and Open Standard tools including the Linux Operating System, the Apache Web Server, the PHP Development Language and the MySQL Database, all Open Source and all reliant on Open Standards.

So why isn't Komodo CMS an Open Source solution?
At the heart of the Komodo CMS philosophy are three key concepts. Firstly, our users do not have to be developers to use the software. Secondly, our users do not have to be designers to use the software. And third, the features and cost of the product are transparent and inclusive.

Without drifting into a sales pitch, Komodo CMS is attractive to people who do not want to get side tracked with technical or design based issues and want to know upfront what they are getting and how much it will cost.

The problem with Open Source CMS?
Perhaps an illustration will work best. The developers of Komodo CMS are members of the Open Source Community for Linux, Apache, PHP and MySQL, and Komodo CMS is a member of the Open Source Industry Australia. We actively contribute to the furtherance of these platforms. We immerse ourselves in the these development communities and trawl for advice, and we live with the occassional shortcomings of these products knowing that we are a part of these communities and have a long-term vested interest in continued heavy involvement. That is our job and part of our product!

Now, if you are thinking of an Open Source CMS solution, you would do well to ask yourself the following questions. Do I want to immerse myself in the product's community? Do I want to learn new skills related to sustaining this new evironment? Am I happy to self support or support through mailing lists? How many times am I going to deploy this application?

If you make a living from web design or software coding and want to become involved with an Open Source community, and from this involvement and education you intend to roll-out significant numbers of websites, then Open Source may be your answer. Of course you could always partner with a proprietary CMS product as well, see our
Partner Program as an example.

But Open Source is FREE!
Free you say? How much is your time worth, learning an Open Source toolkit, becoming involved in the community and customising the product to suit you needs - all this before you even start editing your webpage(s).

How about support, technical assistance and design. Oh, and if you don't want to do all of this new found work yourself, then is the person you employ, by definition a
CMS Expert or Consultant going to do the work for free? Perhaps they will charge you an hourly rate for basic development and deployment work that is included in most proprietary systems. If you are making the decision financially, make sure you look at total cost of ownership (TCO) and all of your internal costs as well.

Of course upgrades, support, training, and measurable outcomes are often more difficult (read more money) with Open Source and in many cases there are significant speed of deployment issues.

You sound pretty hard on Open Source?
Yes and No. We are Open Source junkies, using the LAMP (Linux, Apache, MySQL, and PHP) environments as our base. We don't however expect our customers to have to do what we do, and we would rather charge a fixed and established price than an unknown rate based figure.

For most organisations, focussed on their core competencies and making money from what they do best, Open Source is an unwelcome and potentially expensive distraction. If however, what you do best also happens to marry nicely with dabbling in an Open Source application, then jump in and have fun. There really are some great Open Source CMS products out there, there are great kit homes, and brew it yourself beers as well. Geeks need only apply!

At the Operating System and core delivery platform level, we are the strongest of Open Source supporters. After all, this is the domain of the Geek, and open source provides great benefits and stops one or two Geeks running away with all the money. Sorry Bill! At the end-user application level however, in our humble opinion, the benefits of Open Source are not sufficient to outweigh the negatives.

Open Standards, that is another matter entirely. Transparency, protocols, easier integration and standards, standards, standards, is something we can all benefit from.

As a final note, the Open Source debate is a passionate one, and many would disagree vigorously with the comments made here. Do a web search on 'Open Source and Open Standards' and you will get an inkling of the level of conversation and debate and the scale of this 'war'.

For those reading this who wish to comment, please feel free to email
with your input (don't forget to mention that it relates to the Open Source page). I will post selected content from the best (most educational) emails below this paragraph.

Comments posted here (only well constructed and well mannered posts will be included).