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