Open Source has brought a lot of advantages to software development, such as transparency, collaboration, communication, etc. InnerSource is an attempt for us to bring these advantages into our internal development by adopting the practices and culture of Open Source.
To understand the appeal of InnerSource project management, consider what has made open source software development so successful:
- Programmers share their work with a wide audience, instead of just with a manager or team. In most open source projects, any‐ one in the world is free to view the code, comment on it, learn new skills by examining it, and submit changes that they think will improve it or customize it to their needs.
- New code repositories (branches) based on the project can be made freely, so that sites with unanticipated uses for the code can adapt it. There are usually rules and technical support for remerging different branches into the original main branch.
- People at large geographical distances, at separate times, can work on the same code or contribute different files of code to the same project.
- Communication tends to be written and posted to public sites instead of shared informally by word of mouth, which provides a history of the project as well as learning opportunities for new project members.
- Writing unit tests becomes a key programming task. A “unit test” is a small test that checks for a particular, isolated behavior such as rejecting incorrect input or taking the proper branch under certain conditions. In open source and InnerSource, testing is done constantly as changes are checked in, to protect against failures during production runs.
InnerSource differs from classic open source by remaining within the view and control of a single organization. The “openness” of the project extends across many teams within the organization. This allows the organization to embed differentiating trade secrets into the code without fear that they will be revealed to outsiders, while benefiting from the creativity and diverse perspectives contributed by people throughout the organization.
You can find the detailed guidelines on implementing the various aspects of InnerSource in this section of the Developer Guidelines website. Additionally an implementation checklist to help guide you through the steps is also available. In summary the following steps should be taken to prepare your project for InnerSource:
Define the Owner(s) and Trusted Committer(s) for your project, following the InnerSource Roles guidance .
Configure your Bitbucket repository to allow InnerSource contributions correctly. Follow the guidance on repository configuration .
Create the Contribution Agreement for the project which sets the ground rules for how people can contribute to the project. Follow the specific guidance on creating the Contribution Agreement .
Create and maintain the documentation for the project - ensuring documentation in the repository is kept up to date - particularly including details of the current Trusted Committer if the role is rotated. Follow the guidance on project documentation .
Set up a method of communication for existing contributors, consumers and people who want to contribute. Follow the guidance on project communication .
Setup a project tracking to allow people to report and track issues/suggestions for your project. Follow the guidance on project tracking .
Remember to check out the implementation checklist for more detailed steps and the rest of this section for more specific detail on the different InnerSource concepts.
- InnerSource Commons Checklist - A free PDF by PayPal that describes ways to adopt InnerSource
- InnerSource Checklist Summary
- Three-part series on InnerSource from Salesforce