Asayopenbravowccommunityimperativenv 090419061800 Phpapp01

452 views

Published on

Do you use, or plan to use in the next budget year, an open-source project or product as an alternative to commercial software?

http://www.slideshare.net/mjasay/matt-asay-the-community-imperative-openbravo-world-conference-2009

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
452
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • On this slide, “none” indicates that no OSS projects for each of the categories will be implemented as an alternative to commercial software. Therefore, respondents will be using OSS in conjunction with commercial software. For example, 15% of survey respondents said they are not using OSS as an alternative to commercial software while 63% said they were using OSS operating system software, 54% for applications software, and 75% for infrastructure software as an alternative to commercial software.
  • Respondents were asked to select the top three most important reasons for using OSS software. This slide contains a summary of those results. Consistently across all eight countries, lower total cost of ownership (TCO) and reduction and development of cost-prohibitive projects were major factors for selecting OSS. This clearly indicates these areas are highly cost-sensitive. Another strong reason for using OSS was that it makes it "somewhat" easier to embark on new IT projects or software initiatives. This, too, was indirectly driven as part of cost arbitrage. In interviews and conversations at various events, many attendees indicated that they also use OSS as investment protection against a single vendor "owning" the entire IT department. Managers use several vendors by design; however, with the large number of acquisitions during the past few years, many multivendor IT shops now include only one vendor. Most managers agreed that a single-vendor IT shop was a bigger risk than using OSS alternatives, even in mission-critical applications. Respondents also indicated that the major business reasons for using OSS projects and components were faster time to market, with reduced R&D costs (with no need to “reinvent the wheel”). Users indicated they are able to locate quality components to address niche problems quickly and easily. This faster time to market better positions them to meet the unique demands and requirements of internal and external customers and, in many cases, provides the ability to avoid complex procurement rules and procedures.
  • 24/07/06
  • 24/07/06
  • 24/07/06 November 2002 - Gartner says Jboss “mature” for embedding February 2003 - Jboss 4.0. The rest is history March 2003 - CNET and other news outlets start to cover middleware as open source’s new hunting ground March 2003 - Jboss kicks off its partner program Novell and HP partnership deals in Q2 2004 - Started paying dividends 9-12 months later May 2004 - $10M investment from Accel, Intel Capital, and Matrix Unisys in February 2005
  • Asayopenbravowccommunityimperativenv 090419061800 Phpapp01

    1. 1. Openbravo World Conference The Community Imperative Speaker: Matt Asay, VP of Business Development, Alfresco Barcelona, April 19, 2009
    2. 2. Agenda <ul><li>Open Source Rising </li></ul><ul><ul><li>Market data on open-source adoption </li></ul></ul><ul><ul><li>Reasons for open-source adoption </li></ul></ul><ul><li>Community Mechanics </li></ul><ul><li>Openbravo’s Community Outreach </li></ul><ul><li>Community Begins with You </li></ul><ul><li>Concluding Remarks </li></ul>
    3. 3. Open source is now mainstream Source: Gartner 2008 Number of respondents = 274; Multiple responses allowed. Survey Question: Do you use, or plan to use in the next budget year, an open-source project or product as an alternative to commercial software? 53-55% to adopt open-source by 2010
    4. 4. But what about open-source ERP adoption? Source: Forrester, 2009 60% to adopt open-source ERP by 2010
    5. 5. Why open source? Source: Gartner Number of respondents = 274; Mean summary: Three responses allowed. Survey Question: Select your organization’s top three most important reasons for using open-source software.
    6. 6. But it’s not just about cost <ul><li>“ Open source software solutions will directly compete with closed-source products in all …markets.” </li></ul><ul><ul><li>85% of enterprises currently use OSS </li></ul></ul><ul><ul><li>45% use OSS for mission-critical applications (Continues to grow) </li></ul></ul><ul><li>Why? </li></ul><ul><ul><li>65% say open source has sparked innovation inside their companies </li></ul></ul><ul><ul><li>67% … for lowered costs </li></ul></ul><ul><ul><ul><li>“ Lower TCO and flexibility to launch and develop cost-prohibitive projects continue to be top reasons for using OSS” </li></ul></ul></ul><ul><ul><li>81% … for better quality software </li></ul></ul>Sources: Gartner (2008), CIO Insight (2006), IDC (2006) ‏ “ Open source produces better software.”
    7. 7. It’s also about (lowering) risk <ul><li>Most IT projects fail </li></ul><ul><li>Open source de-risks software acquisition: </li></ul><ul><ul><li>Try before you buy </li></ul></ul><ul><ul><li>Stop your subscription if the vendor stops providing value </li></ul></ul><ul><li>Worst case: </li></ul><ul><ul><li>Project dies and you’re out $xx,xxx or $xxx,xxx, not $x,xxx,xxx </li></ul></ul><ul><li>IT project failure becomes less probabilistic and less painful </li></ul>
    8. 8. … In many ways, open source is working 87% 92% 86% 82% 84% 82% 91%
    9. 9. So open source is being used in more mission-critical tasks Open source is becoming the heart of enterprise computing
    10. 10. Agenda <ul><li>Open Source Rising </li></ul><ul><li>Community Mechanics </li></ul><ul><ul><li>The myth of open-source community </li></ul></ul><ul><ul><li>How commercial open-source communities operate </li></ul></ul><ul><li>Openbravo’s Community Outreach </li></ul><ul><li>Community Begins with You </li></ul><ul><li>Concluding Remarks </li></ul>
    11. 11. It’s no longer about whether open source will succeed …but how (and which projects) The real differentiator going forward is community involvement Whether measured in terms of lines of code added or new projects, open-source growth is phenomenal Source: Dirk Riehle, SAP
    12. 12. <ul><li>Just what is “The Community” supposed to do? </li></ul>
    13. 13. Community mostly happens at the periphery of a project <ul><li><15 core developers do 85-100% of core development work </li></ul><ul><ul><li>1000/10/1 ( Users / Bug Reporters / Patch Submitters ) </li></ul></ul><ul><li>Community is difficult to achieve: </li></ul><ul><ul><li>72% of “open source developers” write code for others like themselves </li></ul></ul><ul><ul><li>Most projects (55%) get no outside involvement a t all </li></ul></ul><ul><ul><li>BUT…even big community projects are written by vendors </li></ul></ul><ul><li>The best place to solicit community involvement is in complements to a project, not the core </li></ul>Sources: Marten Mickos (MySQLUC 2005); O’Mahony & West, 2005; Mockus et al., 2005 The Shape of Community
    14. 14. Why doesn’t community work as advertised? <ul><li>Time </li></ul><ul><ul><li>Who has time to write (lots of) free software? </li></ul></ul><ul><ul><li>Answer: Those that are employed to do so </li></ul></ul><ul><li>Interest </li></ul><ul><ul><li>Who will take out the trash? </li></ul></ul><ul><li>Aptitude </li></ul><ul><ul><li>Writing an ERP system is very hard/not many people can </li></ul></ul><ul><ul><li>The higher up the stack you go, the fewer the developers </li></ul></ul><ul><li>Familiarity with project </li></ul><ul><ul><li>Poor documentation makes it hard to understand a project </li></ul></ul><ul><ul><li>Monolithic code base takes time to learn (M o st won’t bother) </li></ul></ul>
    15. 15. “ There is no upside to pushing freeloaders away.” Linus Torvalds, 2009
    16. 16. Community begins when self-interest meets software
    17. 17. Agenda <ul><li>Open Source Rising </li></ul><ul><li>Community Mechanics </li></ul><ul><li>Openbravo’s Community Outreach </li></ul><ul><ul><li>Modularity and the Firefox-ization of Openbravo </li></ul></ul><ul><ul><li>Openbravo Forge </li></ul></ul><ul><li>Community Begins with You </li></ul><ul><li>Concluding Remarks </li></ul>
    18. 18. <ul><li>Casual development depends upon modularity </li></ul><ul><li>Openbravo modularity enables community first, company second </li></ul><ul><ul><li>Start with Openbravo core, make it your own </li></ul></ul><ul><ul><li>Functionality, integration with 3 rd -party software, localization, etc. </li></ul></ul><ul><li>Community must derive significant value from Openbravo, and beyond Openbravo </li></ul><ul><ul><li>Commercial support from Openbravo </li></ul></ul><ul><ul><li>Commercial opportunities that happen beyond Openbravo, the company </li></ul></ul>Making Openbravo more like …Firefox Community starts when the company gets out of the way, and when a rchitecture facilitates an add-on community Openbravo’s Firefox moment in v2.50 <ul><li>>6,800 third-party add-ons </li></ul><ul><li>45 full-time developers…but: </li></ul><ul><ul><li>1,000 community code contributors; </li></ul></ul><ul><ul><li>>20,000 nightly testers and </li></ul></ul><ul><ul><li>>500,000 beta testers </li></ul></ul><ul><ul><li>>50 million daily users and >125 million total users </li></ul></ul><ul><li>Number of add-ons before Mozilla’s re-architecture? </li></ul><ul><ul><li>Roughly zero </li></ul></ul><ul><ul><li>Compare with Apple Safari and Microsoft IE, which also are weak on community </li></ul></ul>The Firefox phenomenon
    19. 19. Openbravo Forge: A place for community to begin <ul><li>Announced in early April </li></ul><ul><li>Openbravo Forge allows users to register projects and to have access to community/development tools, e.g., bug tracking, Wiki, forums, etc. </li></ul><ul><li>Makes it easier for the community to develop (public or private) industry vertical templates, modules and localizations </li></ul><ul><li>Additionally, Openbravo Forge allows the commercialization of Openbravo community products </li></ul><ul><li>Enables the community without controlling the community </li></ul>
    20. 20. <ul><li>Openbravo is architected for community. </li></ul><ul><li>Now it’s your turn. </li></ul>
    21. 21. Agenda <ul><li>Open Source Rising </li></ul><ul><li>Community Mechanics </li></ul><ul><li>Openbravo’s Community Outreach </li></ul><ul><li>Community Begins with You </li></ul><ul><ul><li>T he more you contribute, the more you benefit </li></ul></ul><ul><ul><li>Ask not … </li></ul></ul><ul><li>Concluding Remarks </li></ul>
    22. 22. Learning from J B oss’ community 2002 2003 2004 2005 2006 3X 2X 1.5X 3.5X
    23. 23. Openbravo: What does it mean for you? <ul><li>Openbravo </li></ul><ul><ul><li>Global QA </li></ul></ul><ul><ul><li>Leveraged development (Code, language packs, business processes, etc.) ‏ </li></ul></ul><ul><ul><li>Lowered barriers to trying Openbravo (means lower cost of sale) ‏ </li></ul></ul><ul><li>Partners </li></ul><ul><ul><li>Ease of customization, enhancements </li></ul></ul><ul><ul><li>Chance to participate with Openbravo in development </li></ul></ul><ul><ul><ul><li>Steer the roadmap in your favor </li></ul></ul></ul><ul><ul><li>Commercial opportunities extending the Openbravo platform </li></ul></ul><ul><li>Customers </li></ul><ul><ul><li>Co-development: Make it your Openbravo </li></ul></ul><ul><ul><li>Lower prices </li></ul></ul><ul><ul><li>Improved product (Performance, functionality, tailored to individual needs) ‏ </li></ul></ul><ul><ul><li>The more you contribute, the less the potential for lock-in </li></ul></ul>
    24. 24. Ask not what Openbravo can do for you…
    25. 25. Agenda Open Source Rising Community Mechanics Openbravo’s Community Outreach Community Begins with You Concluding Remarks

    ×