Slide 1

Slide 1 text

Open Innovation in Action Lessons learned about social collaboration from 30 years of open source Stefane Fermigier, Abilian, March 2012 Monday, March 25, 2013

Slide 2

Slide 2 text

Who am I? Monday, March 25, 2013

Slide 3

Slide 3 text

Monday, March 25, 2013

Slide 4

Slide 4 text

I’m an open source developer Monday, March 25, 2013

Slide 5

Slide 5 text

I’m an open source developer (And an entrepreneur, too...) Monday, March 25, 2013

Slide 6

Slide 6 text

Today’s thesis Many of the aspects of what we call social technologies and social business were pioneered at one point by the open source development communities. It’s also true for Open Innovation. Monday, March 25, 2013

Slide 7

Slide 7 text

A short history of Free & Open Source Software Monday, March 25, 2013

Slide 8

Slide 8 text

FOSS 0.1 1983-1990 Monday, March 25, 2013

Slide 9

Slide 9 text

Photo credit: http://commons.wikimedia.org/wiki/User:Vicapowell39 Monday, March 25, 2013

Slide 10

Slide 10 text

Photo credit: http://commons.wikimedia.org/wiki/User:Vicapowell39 Richard Stallman, Founder of the Free Software Movement Monday, March 25, 2013

Slide 11

Slide 11 text

• The free software movement was started in 1983 by Richard Stallman • Most of the open source software produced at the time was developed by very small teams (2-3 persons), using local development tools • Software were distributed using tapes, then FTP • Marketing was mostly through word-of- mouth Monday, March 25, 2013

Slide 12

Slide 12 text

Early successes • The GNU “operating system” (minus the kernel) was already displacing proprietary tools in the early 90s • The moral and legal frameworks upon which the free software (and later, the open source) movement is built • Didn’t mandate / prescribe any production model for free software, though Monday, March 25, 2013

Slide 13

Slide 13 text

Challenges • Economic and moral questioning: • Is it ok to make money with free software? • How to make the system sustainable? • How to scale development efforts to larger teams? Monday, March 25, 2013

Slide 14

Slide 14 text

FOSS 0.9 1991-1998 Monday, March 25, 2013

Slide 15

Slide 15 text

• Larger scale projects start to appear, attracting tens, then hundreds of developers (and later, thousands) • Tools and practices are developed, most often on top of existing internet protocols to address the needs of distributed development at this scale : • Centralized source code management • Mailing lists or usenet forums Monday, March 25, 2013

Slide 16

Slide 16 text

Successes • Linux (1991) • The Debian (1993) and Red Hat (1994) distributions • The Apache Web Server (1995) Monday, March 25, 2013

Slide 17

Slide 17 text

FOSS 1.0 1998-2007 Monday, March 25, 2013

Slide 18

Slide 18 text

• Open source becomes the preferred term for most free software based businesses • The Web becomes pervasive • Several organizations created to foster governance of open source projects (Apache Foundation, Eclipse Foundation, OW2...) • Several successful IPOs on top of the Web 1.0 bubble (Red Hat, VA Linux), Netscape open sources the Mozilla browser... Monday, March 25, 2013

Slide 19

Slide 19 text

• Real-time shared vision • Real-time status updates • Real-time help requests • Self-service archives Source: Bertrand Delacretaz, 2009 The 4 engines of collaboration Monday, March 25, 2013

Slide 20

Slide 20 text

“Every successful open source project I know uses PRIM. Every closed source project I know, doesn't. People wonder how open source projects manage to create high-quality products without managers or accountability. The answer: we're accountable to our infrastructure. PRIM is the open source secret sauce.” Ted Husted http://jroller.com/TedHusted/entry/prim Monday, March 25, 2013

Slide 21

Slide 21 text

P = Portal (often, a Wiki) Monday, March 25, 2013

Slide 22

Slide 22 text

R = Repository Monday, March 25, 2013

Slide 23

Slide 23 text

I = Issue (or Bug)Tracker Monday, March 25, 2013

Slide 24

Slide 24 text

M = Mailing List (+ foruM) Monday, March 25, 2013

Slide 25

Slide 25 text

Software Forges, a more integrated approach • Sourceforge, launched in 1999 by VA Linux, integrates all these tools in a consistent Web (1.0) portal • Makes it super easy for anyone (3.4 million users currently) to start a new open source project (324 000 as of today) • Several similar products launched afterwards (Collabnet, Trac, Redmine) Monday, March 25, 2013

Slide 26

Slide 26 text

Works for non open source software too... Monday, March 25, 2013

Slide 27

Slide 27 text

FOSS 2.0 2008-now Monday, March 25, 2013

Slide 28

Slide 28 text

Web 2.0 • Wikipedia (2001) • Tim O’Reilly’s Architecture of Participation (2004) and Web 2.0 (also 2004) • Consumer Web 2.0, then Enterprise 2.0 replace older applications Monday, March 25, 2013

Slide 29

Slide 29 text

• Git, and a bunch of other Distributed Source Control Management Systems (DSCM), appear circa 2005 to address the need of very large distributed development teams (1000s of developers for Linux) • They allow for completely decentralized development, and make it much easier for developers to try out new ideas on their own, then “merge” the changes with the main development lines Monday, March 25, 2013

Slide 30

Slide 30 text

Monday, March 25, 2013

Slide 31

Slide 31 text

Linus Torvalds, Git creator (2005) Monday, March 25, 2013

Slide 32

Slide 32 text

Linus Torvalds, Git creator (2005) BTW, he invented Linux too... Monday, March 25, 2013

Slide 33

Slide 33 text

• A new breed of SaaS offerings for developpers, such as GitHub (2008) or StackOverflow (2008), appear, leveraging many of the characteristic features of W2.0 or E2.0 applications: • Activity streams • Social networking • Tagging / folksonomies • Votes, reputation Monday, March 25, 2013

Slide 34

Slide 34 text

GitHub, like SourceForge, but more social Monday, March 25, 2013

Slide 35

Slide 35 text

StackOverflow, a knowledge base based on a reputation system Monday, March 25, 2013

Slide 36

Slide 36 text

Additional tools with a social impact • Continuous integration (with a strong testing culture) allows distributed development to happen with confidence that developers don’t “break the build” • Code review applications Monday, March 25, 2013

Slide 37

Slide 37 text

Continuous integration Monday, March 25, 2013

Slide 38

Slide 38 text

Code review on GitHub Monday, March 25, 2013

Slide 39

Slide 39 text

Open Source as a model for Open Innovation Monday, March 25, 2013

Slide 40

Slide 40 text

Monday, March 25, 2013

Slide 41

Slide 41 text

Governance models for OSS projects • Vendor-led • May include, to balance power with the users: a users club, a more or less independent and powerful board... • Community led • Either formal or informal • If formal, either though a generic community (FSF, ASF, Eclipse, OW2...) or ad-hoc Monday, March 25, 2013

Slide 42

Slide 42 text

How to create a thriving open source community? (May apply to your social business initiative too...) Monday, March 25, 2013

Slide 43

Slide 43 text

• Put people first (“community over code”) • Welcome newcomers, give credits • Learn how to deal with poisonous people • Create an architecture of participation • Have a modular architecture for your product • Be clear about your vision (roadmap) and give regular status reports • Make it easy to contribute Read http://www.artofcommunityonline.org/ for details Monday, March 25, 2013

Slide 44

Slide 44 text

Open by default? Monday, March 25, 2013

Slide 45

Slide 45 text

(...) (...) Source: http://circulaire.legifrance.gouv.fr/pdf/2012/09/cir_35837.pdf Monday, March 25, 2013

Slide 46

Slide 46 text

Source: https://www.gov.uk/service-manual/making-software/open-source.html Monday, March 25, 2013

Slide 47

Slide 47 text

Contact: sf@fermigier.com Web: www.fermigier.com www.abilian.com Monday, March 25, 2013