From the Eclipse Foundation to the Symbian Foundation

Copyright  Symbian 2009
Running a Foundation to Contain Your Code
David Wood, EVP Research, Symbian Ltd
The Eclipse Foundation
The Symbian Foundation

The Symbian Platform
• Symbian OS is the market leading Smartphone OS
• Mature and most widely deployed platform
• Competitive products in mid- and high-end devices
• Operators and developers embrace Symbian OS
7 device manufacturers
> 250 million devices, > 250 device models
> 250 operators
Tens of thousands of apps, 4 million developers
Now becoming Open Source via the Symbian Foundation

Copyright  Symbian 2009 Page: 3
The (approximate) scale of the solution
40 million lines of code (device/tools/test/PC)
450,000 source code files
45,000 directories of source code files
2000 software components
97 packages
12 technology domains
1 mobile operating system

LG KT615
DoCoMo Prime F-01A
by Fujitsu
DoCoMo Prime
SH-01A by Sharp
New phones shipped during November 2008
Samsung I 7110
Nokia 5800
Express Music

entertainment
business health
more…
Huge mobile opportunities
devices that make
all users smarter
enchanting consumer
experiences
rich mobile gateway
to the digital world
extra memory
journalism
extra senses: location,
motion, eyes, ears…
education
The mobile devices of the near future will be
much more powerful and much more useful
than even the best mobile devices of today
+make
society
smarter

Challenges for developers
Batteries drain too quickly
Small screens,
small keyboards
Security and privacy issues
Larger data causes
processing delays
Complexity
Applications difficult to use
Hard for users to find functionality
Delays in phone development projects: quality suffers
Applications fail to run well
when moved to different
device or to different network
Significant mobile challenges

Larger data causes
processing delays
Challenges for developers
Batteries drain too quickly
Small screens,
small keyboards
Security and privacy issues
Complexity
Applications difficult to use
Hard for users to find functionality
Delays in phone development projects: quality suffers
Applications fail to run well
when moved to different
device or to different network
Solving mobile challenges
Openness:
Create/Embrace an ecosystem
Deep challenges and rich
opportunities need very many
developers working on them
Open Source:
Not just innovation
but deep community innovation
Symbian
Foundation

The claims of Open Source Software
• Faster time to market
• More eyeballs looking at code, hence higher quality
• Lower barriers to entry, hence greater innovation
• Lower barriers to collaboration
• Lower license fee
• The tide of history…
And specifically, about Linux:
• Better APIs?
• A larger ecosystem – including better tools
But: Many mobile
phone companies lost
huge amounts of
money pursuing open
source solutions

Copyright  2009 Symbian Software Ltd. Page: 10
Predicting the success of open source
• “I expect the open-source movement to have essentially
won [in] software within three to five years”
… Eric Raymond, “Cathedral and the Bazaar”
… 1999
… (And re-stated in 2001, with the dates clarified as “2003-2005”)
• “Windows 2000 will not ship in a usable form.
(At 60 million lines of code and still bloating, its
development is out of control)”
… “Windows 2000 will be either canceled or dead on arrival.
Either way it will turn into a horrendous train wreck, the worst
strategic disaster in Microsoft's history.”
Over
Woops!?
Or is it just a question of timing?

Incremental
improvement
Disruptive
improvement
Productivity
Disruptive trends
Time
Sales
Disruptive
technologies
are hard to do
business with!
Inspired by:
Clayton Christensen
Innovator’s Dilemma
It’s hard to:
•Read the trends correctly
•Convince customers to switch
•Allocate enough internal focus

Symbian Confidential Internal
Market Report: Sea Change in the Tools Industry
Symbian Product Manager, 12 August 2004
News from [several companies], and
developments around the opensource Eclipse
IDE platform, indicate a sea change in the
tools industry…
It is recommended that Symbian respond by
wholeheartedly embracing the Eclipse
platform…

Some highlights of Eclipse adoption by Symbian
• Carbide family of IDEs for Symbian OS is Eclipse-based
… Launched in 2005
… Used by all Symbian customers & development partners
• Roadmap of improvements
… Latest released version is Carbide v1.3.2 based on Eclipse CDT 4.0
• Symbian is Add-in Provider member of Eclipse Foundation
… Has committers for the DSDP and CDT projects
• Increasing number of developer tools are Eclipse plug-ins
… Used both in-house and in the wider community
… Example: SAW (Symbian Analysis Workbench)
• S60 3.2 phones contain EPL code
… eSWT UI toolkit is part of the MIDP environment on all 3.2 and later
S60 devices
… This may be the largest install base for EPL based code

2004 2005 2006 2007 2008
First technical
engagement
with C/C++
development
tools (CDT)
project
Symbian joins
Eclipse
Foundation
First Symbian
contributions
enabling
Carbide.C++ build
features for
Symbian OS
Symbian’s
first
committer
(DSDP)
Symbian
hosts first
plug-in fest
Key Symbian CDT
contributions:
• Template Engine
• Indexer re-write
Contributions to
DSDP target
management
project enabling
Remote System
Explorer
Symbian’s
second
committer
(CDT)
…
Contributed
Doxygen
support to CDT

The first Eclipse Pluginfest

• Appreciation of the power of a well-governed, meritocratic,
open source community
… Generates lots of innovation
… Support a variety of business models
… Competitors co-exist: Community grows
• Gave Symbian world more confidence in
the potential to adopt a similar model
… Best principles of open source
… Licence (EPL) plus governance
… Meritocratic yet also business-friendly
… Generate lot of innovation
… Grow the community
Developer
tools system
Mobile device
operating system

Evaluating the claims of Open Source Software
• Faster time to market
• More eyeballs looking at code, hence higher quality
• Lower barriers to entry, hence greater innovation
• Lower barriers to collaboration
• Lower license fee
• The tide of history…
And specifically, about Linux:
• Better APIs?
• A larger ecosystem – including better tools
Difficulties at scale and pace
Fragmentation is easy,
Integration is hard
There can be many
other costs of development
Can be copied (eg PIPS/OpenC, Qt)
Not
conclusive
No panacea – but can be powerful!
Not necessarily a better OS

Fragmentation is easy
Integration is hard
Fragmentation is a polite word for chaos

The six laws of fragmentation
1. Fragmentation can have very bad consequences
… Even though there can be good consequences too
2. Open (or Community) Source makes fragmentation easier
3. Copyleft Contracts can help minimise fragmentation

The 9 “popular” OSI-approved licenses
• New and Simplified BSD licenses
• MIT license
• Apache License, 2.0
• Mozilla Public License 1.1 (MPL)
 Common Development & Distribution License (CDDL) (Sun)
• Common Public License 1.0 (CPL) (IBM)
 Eclipse Public License (EPL)
• GNU Library or “Lesser” General Public License (LGPL)
• GNU General Public License (GPL) (FSF)
“Academic” / “Permissive”
“Weak copyleft”
“Strong copyleft”

Weak vs. strong copyleft
• Modifications and derived works permitted
• License must not restrict other software that is
distributed along with the licensed software
Developer 2
Product 2
Source 2
Developer 1
Source 1
Product 1
L1
L1!

Weak vs. strong copyleft
• Modifications and derived works permitted
• License must not restrict other software that is
distributed along with the licensed software
Developer 2
Product 3
Source 3
Developer 1
Source 1
Product 1
L1
L3!
Product 1
Product 4

Three definitions of weak vs. strong
1. Focus on “file-level copyleft” (vs. “projects”)
… “Any changes to MPLed files, or new files into which MPLed code has
been copied, are Modifications and so fall under the MPL. New files
containing only your code are not Modifications, and not covered by
the MPL” – MPL FAQ
2. Focus on “module-level copyleft”
… “For clarity, merely interfacing or interoperating with Eclipse plug-in
APIs (without modification) does not make an Eclipse plug-in a
derivative work” – EPL FAQ
3. “For library use” (LGPL) vs. “For general use” (GPL)
… LGPL: Software that links to the library can have a different license
… GPL: Software that links to this component must also use GPL
… FSF say they prefer people to use the GPL

Motivations for and against strong copyleft
Developer 2
Product 3
Source 3
Developer 1
Source 1
Product 1
L1
L3!?
Product 1
Product 4
• Developer 2 wants to be able to make money from royalty fees
– or preserve some trade secret in Source 3
• Developer 1 wants to encourage innovation (from Developer 2)
• Developer 1 may want to avoid “hoarding” and “fragmentation”

4. Fragmentation can’t be avoided simply by picking the
right contract (and enforcing copyleft)
… The integrators may reject changes made by individual developers

Fragmentation even with copyleft
Developer 2
Source 2
Developer 1
Source 1
L1
Innovation
Different hardware
Different networks
Support different add-on software
Differently prioritised bug fixes
Different performance criteria…
Generic requirements
Different requirements
Source 1, v2
L1
Fork L1
L1

5. The best guarantee against platform fragmentation is
powerful platform leadership & expert ecosystem
… Trustworthy: well-motivated and competent

Overcoming fragmentation tendencies
Developer 2
Source 2
Developer 1
Source 1
L1
Innovation
Different hardware
Different networks
Support different add-on software
Differently prioritised bug fixes
Different performance criteria…
Generic requirements
Different requirements
Source 1, v2
L1
Fork L1
L1
Skilled ecosystem
Skilled &
attractive
integrators
Clear
leadership

5. The best guarantee against platform fragmentation is
powerful platform leadership & healthy ecosystem
… Trustworthy: well-motivated and competent
6. The less mature the platform, the more likely it will be to
fragment, especially if there’s a diverse customer base
and a hectic market environment

Fragmentation is easy
Integration is hard
Stable and mature base,
with reliable processes

Which mobile OS best solves
the series of hard problems for
device & service creation?
Large pool of productive
and engaged developers
Nimble and agile
response to market needs
Best principles of
open source software
Tools,
APIs
Large,
viable
market
Intensely
listening to
customers
And
delighting
them
Stable and mature base,
with reliable processes

The winning mobile OS’s

OS diversity can
be hidden from
applications by
intermediate
layers (eg Java)
Some apps do
need native access
(for speed, APIs…)
The device creation
community needs
consistent and
reliable native access
Device creation
fails if the DCC
experiences too
much OS
fragmentation
?

Proving time for Symbian Foundation platform
June
2008
June
2010
H1
2009
Software
Small community,
high barrier to entry
Large community,
low barrier
to entry
CKL or DKL
SFL
EPL
Open source,
zero barrier to entry

Why the EPL? – choosing an OSS license
• The choice of a license is a necessary (but not sufficient) part
of reducing software fragmentation
… This is an argument for a “weak copyleft” license
… Permits the creation of new components – above, below, or alongside
… Stops customers from hoarding their changes to original components
1. The license should be “business friendly”
… Clearly written; Already tried and tested
… Minimises the risk of customers being unexpectedly forced to release
source code for their own innovative new components
2. The license should be “integration friendly”
… Supports coexisting with software written under other licenses
3. The license should be “patent friendly”

Proving time for Symbian Foundation platform
June
2008
June
2010
H1
2009
Software
Small community,
high barrier to entry
Large community,
low barrier
to entry
CKL or DKL
SFL
EPL
Open source,
zero barrier to entry
3 UIs: S60,
UIQ, MOAP(S) 1 UI: S60
Regular incremental releases
Number
of
independent
contributors

Symbian Foundation governance principles
• Cooperate on the shared infrastructure
… Enable innovation and competition outside shared
infrastructure
• Contribution is king
… Expect deeper contributions from wider and wider groups
of people
• Meritocracy rather than $$$ decides
Transparency of process as well as of code

Symbian Foundation operating principles
• Role of Foundation itself is to create huge leverage
… Limited software development by Foundation staff
members
 Software codeline management
 Developer ecosystem management
• Councils to elevate best ecosystem understanding
… Roadmap planning; Architecture;
… UI and usability; Releases
• Regional Advisory Councils
• Keep the platform the clear leader
… Minimise the risks of platform fragmentation
Expand huge business opportunity

Four top Symbian Foundation priorities
1. Quickly complete highly competitive fully open mobile
operating system
… Mobile software set free…
2. Enable easy creation of rich applications
… Web, Python, Java, Flash, Silverlight, Qt Software, native…
3. Enable easy introduction of novel hardware
… New kinds of smart mobile device
… New peripherals and new hardware providers…
4. Remove friction from the wider ecosystem
… Streamline routes from innovation to market
… Improve application signing, application deployment…
Accelerate
consumer
experiences

Success metrics 2008-2013-2018

From the Eclipse Foundation to the Symbian Foundation

More Related Content

Similar to From the Eclipse Foundation to the Symbian Foundation (20)

More from David Wood (20)

Recently uploaded (20)

From the Eclipse Foundation to the Symbian Foundation