Welcome to InnerSource, the powerful movement for developing open source software within the walls of a single organization, where the «openness» of a project extends across teams inside the company. In this report, O’Reilly editor and author Andy Oram takes you inside InnerSource, first by reviewing the principles that make open source development successful, and then by describing how InnerSource has worked at PayPal, the leading Internet commerce facilitator.
PayPal’s path to InnerSource involved a series of large-scale corporate decisions that included a conscious shift in tools and corporate culture. Through InnerSource, the company not only achieved faster development and better quality, but also created an environment of cross-team cooperation that encouraged programmers to contribute to any of PayPal’s development projects.
You’ll learn specific advantages of the InnerSource strategy, including:
- Faster development: Programmers use unit tests, code coverage, and continuous integration to remove bugs at early stages
- Complete documentation: Code is documented better, both in-code comments and less formally on discussion lists
- Code reuse: Programmers across the organization understand the code and architecture of modules developed by other teams
- Cross-team collaboration: Contributions by members outside of the team are frictionless and rarely have to be rewritten
- Development with GitHub: GitHub maintains private repositories for in-house projects as well as public repositories for open source code