Professional Documents
Culture Documents
Initial code
contribution
250 million phones shipped
250 different phone models
2009
100 million
phones shipped 2008 Nokia acquires
Symbian Ltd
Symbian Ltd was 2006
founded
1998
3
Members 2009
Expert teams
Staffed by Nokia and
Symbian Ltd to look at
specific problems Oversight by founding
members
What Infrastructure
is needed? How is the platform
Bug tracker, Mailing Lists, governed?
SCM system, etc. Feature & Roadmap,
How are roadmaps Architecture, UI and
created? Release councils
Gaps, unintended
consequences, some
things did not fit Helped give
Symbian a
GOOD START
8
Preparing the Code
3rd party IP and the initial contribution
9
The IP Challenge
12
The cultural challenge:
changing an eco-system
Eco-system: what to do?
A shock for the eco-
system
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
Major contributions
in the making
• 3 from Japan
• 5 from Nokia
• 7 otherwise
• More discussed at SEE
Contributions being
worked on …
17
Lessons learnt!
So far …
How are OSS projects normally created?
Idea
Proprietary
Mi
Incubator
Project
• Process takes between 2-24 months
• Project adds 2-3 committers
• Process requires a large amount of support
• Apache average: 14 months
19
How can you do this as
FAST as possible when
you have a HUGE initial
contribution?
20
Lesson: A STRONG FOUNDATION
Build
16 out of 134
Kernel:
Kernel,
beagleboard,
Security qemu
IDE,
hostenv,
etc.
24
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
+ =
Problems (which Big stake in builds sense of
people care about) solving these OWNERSHIP
26
Lesson: COMMUNITY REPRESENTATION
Councils:
• F&R
• Architecture
• UI
• Release
COUNCILS are
becoming
mechanisms
for
COMMUNITY
REPRESENTATION
27
Lesson: LET EVERYBODY INFLUENCE
28
Lesson: OPENESS
Open Management
Our community like the fact
that roadmaps, backlogs,
minutes, etc. are publicly
Be as open as you
available!
can
BUT
do not force your
Many are experimenting with community to be!
IDEAS – being open can lead
to embarrassment
Culture Change &
Worry to share information Cultural Collision
that can be used to deduce
trade secrets
29
Lesson: INCENTIVE STRUCTURE
Vendor Community
Neutrality
• Can I influence the direction of the community?
• Influence = protect investment
Closed Open
Development
30
We have a very good
chance of succeeding
31
S^1 & S^2 devices in 2009
SH‐04A
X6 5230 N97 Mini
Symbian is projected to be
the most used OS in 2012 &
2014
• Juniper Research
• Gartner 33
Questions
larsk@symbian.org
Twitter: lars_kurth
34