open source and content management (+audio)

IMS 20084th Dec 2008

Open Source and Content Management

Matt HamiltonMember of the Board, Plone Foundation

Technical Director, Netsight Internet Solutions


What is Open Source?

Software that is released with

source code under a license that

permits access to the code and

derivative works


Some notable OS projects


Open Source CMS landscape


Why Open Source?

3 Key Reasons for Open Source in Content Management:

– Better Fit– More Transparent– Lower Risk


Why Open Source?

Better Fit– Closing the requirements gap

– Open Source provides a lower common denominator


Why Open Source?

More Transparent– Auditability

– Access to source code invaluable for customisation

– Project / roadmap more transparent


Why Open Source?

Lower Risk– Lower risk of 'dead-ends'

– Lower risk of failure

– Lower risk of takeover

– Empower IT department


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


Who is using OS CMSs?


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?



Prototype!



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'


Community



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?



'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



“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


Community Support



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


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


Formalised methods

Aspect Score

Software 4

Support 2

Documentation 1

Training 1

Integration 1

Professional Services 1

TOTAL 10

OSMM Weightings:


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


Thank you!

Questions?

or

come fnd me at the Plone stand, 349

or

[email protected]

open source and content management (+audio)

Technology