book

Adopting InnerSource

by Danese Cooper, Klaas-Jan Stol

September 2018

Intermediate to advanced

187 pages

4h 46m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Old Patterns of Development: Closed and SlowFactors Driving Open SourceProprietary HierarchiesThe Open Source WayWhy Does Open Source Development Succeed?What Is InnerSource?A History of InnerSourceWhy Do Companies Adopt InnerSource?Breaking Down Silos and BottlenecksReuseKnowledge Sharing and Full Stack TeamsInnovationImproving QualityStaff Mobility and Process StandardizationInnerSource TodayWhy We Wrote This BookWho Should Read This BookHow This Book Is OrganizedVisit Us OnlineAcknowledgments
Origins of The Apache WayFundamentals of The Apache WayMeritocracyTransparencyCommunity
Background on Internet Protocols for Voice CommunicationSIP: A Brief BackgroundThe Project: The Common SIP Stack (CSS)Phase 1 (1998–2000): The Foundational YearsPhase 2 (2001–2003): Opportunistic PartneringPhase 3 (2004–2006): Corporate Open SourceReflections, Insights, and DiscussionAdvertising and EncouragementThe SIP Asset: By the NumbersLooking BackAcknowledgments
Why InnerSourceStarting the BIOS JourneyEstablishing and Growing the BIOSphereBIOS ValuesBIOS Review CommitteeBIOS Governance OfficeAttracting ContributorsFrom BIOS to Social CodingSustaining Social CodingSuccess StoriesWidespread AdoptionDiverse Ecosystem of CommunitiesImproved CollaborationPersonal GrowthIncreased ProductivityAlignment with BusinessSuccess FactorsChallengesLessons LearnedConclusionAcknowledgments
A Little BackgroundAttributes of InnerSourceThe CheckOut ExperimentThe Onboarding ExperimentExecutive Air CoverMeanwhile, in IndiaLearning GoalsBeginning Symphony and InnerSource Brand DilutionInitial Symphony TrainingThe Contributing.md FileCadence of Check-InsOutcomesThe Rhythm of InnerSource WorkThe Future of InnerSource at PayPalAcknowledgments
Looking for New Ways of OrganizingStarting the Journey Toward InnerSourceWhy InnerSource?InnerSource ExperimentsSteps Toward InnerSourceGetting People on BoardLeading by ExampleInnerSource PrinciplesInnerSource ResultsInnerSource: One Year LaterInnerSource ChallengesBuilding Trust in Written CommunicationScaling InnerSource Beyond First ExperimentsGetting Other, Nondeveloper Colleagues on BoardCrossing the Boundary Toward Open APIs and Open SourceConclusion and Future OutlookAcknowledgments
The Changing Telecommunications LandscapeWhy InnerSource?Scaling Up Development CapacityReducing WasteImproving QualityStarting the Community Developed Software ProgramCreating Core TeamsSetting Up Contribution RulesSetting Up a Flexible CDS InfrastructureCreating the Governance CouncilSelecting Components and Development ModelsDevelopment ZonesCollaboration WorkflowMaking Collaborations HappenPillars of Community-Developed SoftwareSuccess: The User Interface SDK FrameworkLessons LearnedThe Future of InnerSource at EricssonAcknowledgments
Comparison of the Case StudiesProductProcesses and ToolsCommunity and ManagementGuidelines for Adopting InnerSourceProductProcess and ToolsCommunity and ManagementThe InnerSource Commons

Content preview from Adopting InnerSource

Chapter 1. The InnerSource Approach to Innovation and Software Development

With Andy Oram

InnerSource is a software development strategy rapidly spreading throughout large corporations—and it is also more. At its essence, InnerSource enables software developers to contribute to the efforts of other teams, fostering transparency and openness to contributions from others. But beyond that, InnerSource represents a collaborative and empowering way of involving employees in making and implementing decisions throughout the corporation. It embodies a philosophy of human relations, an approach to rewards and motivations, and a loose, adaptable set of tools and practices.

This book presents case studies at a range of companies to show when and why InnerSource may be useful to your organization. The case studies candidly discuss the difficulties of getting InnerSource projects started, along with the progress so far and the benefits or negative fallout. We hope that readers will be inspired to advocate for InnerSource within their software development groups and organizations.

InnerSource is an adaptation of Open Source practices to code that remains proprietary and can be seen only within a single organization, or a small set of collaborating organizations. Thus, InnerSource is a historical development drawing on the Open Source movement along with other trends in software. This chapter introduces InnerSource and locates it in the history of software.