OSSG:Open Source doesn’t alwaysrepresent the best valueJanus Boye - email@example.comLondon, January 2010
Who is Janus Boye?• Founder of J. Boye – known for vendor-neutral blog,community of practice and conferences• 225 members, divided into several groups• Why community of practice: • Much to gain from sharing ideas • No “one correct route” • Frequent changes in priorities
Some of our membersAlfa Laval, Amnesty, Arup, Borealis,Carlsberg, City of Aarhus, Danfoss,Danish Agency for GovernmentalManagement, Elexon, EnvironmentAgency, European Patent Office, LEGO,Maersk, Medtronic, Nordea, OdenseUniversity Hospital, Specsavers,Swarovski, SWIFT, UNHCR, Unilever,University of Copenhagen, Wienerberger,WWF
AgendaConfusionOpen source issues 1. Support & Training 2. Risks 3. Requirements 4. Implementation 5. CommunityYour opportunity
An Open Source of Confusion True or False?Open source Commercial / Proprietary• Low cost • High cost• Pay for services • Pay for software• Ease of customisation • Difficult to customise• Open platforms • Proprietary platforms• Community support • No community support• Future proofing • Short-term• “Try before you buy” • “Buy before you try”
Clay Shirky“The bulk of open source projects fail, and most ofthe remaining successes are quite modest. Butdoes that mean the threat from open systemsgenerally is overrated and the commercialsoftware industry can breathe easy? Here theanswer is no. Open source is a profound threat,not because the open source ecosystem isoutsuccessing commercial efforts but because itis outfailing them. Because the open sourceecosystem, and by extension open socialecosystems generally, rely on peer production,the work on those systems can be considerablymore experimental at a considerable less cost,than any firm can afford”(from page 245 of the hard cover version)
Nick Carr“Simply put, it remains difficult, if not impossible, to draw any broad conclusions about ITs effect on the competitiveness and profitability of individual businesses”
1) Support & Training• Who will you call?• Quality of documentation
2) Risks• Early mover disadvantages• Who is responsible for bug fixing ?• Systems don’t last forever – who will help you when they die? • e.g. HyperContent, Mambo
Case: • Recognized that no system is perfect and meets all requirements • Selected Plone for initial scoping exercise with small integrator
4) Implementation• Significant cost factor• Would you implement yourself?
5) Community• What are your plans for engaging with the community?
Case: • Selected TYPO3 and decided to work with small integrator while building their own implementation skills • Attended TYPO3 conference and actively participates in community
Your opportunity1. You can save money with open source2. Engage with the community3. Look beyond technology when selecting a new vendor / system Make the right decisions
Sources of vendor-neutral inspirationCMS Watch - www.cmswatch.comContent Here by Seth Gottliebwww.contenthere.comGraham Oakes - www.grahamoakes.co.ukIntranetFocus by Martin Whitewww.intranetfocus.comJon On Tech – www.jonontech.comStep Two Designs - www.steptwo.com.au
Continue the conversation…• J. Boye Blog: jboye.com/blog• Community of Practice: jboye.com/community-of-practice• Email: firstname.lastname@example.org• Twitter: @janusboye• LinkedIn: http://dk.linkedin.com/in/janusboye