Building Innovation with Open Source Approaches

1,439 views

Published on

My talk at TransferSummit 2010.

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,439
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • We let our users drive the development Shorter planning cycles than normal Balance vision with demand We do not have a separate support team Developers provide support We do have a separate QA team But developers test their systems thoroughly Hugely automated test and build We do not have a separate training/consultancy team Our customer architects contribute to the code Our developers do training and on-site consultancy We let our users drive the development Shorter planning cycles than normal Balance vision with demand We do not have a separate support team Developers provide support We do have a separate QA team But developers test their systems thoroughly Hugely automated test and build We do not have a separate training/consultancy team Our customer architects contribute to the code Our developers do training and on-site consultancy
  • We do everything on mailing lists Almost all our mailing lists are open Architecture Dev lists We get mails from concerned people who think there is a problem with our infrastructure Open Bug Tracker Open build processes What is closed? Customer support system Support mailing list Sales and marketing
  • Building Innovation with Open Source Approaches

    1. 1. How to build innovation using Open Source approaches Paul Fremantle [email_address] @pzfreo / Twitter CTO and Co-Founder, WSO2
    2. 2. Me <ul><li>Open Source </li></ul><ul><ul><li>Wrote my first public domain code in 1992 </li></ul></ul><ul><ul><ul><li>Posted on FidoNet </li></ul></ul></ul><ul><ul><li>First involvement with Apache in 2000 </li></ul></ul><ul><ul><ul><li>Spoke at ApacheCon London 2000 </li></ul></ul></ul><ul><ul><li>Member of the ASF, on several PMCs </li></ul></ul><ul><ul><li>VP/Apache Synapse </li></ul></ul><ul><li>Work </li></ul><ul><ul><li>9 years at IBM, leaving as a STSM in WebSphere Architecture </li></ul></ul><ul><ul><li>Set up WSO2 in 2005 </li></ul></ul><ul><ul><li>Named Infoworld CTO 25 in 2008 </li></ul></ul><ul><ul><li>Technical team of ~60 people </li></ul></ul><ul><li>Home </li></ul><ul><ul><li>Two children 13 and 9 </li></ul></ul><ul><ul><li>Play the tin whistle </li></ul></ul><ul><ul><li>Occasional blacksmith </li></ul></ul>
    3. 3. Themes for this talk <ul><li>Open Source / Open Development </li></ul><ul><li>What is an Open Source company? </li></ul><ul><li>Does Open Source promote innovation? </li></ul><ul><li>What can companies learn from Open Source? </li></ul><ul><li>Usability isn’t just about UIs </li></ul><ul><li>What have we (WSO2) done that we think is innovative? </li></ul>
    4. 4. How do you encourage innovation?
    5. 6. A short history of WSO2 <ul><li>Founded in August 2005 </li></ul><ul><ul><li>By 3 Apache Members </li></ul></ul><ul><ul><li>US, UK, Sri Lanka </li></ul></ul><ul><li>Three core thoughts: </li></ul><ul><ul><li>Lean software based on standards and interop </li></ul></ul><ul><ul><li>Open Source </li></ul></ul><ul><ul><li>Global company with core team in Sri Lanka </li></ul></ul>
    6. 7. A view of Open Source companies – There are No Open Source companies <ul><li>Only companies that make money: •    via expertise in consultancy •    hoarding copyright ownership for a big sale •    providing additional value on top of OSS products •    licensing fear, uncertainty and doubt </li></ul><ul><li>(choosing GPL to make users who fear GPL pay) </li></ul><ul><li>Henri Yandell commenting on my blog: http://bit.ly/c7xOow </li></ul><ul><li>My response: http://www.sdtimes.com/link/34351 </li></ul>
    7. 8. Bait and Switch
    8. 9. What does is mean to be “Open Source” <ul><li>Publish code under an OSI approved license </li></ul><ul><li>Have some part of your code Open Source </li></ul><ul><li>Support Open Source software </li></ul>
    9. 10. <ul><li>Cost </li></ul><ul><li>Differentiation </li></ul><ul><li>Focus </li></ul>
    10. 12. WSO2’s differentiation is focus on all things Open Source <ul><li>Open Development </li></ul><ul><li>Community </li></ul><ul><li>License </li></ul><ul><li>Processes </li></ul><ul><li>People </li></ul>
    11. 13. Why the Apache License?
    12. 14. Usability U.S. Mission Photo: Eric Bridiers 
    13. 15. Open Source Processes Photo http:// garth.vox.com /
    14. 16. Open Development
    15. 19. The suits are not (completely) in charge <ul><li>Everyone is encouraged to challenge </li></ul><ul><li>Product managers are often younger than their team </li></ul><ul><li>Engineers pitch in on marketing and sales issues </li></ul><ul><li>Not all experienced hires fit into this well </li></ul>
    16. 20. Image: Mike Cooter
    17. 22. eBay
    18. 24. WSO2 Carbon
    19. 26. Cloud Native
    20. 27. WSO2 Stratos: Platform as a Service
    21. 28. http://cloud.wso2.com
    22. 29. Summary <ul><li>Choose the right license </li></ul><ul><ul><li>…. But the license is a tiny portion of being “Open Source” </li></ul></ul><ul><li>Innovation is not just inventiveness </li></ul><ul><ul><li>The team needs to focus on real needs </li></ul></ul><ul><li>Try to disrupt yourself </li></ul><ul><ul><li>It may not work, but its certainly fun </li></ul></ul><ul><li>Meritocracy breeds innovation </li></ul>
    23. 30. Thank you

    ×