Book description
Although many large corporations are reluctant to release the software they use in-house publicly as open source, those companies can still use principles and processes of open source for developing their in-house software—a practice popularly known as InnerSource. But adopting open source practices without understanding the cultural context behind them often fails. That’s where this report comes in.
Author Silona Bonewald explains how the InnerSource initiative, introduced by PayPal, can help your company develop software internally by applying lessons from the open source movement. A checklist guides you through various steps needed to produce open source software, whether it’s companywide or just for one team.
Alongside the how, Bonewald—Director of InnerSource Commons—also explains the why behind open source. You’ll learn ways to improve collaboration, create cleaner code, reduce bottlenecks, and facilitate integrations among teams.
This report examines:
- Ways to adapt InnerSource to your business environment without diluting open source fundamentals
- The crucial role of the Trusted Committer in the InnerSource process
- How to extracting tribal knowledge from silos through passive documentation
- Why contributing agreements formalize the responsibilities of developers who originate code
- How to move from internal silos to internal transparency
Table of contents
- Foreword
- 1. Why InnerSource?
- 2. What InnerSource Is and Isn’t
- 3. The Most Important Role, and the First Step: Trusted Committer
- 4. Passive Documentation and the Need for Findability
- 5. Creating Good House Rules for Guests: Writing Contributing Agreements
- 6. Working Within the Enterprise: Understanding Planning
-
7. From Internal Silos to Internal Transparency
- Where Did Silos Come From?
- What’s Wrong with Silos?
- Transparency for Community Sourcing
- Transparency Boosts Decision-Making
- How Do We Break Down Silo Walls?
- Findable Documentation Is Part of Transparency
- Where Do We Still Need to Improve Transparency?
- What Are the Limits or Pitfalls in Enterprise Transparency?
- 8. Looking Forward
- 9. Appendix
Product information
- Title: Understanding the InnerSource Checklist
- Author(s):
- Release date: July 2017
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491986905
You might also like
book
SRE サイトリライアビリティエンジニアリング ―Googleの信頼性を支えるエンジニアリングチーム
GoogleのSREチームの主要メンバーによって書かれた本書は、ソフトウェアのライフサイクル全体にコミットすることで世界最大規模のソフトウェアシステムがどのように構築、導入、監視、維持されているのかを解説します。はじめにリスク管理やサービスレベル目標、リリースエンジニアリングなどSREの行動の基礎となる原則について解説し、次にインシデント管理や障害の根本原因分析、SRE内でのソフトウェア開発など大規模分散コンピューティングシステムを構築し運用するSREの実践について詳述します。急速にスケールするサービスを高い信頼性で運用する方法を解説する本書はエンジニア必携の一冊です。
book
IBM WebSphere: Deployment and Advanced Configuration
The expert guide to deploying and managing any WebSphere Application Server V5.x application and environment If …
article
Why the Power of Technology Rarely Goes to the People
Throughout history, the advantages and costs of technological innovations have been unevenly distributed between the powerful …
video
Panel: Real-time Discussions on Real-time Data processing
How do streaming experts define “streaming”? What are their favorite use cases of real-time streaming, and …