Open Source solutions are becoming more commonplace in corporate IT, with two thirds of companies using Open Source today or planning to use it soon. We've all heard the hype: cheaper to buy, cheaper to run, cheaper to fix. Using Open Source software reduces your risks. But how does this translate to the world of Content Management? The advantages of Open Source systems go beyond simple cost savings. Content management by its very nature requires a significant level of customisation and integration to meet business requirements. By not prohibiting the inspection and modification of the source code, Open Source enables a level of flexibility not available with proprietary systems. Open Source enables you to leverage a culture of trust and openness, rather than secrecy. By having access to the source code, a customer can be safe in the knowledge that everything that the software vendor was intended to deliver can be independently verified. In this talk you will learn how the Open Source community works, how its distributed nature makes it more resilient, and how you can become a part of it and benefit. We will cover the key criteria to consider when evaluating which Open Source CMS is the right fit for your requirements.

1. Open Source and
Content Management
Matt Hamilton
Member of the Board, Plone Foundation
Technical Director, Netsight Internet Solutions
IMS 2008
4th Dec 2008

2. What is Open Source?
Software that is released with
source code under a license that
permits access to the code and
derivative works
IMS 2008
4th Dec 2008

3. Some notable OS projects
IMS 2008
4th Dec 2008

4. Open Source CMS landscape
IMS 2008
4th Dec 2008

5. Open Source CMS landscape
IMS 2008
4th Dec 2008

6. Why Open Source?
3 Key Reasons for Open Source in Content
Management:
– Better Fit
– More Transparent
– Lower Risk
IMS 2008
4th Dec 2008

7. Why Open Source?
Better Fit
– Closing the requirements gap
– Open Source provides a lower common denominator
IMS 2008
4th Dec 2008

8. Why Open Source?
More Transparent
– Auditability
– Access to source code invaluable for customisation
– Project / roadmap more transparent
IMS 2008
4th Dec 2008

9. Why Open Source?
Lower Risk
– Lower risk of 'dead-ends'
– Lower risk of failure
– Lower risk of takeover
– Empower IT department
IMS 2008
4th Dec 2008

10. Who is using Open Source?
Eighty-fve percent of companies are
already using open-source software,
with most of the remaining 15 percent
expecting to do so within the next year,
according to analysts at Gartner.
Gartner, Open-Source Impact on Application Software, Worldwide and Regional, Nov 2008
IMS 2008
4th Dec 2008

11. Who is using OS CMSs?
IMS 2008
4th Dec 2008

12. Evaluating an OS CMS
Without a vendor trying to pitch to you, how do
you evaluate all these different CMS systems?
– Does its features match what you need?
– Does the technology stack ft your organisation?
– How active is the community?
– How many companies are there out there to call on
for help and support?
– What add-ons/extensions are there?
– Documentation, books, training?
IMS 2008
4th Dec 2008

13. Evaluating an OS CMS
Prototype!
IMS 2008
4th Dec 2008

14. Evaluating an OS CMS
Prototyping
– No license fees, so low barrier to entry
– Plenty of consultancy companies to help you
– Money invested up front on evaluation is wise move
you would have just spend it on license fees anyways!
– Prototype specifc functionality you need. You want
custom content type for a report? You want users from
Active Directory? Show us!
– Can see through 'marketing gloss'
IMS 2008
4th Dec 2008

15. Community
IMS 2008
4th Dec 2008

16. Evaluating an OS CMS
Community
– How centralised is the project? Bus Number?
– How easy is it to interact with?
– Mailing lists
– Conferences, Sprints, etc
– Special interest groups
– Published books?
– Legal foundations? Licenses? Trademarks?
IMS 2008
4th Dec 2008

17. Evaluating an OS CMS
'Commercial Open Source'
– A project released under an Open Source licence,
but developed and supported by primarily one
company.
– A double edged sword?
– Does commercial support apply to OSS version of code?
– Risks of vendor takeover / failure
– Special interest groups
– Open Source code, but closed source mentality
IMS 2008
4th Dec 2008

18. Evaluating an OS CMS
“The health, maturity and stability
of an Open Source project is a direct
refection of the health, maturity
and stability of the community that
surrounds it.”
Open Source for the Enterprise, Dan Woods & Gautam Guliani
IMS 2008
4th Dec 2008

19. Community Support
IMS 2008
4th Dec 2008

20. Evaluating an OS CMS
Formalised Methods
– Business Readiness Rating (BRR)
– Open Source Maturity Model – Navica
– Open Source Maturity Model – Cap Gemini
– Method for Qualifcation and Selection of Open
Source software (QSOS) – Atos Origin
IMS 2008
4th Dec 2008

21. Formalised methods
Maturity Tests
– Criteria set out of the software to be assessed for
maturity. Usually a mixture of quantitative and
evaluative questions
Requirements Weightings
– Different tests weighted according to the relevance
of each test to the intended use (and users)
Scores Awarded
– Each item of software examined and given an
overall score indicating comparative merit and
readiness for deployment
IMS 2008
4th Dec 2008

22. Formalised methods
OSMM Weightings:
Aspect Score
Software 4
Support 2
Documentation 1
Training 1
Integration 1
Professional Services 1
TOTAL 10
IMS 2008
4th Dec 2008

23. Procuring an OS CMS
Do your homework
– Assess your own requirements
– Evaluate different systems
– Get consultant/integrators in to demo
Look at TOTAL costs
– Don't be afraid to spend some money in the
evaluation
Iterative Development
– Don't try to do too much too quickly
– Prototype
IMS 2008
4th Dec 2008

24. Thank you!
Questions?
or
come fnd me at the Plone stand, 349
or
matth@netsight.co.uk
IMS 2008
4th Dec 2008