An introduction to innersource · GitHub
Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Adopting this modern approach to software development can be transformative—enabling collaboration and fostering the creation of high quality code. But understanding the principles, and potential challenges, is critical to success.
Many companies use the word “innersource” to describe how their engineering teams work together on code. Innersource is a development methodology where engineers build proprietary software using best practices from large-scale open source projects, like Kubernetes or Microsoft’s Visual Studio Code. Large-scale open source projects require coordination and teamwork across thousands of contributors. The most successful ones are driven by a vision for their future, in addition to day-to-day user needs: speed, reliability, and functionality.
The scale at which these operate can teach us a few lessons—and help your business build better software, faster using innersource. In this article, we’ll cover the basics of how teams use innersource in their daily workflows and apply open source practices to work collaboratively and efficiently. How to get started with innersource Beginning your journey to adopt innersource practices requires careful planning and a cultural shift.
Start by identifying a pilot project that embodies the principles of collaboration and transparency. Define clear success criteria to measure progress, and encourage feedback from all participants. Set Up the Foundations Establish Repository Settings : Configure your repositories to ensure appropriate access for internal contributors. This promotes a culture of collaboration and makes code visible to all employees. Automate Processes : Use tools that automate tasks such as issue triage, code reviews, and release management to save time and reduce manual errors.
What makes a project open source? GitHub is home to the largest open source community in the world. What our community builds spans the interests and skillsets of millions of contributors. Together, they work on programming languages like Apple’s Swift and frameworks like Facebook’s React.js—and they don’t just write code. Datasets, legal documentation, and more can also be open sourced. Anyone can use open source software.
They can also view, modify, and distribute a project for any purpose—as enforced by open source licenses . Similarly, anyone can help build open source software. In general, projects are developed by a community of distributed contributors who share code, feedback, bug reports, and more. Best practices for this kind of open collaboration are fundamental to innersource, and we’ll spend the rest of this article going through a few key learnings, tools, and terms.
To learn more about how people start and contribute to open source projects, check out our guides . Lessons learned from the open source community If your team builds software, you’re probably already building with or on someone else’s open source project. The community is rich with lessons on how to collaborate across time zones, rally contributors, and manage large, complex projects. Here are a few to keep in mind as you set up an innersource practice: Open collaboration encourages more contributions More contributions mean more opportunities.
Open source projects can accept changes from anybody in the world. That’s a lot of brainpower dedicated to advancing a project, meeting user needs, and finding and fixing bugs. Similarly, innersource brings more ideas to the table. Teams can more easily innovate—and with more people inspecting code for errors and inconsistencies, they can build securer, more reliable software. Problems are found and fixed before the wrong person discovers them.
Developers don’t always have to start from scratch Anyone can discover and reuse open source projects for nearly any reason. People can even use them to build other things or modify them to suit their specific needs. Similarly, innersource code helps your team discover, customize, and reuse existing internal projects. They can also establish and build on a shared set of documented processes to optimize the way your company deploys and uses software.
This can lead to lower cost, greater flexibility, and an end to vendor lock-in. Transparent decision-making builds process, trust, and alignment Successful open source maintainers document their decisions by default. Because each conversation has its own URL and a history of comments for context, time zones matter less, and developers can work asynchronously without skipping a beat. Opening up your projects brings a new level of transparency to your organization.
Not only is the code visible but also the process and decision-making behind it. Well-documented conversations help developers on distributed teams get up to speed and start building. And with work happening in the open, collaboration can also include product managers, designers, security teams, and more. Participation is critical The success of any open source project depends on participation. There are many built-in reasons to contribute—to improve skills, find a mentor, or build a reputation, for example—but project maintainers also need to create a community culture that welcomes and encourages participation.
Within an enterprise, individual developers can pursue their interests, share ideas on a level playing field, and more easily learn from their peers. However, innersource also requires a cultural shift. Your team’s culture will need to encourage knowledge sharing and welcome contributions from across your organization. Core development teams strengthen a project’s process Open source projects may have thousands of contributors and community members, but a much smaller team is usually responsible for the project’s overall direction.
This speeds up decision-making and ensures that someone’s always responsible. For innersource projects, distributing control across a smaller group of participants frequently makes approvals and reviews more effective. Creating a small, cross-functional team of decision makers can also help teams stick to quality standards and gain executive support. An open source community behind your firewall Innersource has been described in a variety of ways and developers in organizations that already engage with large open source communities may not use the term innersource at all.
Instead, they think of it simply as the way they apply open source methodologies to software development behind their firewall. Innersource does not imply reduced security or privacy. You don’t necessarily have to share proprietary software publicly or invite any outside individuals to view source code or access innersource projects. Companies can rest assured that any nonpublic code will remain securely within their environment—and only developers with appropriate permissions will be able to contribute.
What we're seeing now is the technology has caught up with all these ideas of innovation and collaboration, and that's really critical for us. Joan Watson, Research and Development IT, Emerging Tech and Business Engagement, DXC Technology Adopting innersource practices is like starting an open source community within your organization. As with open source, transparent collaboration mobilizes a community’s collective knowledge and skills to create better software.
An innersource community, in contrast, contains the knowledge, skills, and abilities of people and tools within a single enterprise. Enhancing Collaboration Encourage participation to foster a collaborative environment, ensure that all employees can raise bugs and feature requests. Create a culture where contributions from any team member are welcomed, regardless of their ro
The rest of this page is on the live site.