InnerSource is a term that describes the new practice of organizations adopting open source methodology to create proprietary software. This blog will focus on the Inner-Source ecosystem which leverages multiple AWS service. Services such as CodeCommit and CodeGuru, CodeBuild and CodeArtifact, CodePipeline and other AWS services.
Exploring InnerSource and Its Uniqueness
Most IT companies today use open source software (OSS). It is a great way to standardize software and bring cost-effectiveness by reusing high quality, time-tested code. While some organizations may allow it to be used as-is, others may use a vetting process to ensure that the OSS conforms to their security standards and quality. The OSS is a result of how community projects are managed and maintained and the culture of openness and collaboration they foster. Many organizations that create closed-source software are trying to emulate these principles and practices. This approach, which is often referred to as “InnerSource”, is perhaps more widely discussed than it is actually adopted.
InnerSource is a great tool for software collaboration within an organization’s scope. It also keeps its concerns about IP and legality under control. It allows for collaboration and innovation across organizational borders by sharing knowledge and talents. The benefits of higher code quality and faster time to market are being realized by organizations at a fraction the cost.
What makes up an InnerSource Ecosystem
InnerSource ecology is built on infrastructures and processes that foster collaboration. These systems include many support tools and features, including peer reviews, code hosting and issue tracking, communication and collaboration, Pull Request (PR), approval flow, documentation and automated testing, as well as continuous integration. This system has a significant component, an entry portal. This allows employees to find projects based upon InnerSource and also join the communities. They can start as ordinary users of the reusable codes and then graduate the contributors and the committers.
InnerSource System to facilitate a development workflow.
InnerSource thrives on community collaboration. There is no entry barrier to allow for adaptability. It is important to decide strategically for projects that it can be InnerSourced and has the correct licensing model. Businesses should bootstrap the initiatives by providing seed products that can draw its community and maintainers as well as the first set of contributors. Many of these users could be promoted to trusted committers through a meritocracy-based model.
Organizations should plan to transition from an infra-specific model over time to a project-specific model. A project-specific InnerSource model has a dedicated team that is funded by other business units and responsible for a particular software asset. The infrastructure-based InnerSource model provides the infrastructure for the creation of the ecosystem, including code repositories, document repositories, communication platforms, and so forth. This allows anyone within the organization to create InnerSource projects while the project initiators can manage and maintain their projects. It is difficult to overstate the importance of modular architecture in InnerSource projects. This architecture aids developers in understanding the code and allows code reuse and parallel development. Multiple contributors can work on different modules of code, avoiding conflicts during code merging.
InnerSource Model Solution
This model solution was created to facilitate a developer’s workflow.
The distributed version control (AWS CodeCommit) is at the heart of the InnerSource verse. To maintain transparency in the system