OPEN SOURCE AS AN ELEMENT OF

CORPORATE STRATEGY

Shawn BriscoeDirector Strategy SVCS

@black_duck_sw

Guy MartinSenior Strategist

@SamsungOSG

2

FRAMEWORK FOR OPEN SOURCE

INTERACTIONS

Flexible Framework for:

• Organizational/team-specific

needs

• Evolving adoption/use of OSS

• Interrelated focus areas

Four (4) Focus Areas:

• Strategy & Governance

• Consume

• Collaborate

• Create

3

OPEN SOURCE IS A STRATEGIC ASSET

30%

80%

Average* Best in class

*Source: IDC 2012

COVER MASTER

+

SOURCE

the future of

OPEN

2014

5

2014 SURVEY COLLABORATORS

6

FACTORS FOR ENTERPRISE ADOPTION OF

OSS

7

FACTORS FOR ENTERPRISE PARTICIPATION IN

OPEN SOURCE COMMUNITIES

8

ELEMENTS OF AN ENTERPRISE OPEN SOURCE

STRATEGY

Culture

Product

Community

Governance

Open Source

Strategy

9

PRODUCT STRATEGY

Building

OSS

Your Product

or Service

Open

Source Your Product

or Service

Building

for OSS

Open

Source

Building

with OSS

Your Product

or Service

Open

Source

Building

on OSS

Open

Source

Your

Business

10

THE PROMISE OF OPEN SOURCE

Systematically streamline, safeguard, and

manage open source throughout your software

development value chain.

Choose Approve Inventory SecureScan Deliver

11

MITIGATE SECURITY RISKS

12

CORPORATE CULTURE

Collaboratio

n

Transparenc

y

Meritocracy

Contribution

Governance

Organization

al

Knowledge

Reuse

Metrics

INNER SOURCE

13

COMMUNITY STRATEGY

Operational

Efficiency

Technology

Influence

Talent

Identification

Stewardship

14

CASE STUDY

Samsung Open Source Group

15

Prolification + Contributions

SAMSUNG OPEN SOURCE TIMELINE

Exploring

Possibilities

Using embedded Linux in select products

Adoption

Adoption of Linux and Open Source SW as a viable alternative

Tizen

Major

Contribution

2012200820052002

Open Source Group

Created in SRA-SV + Open Source Office in SRUK

2013

16

Open Source

Leadership

SAMSUNG OSG MISSION

17

WHY?

18

HOW?

Strategy Components

Grow OpenSource

Competence

Thought Leadership

External &Internal Visibility

UpstreamContributions

Educate/MentorProductTeams

19

RESULTS TO DATE (2014)

• Contributions

• 25 dedicated OSS developers (16 maintainers)• Linux Kernel, Multimedia, Graphics, Web, Virtualization

• > 6300 upstream contributions• 2/3 bug fixes, remaining split between enhancements/new features

• 98% contribution acceptance rate

• 15% of contributions driven by business units

• Thought Leadership/Visibility

• > 60 conference presentations/papers

• 13 media mentions (including WSJ, Linux.com, etc.)

• 35 product developers graduated from

OSS Leadership Program

20

Lessons Learned Along the Road….

21

RULE #1

No two communities are exactly the same!

22

RULE #2

Communities don’t work for individual companies

23

UNDERSTAND COMMUNITY GOVERNANCE

• Each community is different

• Contributions need to ‘fit’ with other code/patches

24

UNDERSTAND COMMUNITY MOTIVATORS

• Successful communities are powered by motivated

people

• Motivation can be: status, money, peer recognition

25

BE CAREFUL OF ‘CUSTOM’ LICENSES

• Communities do not work well with ‘custom licenses’

• Gaining contributors/momentum requires low barriers

to entry

http://opensource.org/licenses/index.html

26

COMMUNITIES NEED NURTURING

• Posting code to public sites is not collaboration

• Community participation is a cycle – expect change

27

BE HUMBLE, BUT BOLD

• Community leadership is earned, not granted• Accept community feedback and rework code

• Bring technical expertise to the table• Contributions need to be ongoing to maintain leadership status

Humble Bold

Leadership != ControlAccounting != Leadership

28

THANK YOU!