Downloaded 90 times
Future of Open Source CMS
- 1. Future of OpenSource CMS The Future of Open Source Content Management GilbaneSF Conference May 2010
- 2. Follow us onthe Future of Open Source CMS hashtag: #fosc
- 3. So what isthe Future of Open Source CMS?
- 4. 2000-2010: Proprietary ECMcontent silos era…
- 5. … and strongvendor lock-in
- 6. CMS Key Trend:Separation of Platforms and Applications/Products Content-Enabled Runtime Content Application Server Content Middleware Content Application Builder Content Management Products Composite Content Applications User Experience Content-Enabled Solutions CEVA IDE PaaS RIA Content Studio Personas Composite Content Platforms SaaS
- 7. I am anengineer Do you speak JEE/.Net? Does it work with Spring? Does it support JSR283? Where is the dev list? Where are the Easter eggs? CMIS rocks! A Composite Content Platform for Techies….
- 8. … todevelop Content-Enabled Applications for Practitioners
- 9. CMS are indeedTwo Distinct Products Addressing two audiences Which require two different Business Models
- 10. 1) Content-Enabled Productsand Solutions Reaching the Next Generation of Content-Enabled Applications
- 11. Increasingly Faster Paceof Innovations for Content-Enabled Applications
- 12. Personalized and UbiquitousContent Consumption Experience
- 13. Social Groups andWorkplaces
- 14. Personal and PortableThinkboxes you can keep all-along your Life
- 15. Ideation and MarketPredictions Rooms
- 16. New Ways toleverage your Social Intelligence
- 17.
- 18. Which content applicationswill be hot in the next years Who Knows? (Certainly not the CMS Vendors)
- 19. CMS Mission Statement:Ease the development of social-enabled, semantically-rich, visually appealing content-safe and Interoperable-ready Composite Content Applications Composite Development Tools Urgently Needed Y. BARON
- 20. 2) The Riseof Composite Content Platforms
- 21. But not thelist of Valued Added Content Services your developers can rely upon Structured, Unstructured, Videos, Office Files, Emails… all Content Objects are equal
- 22. Built-in Lifecycle Services:Any Content deserves a Retention Plan today
- 23. Built-in Semantic Services:TextMining into your information wealth
- 24. Built-in Social Services:Leverage your Interest Graph at best
- 25. Built-in Mashability Services:Reaching the Next Level of Content and Data Reuse
- 26. Buit-in Data PrivacyServices: Personal vs Corporate vs Open Data DataPortability Personal Data Content DRM Content Licensing Information Wallets
- 27. Content Enrichment ServicesAre the Backbone of tomorrow Composite Content Solutions
- 28. Publishing Services SocialNetworks Semanticity Information Access Content Interoperability and Open Standards Actionable Content Indexing Social Graph CMIS MultiChannel Communities File Plan Engagement & Collaboration Rules Web Mashability Library Services UGC Social Gadgets Portlets Mashups Query standards Related Content SocialRank Dashboards Activity Streams Scanning& Imaging Video Images (Coumpound) Documents Email Forms Semantic Lifting JCR Scripting Personalization Multi-variate Testing 2009: Heavy custom integration needed to develop any new Content Application Business Processing Workflow ECM Platform WCM Platform Portal Platform Social Platform Search Platform
- 29. Publishing Services SocialNetworks Semanticity Information Access Content Interoperability and Open Standards Actionable Content Indexing Social Graph CMIS MultiChannel Communities File Plan Engagement & Collaboration Rules Web Mashability Library Services UGC Social Gadgets Portlets Mashups Query standards Related Content SocialRank Dashboards Activity Streams Scanning& Imaging Video Images (Coumpound) Documents Email Forms Semantic Lifting JCR Scripting Personalization Multi-variate Testing 2010-2012: Document Centric vs Social Publishing Centric Platforms Business Processing Workflow Document-Centric Platform Social Publishing-Centric Platform
- 30. Publishing Services SocialNetworks Semanticity Information Access Content Interoperability and Open Standards Actionable Content Indexing Social Graph CMIS MultiChannel Communities File Plan Engagement & Collaboration Rules Web Mashability Library Services UGC Social Gadgets Portlets Mashups Query standards Related Content SocialRank Dashboards Activity Streams Scanning& Imaging Video Images (Coumpound) Documents Email Forms Semantic Lifting JCR Scripting Personalization Multi-variate Testing Business Processing Workflow Composite Content Platforms 2015: The best of all possible worlds under the same umbrella: utopia or soon a reality?
- 31. Conclusion: Merger ofApplication Servers and Content Stores Composite Content Apps Builder Agile Content Applications Will drive a new Generation of Composite Content Platforms RIA Content Studio Natively Interoperability Federated Content Explorer Friction-less Integration Data Portability
- 32. 3) How dothese trends impact Open Source CMS?
- 33. Open Source CMSfrom a Vendor perspective Cost Sharing Software Fondations « Software is not an asset, it is a liability » De-Facto Standards Free Viral Marketing
- 34. Pimp My « Information »Ride Custom Solutions No Vendor Lock-in Open Source CMS from a customer perspective Free Beers
- 35. Common Open SourceBusiness Model Pitfalls
- 36. Mixing Community Buildswith Freemium Editions Mixing OpenCore with Shareware 2.0 Mixing Developement Communities with Communities of Practice
- 37. “ The realvalue comes from being able to concentrate on differentiating, user-centered applications – those can be still developed in a closed way, if the company believes that this gives them greater value; but the infrastructure and the 80% of non-differentiating software expenditure can be delivered at a much lower price point if developed in a shared way “ http://carlodaffara.conecta.it/?p=42 Reality: User-centered applications are different from Infrastructure Nokia Maemo Platform
- 38. Layer your OpenSource Strategy by Lines of Products And find the right Value Proposition Labs Development Branch For the OS Community Stable Production Branch For Users Open Core Open Derivatives Freemium/Trial Edition Community Open Source Dual GPL/Commercial licensing Community Edition Community Edition Free Edition (Optional Support Program) Commercial Editions Usually Business-Friendly Licenses Commercial Open Source Proprietary Derivatives Free App-etitizers Commercial Editions Restricted Visible Source Proprietary license Proprietary Software
- 39. Let’s now applyit to the CMS Industry Labs Development Branch For the OS Community Stable Production Branch For Users Composite Content Platform Content Management Products Freemium/Trial Edition Community Open Source Dual GPL/Commercial licensing Community Edition Community Edition Free Edition (Optional Support Program) Commercial Editions Usually Business-Friendly Licenses Commercial Open Source Content-Enabled Applications/Solutions Free App-etitizers Commercial Apps Restricted Visible Source or proprietary license Proprietary Software
- 40. Sales Model ForPractitioners (Products) For Developers (Platform) Shared Infrastructure Libs Content Application Server Content-Enabled Solutions Apache Spring JBoss Content Studio RIA Builder Control and Monitoring Center 3rd Party Libs Terracotta Solution for Marketers Subscriptions Composite Content Platform & Runtime Content Management Products Solution For Information Workers DMS DAM WCM RM E2.0 Community OSS / Business-Friendly License Any Licenses Hybrid License / Prof. Open Source GPL/Commercial Online Communities Social Media Care SaaS Etc… Dashboards Indirect « Second-Level » OEM Subscriptions Social Workplaces Public Sites PaaS Perpetual Licensing Composite Content Applications Subscriptions
- 41. ( CompositeContent Platforms + Content-enabled Applications + xCM Product Family ) x Open Source _______________________ First-Class Content Solutions for Tomorrow
- 42.
Editor's Notes
- #5 Content Silos didn’t work (ECM would cover all needs for Fortune 1000). It would have work in an ideal world where all departments use the same technology. The problem is that proprietary silos aren’t interoperable. The other issue is the document (binary) centric approach of these systems –as opposed to open, structured and more granular content format combined to more flexible service oriented architecture which is today needed.
- #6 Pb is vendor lock in and minimal interoperability are linked. Initiatives such as CMIS are out there today because of customer pressure and because of competition
- #7 This is about the future: Solutions/Applications for Practitioners in green (CEVA: Content Enable Vertical Applications now CCA: Composite Content Application), Platform for Techies in blue: techy talk. Better split between Platform and Solutions which should result by different product offers
- #10 Le CMS isn’t one product, it is 2 products
- #11 In 2015, content applications will be independent of the content store and should be designed, developed and deployed more quickly. Ever-changing users needs. Disruptive trends (social, E2.0, new devices, …) combined with a tsunami/deluge of information will boost the development of Content-enabled Applications.
- #12 The fast rise of Composite Content Applications: “Heterogeneous content types enriched by various added value services & mashuped together to form an actionable application” Today a DMS or WCM Content Storage/Platform and Management are heavily coupled tomorrow they will decoupled and several distinct Content Applications will shared the same CP
- #13 Various examples: Dynamic and personalized Newspapers-styled content aggregator
- #14 Social Apps / SoCo Apps / Workspaces are also good example of next generation of heavily dynamic content-enabled applications.
- #15 But we could also think of personal thinkboxes (ex.: evernote, dropbox)
- #16 Or E2.0 ideation and market prediction spaces
- #17 Or to new ways to foster communication among employees
- #18 Or simply to create curated information hub to help better digest the ever-growing mass-volume of public-facing or enterprise-facing information
- #19 Is it the role of CMS to find and develop the next Killer Content-Enabled Applications? No.
- #20 But the CMS should provide all the required tools 1) to help more rapidly develop such new content-enabled applications (aka the Composite Content Platform) and 2) all the Content Management Products to help practitioners manage the created content assets wherever the content was created, whatever the content-enabled application is reusing them, until their end-of-life and from a secure manner.
- #21 This need for content-enabled applications lead us to the fast rise of Composite Content Platforms
- #22 Composite Content Developers do not want to split project any more according to the type of data they want to manage but according to the list of integrated, value added, content enrichment services they can access off the shelves.
- #23 Could you imagine today an E2.0 application without proper content lifecycle services? (but this is however still the case in most E2.0 offers)
- #24 Could you imagine managing TB of content without the properly integrated textmining services?
- #25 How could your developers socialize their content-enabled applications without being able to rely first upon some core social/interest graph services?
- #26 How could you rapidly develop new content or data driven applications without having access to some core mashability services?
- #27 Do you want to restart readressing all the user authentification and content authorizations problems just because you want to develop a new content-enabled applications?
- #28 Composite Content Platform should provide to the developers all this content enrichment services from day 1
- #29 Today most complex composite content applications still require the acquisition and integration of several expensive system. Too much time is spent on coupling these services together at the place of focusing on developing the business-oriented applications
- #30 Today we are assisting to a split between document-centric platform which are expanding on the Search, eDiscovery, RM, Case Management,… side and between the WCM, Portal, SoCo and other E2.0 vendors which are more oriented towards social publishing aspects.
- #31 But composite content platforms should unify all these trends into one single, service-oriented, content enrichment platform.
- #32 The merge of Application Servers (J2EE;…) / Web Applications (Servlets,…) and the one of Content Store (JCR) + Publishing frameworks will drive a new generation of Composite Content Platforms. They will favour the fast development of Content-enabled Apps + Provide all the tools (CM Product Families such as DM, WCM, RM, DAM,…) to ensure that all the generated content assets could be managed horizontally, from a cross content apps perspective, from the best manner. Content-enabled Applications will focus on the context and the use case while CM Products on the content assets lifecycle.
- #33 Lots of Open Source CMS out there. Could we identify certain core directions which will impact all of them?
- #34 From a vendor perspective, open source is still mainly about 1) cost-reduction and 2) free promotion
- #35 From a customer perspective this is mainly about 1) accessing to some free beers and 2) being able to customize their solutions without any vendor lock-in
- #36 But forever open source business model are trying to figure out how to find the right economical business model
- #37 Several common pitfalls today exist and have been stressed by the recent economical downturn and the need to more rapidly monetize certain open source investments. There are plenty of confusion today on mixing the community of developers with the community of business practices, the OpenCore with some promotional ShareWare Edition or giving nighlty builds as freemium versions. All these pitfalls create FUD around open source (not mentionning what happend to MySQL and the sudden risks raised by a movement which was pretending that because the source code was present, the software will be there forever even if the main contributor would disapear).
- #38 Furthermore not all software is equal. User-centered applications are not infrastructure librarires. Open Source in general is better at the kernel and system utilities level
- #39 Applied to a Commmercial/Professional Open Source business model, this should give such a table. Note the clear distinction between the Community and the Freemium Editions in regards of the Development or Stable branch of the code. Note also the clear distinction of the goal of each sub-product offers (Community open Source or Vendor-driven Commercial Open Source).
- #40 Applied to the CMS industry and merged with the trends previously presented this could give the following graph.
- #41 More specifically to the CMs industry we should assist to: - The fast rise of community open sourced Composite Content Platform - which will allow Web Agencies, SI and Customers to rapidly develop their Composite Content Applications - The whole managed by a serie of CM Products. The CM Product Suite is not a pre-requirement and ideally-speaking a DAM Product from one vendor could be used in parrallel of a WCM of another vendor and empower the same Content-Enabled Applications.
- #42 If you spice-up this business model with som Open Source magic powder this should give you the opportunity to create new disruptive business models or at least the opportunity to get the flexibility and agility required to develop some first-class content solutions to address your future content issues.