Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Towards An Open Development Culture V1.0

The Symbian Foundation will share the lessons learned by itself and its contributor community, during the first months on its journey towards open software development. We will explore challenges and reflections on community building, open source leadership, collaboration, development and incubation processes as experienced in this ambitious open source endeavour.

  • Be the first to comment

  • Be the first to like this

Towards An Open Development Culture V1.0

  1. 1. Towards an Open Development CultureLars Kurth, Contributor Community<br />This talk is about sharing what we have learned in the last 8 months!<br />
  2. 2. A short history<br />Initial codecontribution<br />250 million phones shipped<br />250 different phone models<br />2009<br />100 million<br />phones shipped<br />2008<br />Nokia acquires Symbian Ltd<br />2006<br />Symbian Ltd was <br />founded <br />1998<br />Copyright © 2009 Symbian Foundation. Public<br />
  3. 3. We are …<br /><ul><li> An independent nonprofit open source organization
  4. 4. Membership based
  5. 5. Board of directors staffed by funding members</li></ul>3<br />
  6. 6. Members 2009<br />
  7. 7. Preparation work:<br />Preparation work:Seeding the creation of the Foundation<br />
  8. 8. Copyright © 2009 Symbian Foundation.<br />6<br />Planning the Foundation<br />Oversight by founding members<br />Expert teams <br />Staffed by Nokia and Symbian Ltd to look at specific problems<br />More than 100 people were involved<br />
  9. 9. 7<br />Looking to solve problems such as ...<br />What Infrastructure<br />is needed?<br />Bug tracker, Mailing Lists, <br />SCM system, etc.<br />How do different parts ~of the community work together?<br />Collaboration Process<br />What are the different open source roles?<br />Package Owners, Committers, etc.<br />How is the platform governed?<br />Feature & Roadmap, Architecture, UI and Release councils<br />How will the code base be structured?<br />System model and technology domains<br />How are roadmaps created?<br />AND MANY MORE …<br />
  10. 10. 8<br /> BUT:<br /> of course there were some issues !<br />Gaps, unintended consequences, somethings did not fit<br />Helped give Symbian a GOOD START<br />
  11. 11. 9<br />Preparing the Code3rd party IP and the initial contribution<br />Preparing the Code<br />3rd party IP and the initial contribution<br />After 10 years the codebase contained a big portion of 3rd party IP<br />Which could not be open sourced<br />40 Million Lines of C++<br />
  12. 12. The IP Challenge<br />40 million lines of code had to be checked for IP violations<br />Many false positives<br />Many benign cases (e.g. code copied from a book)<br />It took 6 months to identify all serious IP issues<br />16% of components had an instance of an IP issue<br />94 cases altogether<br />Affected code needed to be removed initially<br />Ultimately replace by open source friendly code<br />
  13. 13. Handling IP Holes<br />Copyright © 2009 Symbian Foundation.<br />11<br />Removing code left “dirty holes” – aka components that did not build.<br />Contribution, R&D License or non-core items(leave the hole)<br />Refactor code such that components build – “clean holes”<br />Fill the holes …(on average 10 per month)<br />
  14. 14. 12<br />Challenge:<br />negotiating IP issues<br />
  15. 15. The cultural challenge:<br />The cultural challenge:changing an eco-system <br />
  16. 16. Eco-system: what to do?<br />Raising questions such as …<br /><ul><li> Will Symbian still be around in a year?
  17. 17. What is the opportunity?
  18. 18. What is the risk?
  19. 19. How does the game change?
  20. 20. How do I adapt?
  21. 21. Do I need to change my business model?</li></ul>This takes time<br />Many eco-system companies<br />are concluding this process<br />Early birds are thriving<br />A shock for the eco-system<br />14<br />
  22. 22. Copyright © 2009 Symbian Foundation.<br />15<br />Community Leadership: in its Infancy<br />Solution: education, supporting, mentor and rewarding desired behavior!<br />Solution: foundation staff leading and act as role models<br />How do I find 130 open source leaders who know their technology?<br />Personal “change” challenges<br /><ul><li> Why would anybody want to contribute?
  23. 23. What do I need to do to be successful?
  24. 24. What support can I count on
  25. 25. What am I allowed / not allowed to do?</li></ul>I Can’t! Experts need to grow into open leaders over time!<br />
  26. 26. Copyright © 2009 Symbian Foundation.<br />16<br />Starting the Contributor Community<br />We had to learn what motivates contributions<br />Transfer the knowledge to the community<br />Transfer the knowledge to our open source leaders<br />All contributions satisfy a SELFISH NEED!<br />Show me the NEED<br />Show me the MONEY<br />
  27. 27. Contributions: Thank You !!!<br />17<br />Major contributionsin the making<br /><ul><li> 3 from Japan
  28. 28. 5 from Nokia
  29. 29. 7 otherwise
  30. 30. More discussed at SEE</li></ul>Initial contributions:<br />Smaller contributions just happen! Hard to track<br />Other contributions so far …<br />Contributions being worked on …<br />
  31. 31. Lessons learnt!<br />Lessons learnt!<br />So far …<br />
  32. 32. How are OSS projects normally created?<br />19<br />Idea<br />Proprietary<br />Mi<br />Project<br />Incubator<br /><ul><li> Process takes between 2-24 months
  33. 33. Project adds 2-3 committers
  34. 34. Process requires a large amount of support
  35. 35. Apache average: 14 months</li></li></ul><li>20<br />How can you do this as FAST as possible when you have a HUGE initial contribution?<br />
  36. 36. Lesson: A STRONG FOUNDATION<br />21<br />A strong team of community managers and<br />technology managers<br />An open source organization with some technical capability<br />And prove to community that the model works<br />And show opportunities<br />Can find and work withvendors who may want tocontribute<br />Can initiate projects<br />Because of results the community takesinitiative<br />
  37. 37. Copyright © 2009 Symbian Foundation.<br />22<br />Building and releasing the platform and development kits.<br />Solution: the open source Foundation delivers critical common goods<br />Many open source projects struggle with common goods<br />A variant of the Tragedy of the Commons<br />Testing for compatibility<br />Lesson: Common Goods<br />
  38. 38. 23<br />Members Companies<br />Using and contributing<br />SFL Package<br />EPL Package<br />Everybody<br />Using and contributing<br />A beta period towards going open source : <br />learn, fix & de-risk<br />Two stages to true Open Source<br />
  39. 39. Moving to the EPL<br />So far: learning how to EPL, such that ourcommunity can movefaster<br />Build<br />16 out of 134<br />Kernel:<br />Kernel,beagleboard, qemu<br />Security<br />IDE, hostenv, etc.<br />24<br />
  40. 40. Lesson: Two stage process<br />25<br />The Good:<br /><ul><li> Time to staff the foundation
  41. 41. Time for community leaders to learn
  42. 42. Time to resolve challenges
  43. 43. Time to build momentum</li></ul>The Bad:<br /><ul><li> Negative publicity
  44. 44. Negative sentiment from parts of the OSS community</li></li></ul><li>Lesson: LEAVE CHALLENGES<br />26<br />When the foundation started, significant parts of how it was to operate were still to defineCouncil members had some CHALLENGES to resolve<br />builds sense of<br />OWNERSHIP<br />Actually this wasa blessing!<br />Problems (which people care about)<br />Big stake in solving these<br />+<br />=<br />
  45. 45. 27<br />Lesson: COMMUNITY REPRESENTATION<br />COUNCILS are becoming mechanisms<br />for<br />COMMUNITY REPRESENTATION<br />Councils:<br /><ul><li> F&R
  46. 46. Architecture
  47. 47. UI
  48. 48. Release </li></li></ul><li>Lesson: LET EVERYBODY INFLUENCE<br />28<br />SIGs: Special Interest Groups<br />Sense of<br />OWNERSHIP<br />Symbian Idea Sitehttp://ideas.symbian.org/: <br />400 ideas added in a week<br />Working groups (e.g. UI migration working group)<br />BoFs and other interactive parts of our annual conference!<br />UI Brainstorm<br />
  49. 49. Lesson: OPENESS<br />29<br />Open Management<br />Our community like the fact that roadmaps, backlogs, minutes, etc. are publicly available!<br />Worry to share information that can be used to deduce trade secrets<br />Culture Change & Cultural Collision<br />Many are experimenting with IDEAS – being open can lead to embarrassment<br />Be as open as you can<br />BUT <br />do not force your community to be!<br />
  50. 50. Lesson: INCENTIVE STRUCTURE<br /><ul><li> Can I see roadmaps, influence the direction of APIs and the platform?
  51. 51. Influence = make the platform work for me
  52. 52. Can I influence the direction of the community?
  53. 53. Influence = protect investment</li></ul>Vendor<br />Community<br />Neutrality<br />Closed<br />Open<br />Development<br />30<br />
  54. 54. 31<br />Still lots to do and learn!<br />So far being part of this journey has been FUN, but also lots of HARD WORK!<br />We have a very goodchance of succeeding <br />
  55. 55. S^1 & S^2 devices in 2009<br />SH-04A<br />X6<br />N97 Mini<br />F-03A<br />F-01A<br />F-08A<br />N97<br />SH-06A<br />SH-05A<br />SH-06A Nerv<br />5230<br />5800 Express Music<br />5530 Express Music<br />5800Navi<br />Satio<br />SH-07A<br />SH-03A<br />SH-02A<br />SH-01A<br />F-02A<br />F-09A<br />F-04A<br />i8910<br />
  56. 56. Some data to close...<br />&gt;60% of these will be based on open source operating systems<br />Symbian is projected to be the most used OS in 2012 & 2014<br />In 2012 - 2014 there will be 372 - 525 million smart phones.<br />Open Source in Mobile is here to stay !!!<br /><ul><li>Juniper Research
  57. 57. Gartner</li></ul>33<br />
  58. 58. Questions<br />larsk@symbian.org<br />Twitter: lars_kurth<br />34<br />

×