introduction to open source - lunds tekniska...
TRANSCRIPT
1
Public A Introduction to Open Source 2015-04-13 1
Introduction to Open Source
Carl Eric Mols Mateo Davis
Sony Mobile Communications AB
Public A Introduction to Open Source 2015-04-13 2
Agenda
• General Overview • What is it? • Theory of Why it Works • Open Source Licensing Basics
• Open Source at Sony Mobile • History • Strategy • Intellectual Property • Open Source Processes
2
Public A Introduction to Open Source 2015-04-13 3
Why are we here??
• SOMC’s History/Transition – Share lessons learned
• Engineers/Developers - have tremendous opportunities, but with that comes responsibility
• Lawyers and Engineers need to work together – legal and technical issues overlap
Public A Introduction to Open Source 2015-04-13 4
What is Open Source Software?
• Computer Software that provides its source code under a license with the rights to study, change, and distribute the software to anyone and for any purpose
• OSI Definition: 10 Freedoms – http://opensource.org/osd-annotated
• Is it widely used?
3
Public A Introduction to Open Source 2015-04-13 5
Wildly Successful
• More Stable
• Faster Development Time
• More Secure
• It is everywhere: • 2 billion people own a smartphone, full of Open Source • Internet, web services, medical equipment, cars and likely your fridge too. • Even the US DoD is a major user of Open Source … think ARPAnet …
Google Chrome
Apache
Public A Introduction to Open Source 2015-04-13 6
The Cathedral vs The Bazaar – Why it Works
• Linus’ Law: with enough eyeballs, all bugs are shallow • Release early, release often (bleeding edge vs. stable releases) • Users = Co-Developers: users become testers, and testers become contributors • Skilled developers wandering through your architecture • Self-selection of developers • Public - your work is on display (and the criticism can be brutal) • Meritocracy + Democracy/little management • Crowd Power – crowd decision-making works in the context of code development • Why developers volunteer: reputation, experience, scratch an itch/solve a problem • Why developers are paid: shared support and maintenance makes it cost efficient
and more reliable
See Eric S Raymond, The Cathedral and the Bazaar: http://www.catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/
4
Public A Introduction to Open Source 2015-04-13 7
Licensing Basics - Copyright
• Copyright attaches to every novel expression of an idea (e.g., software)
• Exclusive Right to: • Copy • Modify • Distribute
• Time Limited – 50+ years
• License – grants defined rights
Public A Introduction to Open Source 2015-04-13 8
Copyleft
Richard M Stallman Reciprocity Distribution = trigger Changing the code/combining with other code = need to provide changes/combination to the downstream recipient
5
Public A Introduction to Open Source 2015-04-13 9
Open Source Licensing Overview
CopyLeft Permissive
GPLv2 Mozilla Public Apache 2.0 MIT (+ v3) BSD
(+ Affero)
Derivative Modifications Patent protection Notice work to files only
Public A Introduction to Open Source 2015-04-13 10
License Interpretation (Re Copyleft)
• GPL uses very technical language (+ is a manifesto as much as a license)
• Glosses on licenses created by old message board discussions/FAQs • E.g, Linus Torvald’s interpretaion of the GPL as it applies to Linux • Stallman/FSF’s FAQ pages about the GPL
• What is a derivative work often becomes very technical • Widely recognized exceptions/interpretations by the community –
shims, sockets, etc.
6
Public A Introduction to Open Source 2015-04-13 11
Open Source Community
• Free Software Foundation – Stallman founded • Software Freedom Law Center – Eben Moglen • Apache Foundation • Linux Foundation • gpl-violations.org
Public A Introduction to Open Source 2015-04-13 12
Open Source at Sony Mobile
7
Public A Introduction to Open Source 2015-04-13 13
+ Miscellaneous
Overview of Different Open Source Activities
Public A Introduction to Open Source 2015-04-13 14
Entry
OS History
Inner-Source
2002 2009 Present Microsoft
8
Public A Introduction to Open Source 2015-04-13 15
Official Strategy
Public A Introduction to Open Source 2015-04-13 16
Fundamental objectives for [AOSP] contributions
• Reduce Cost of Maintenance Contributions reduce the patch mountain.
• Improve Time-To-Market Fewer patches means faster bring ups. Feedback from Google shows insights to roadmaps/strategic direction.
• Disrupt Competitors
By contributing, we force competitors to re-adjust their set of patches.
• Get Closer to Google Create engineer-to-engineer relationships that can be leveraged to drive the business. Influence Android strategy.
9
Public A Introduction to Open Source 2015-04-13 17
Contribution Strategy chart B
usin
ess
Impa
ct /
Uni
quen
ess
High
Platform / Leverage
Strategic Alliances & Investments
Control focus
Control Complexity High Low
Strategic
Product / Bottleneck Standard
TTM focus
Cost focus
Public A Introduction to Open Source 2015-04-13 18
Major groupings
Bus
ines
s Im
pact
/ U
niqu
enes
s
High
Platform / Leverage
Control Complexity High Low
Strategic
Product / Bottleneck Standard
= Contribute
= Keep close, but enablers should be contributed.
10
Public A Introduction to Open Source 2015-04-13 19
Intellectual Property Rights and Contributions
• Patent Strategy To reduce royalty payments and to ensure that products are the most appealing.
• IPR Dept Checks contributions for conflict with IPR goals and objectives.
• Modify If there are patent issues, IPR Dept can often suggest alteration of a proposal to allow for contributions. It is extremely rare a contribution proposal is fully rejected!
• Document Track all submitted contribution proposals and their status.
Do not Self-Censor! Try it, and if (when!) getting an approval from Open Source Board = IPR is cleared to contribute.
Public A Introduction to Open Source 2015-04-13 20
Open Source Processes
• 2 Corporate Directives • Intake – Open Source Software Directive • Output – Open Source Software Contribution Directive
• Open Source Board – Decision making body for contributions of Open Source. Maintains the Open Source Directives. Members:
• Legal • IPR • Open Source Operations • Technology/CTO • Development (GSM) • UX (App Software)
11
Public A Introduction to Open Source 2015-04-13 21
OSS Intake
SW Engineer
Open Source SW Operations
Business Manager / Sourcing Officer*
Legal IPR
Open Source Software
5. Reject / Accept
4. Recommendation
1. Initiate OSS Evaluation
2. Prepare
Guiding principal: In line with intake of 3rd party commercial SW components
3. Review
Governance of business decision
Public A Introduction to Open Source 2015-04-13 22
Classification of Contributions
Trivial contribution A Trivial contribution is a rather small and simple change to already existing open source software. No new functionality added. No significant improvement in performance.
• E.g., bug fixes
Medium contribution A Medium Contribution is larger than a Trivial Contribution. It can contain both substantially changed functionality and completely new functionality.
• E.g., new Linux device drivers (support for new hardware)
Major contribution A Major Contribution involves substantial amounts of code, with significant Intellectual Property value, and is the result of considerable internal development efforts.
• E.g., DRM Framework
12
Public A Introduction to Open Source 2015-04-13 23
Scheme on OSS Contribution- Trivial contribution
INTERNAL USE ONLY
Open Source Board
Business Manager / Contribution Officer
Open Source Software
CTO / Executive Management
Sony IPD Parental Approval
If Android Note that Trivial contributions only requires Business Manager’s approval!
Public A Introduction to Open Source 2015-04-13 24
Scheme on OSS Contribution- Medium contribution
INTERNAL USE ONLY
Open Source Board
Business Manager / Contribution Officer
Open Source Software
2. Approve / Reject
Representation in the Open Source Board • Technology • Software • GSM • Legal • IPR • Open Source SW Operations
CTO / Executive Management
Sony IPD Parental Approval
Yes Patent
Clause?
Accepted
No
1. Contribution Proposal
13
Public A Introduction to Open Source 2015-04-13 25
Scheme on OSS Contribution- Major contribution
INTERNAL USE ONLY
Open Source Board
Business Manager / Contribution Officer
Open Source Software
2. Assess and recommend
3. Approve / Reject
4. Notify
Representation in the Open Source Board • Technology • Software • GSM • Legal • IPR • Open Source SW Operations
CTO / Executive Management
Sony IPD Parental Approval
Yes Patent
Clause?
Accepted
No
1. Contribution Proposal
Public A Introduction to Open Source 2015-04-13 26
Conclusions
• Engineers empowered, but need to take responsibility
• Legal and Development/Engineers need to work together
• Open Source is simple –understand the consequences and handle it
accordingly
• Process/Administration
14
“SONY” or “make.believe” is a registered trademark and/or trademark of Sony Corporation.
Names of Sony products and services are the registered trademarks and/or trademarks of Sony Corporation or its Group companies.
Other company names and product names are the registered trademarks and/or trademarks of the respective companies