Have you ever been blocked in your next coding task because another team didn’t have time to add a feature in their system that you depend on? Perhaps after a while you even had to do some extra work in your project to work around the missing feature. How nice would it be to never be blocked in this way?
LearnInnerSource contributors operate outside of regular team boundaries, they are the links crossing organizational silos. As such, they need to be aware of a few common practices that make this work more effective.
LearnIn the last segment we have outlined why you would want to reuse components and become active as a Contributor. This article shares best practices on how to successfully contribute your changes to the host team’s code base.
LearnAre you ready to start contributing to other teams projects/repos? Do you look forward to reducing your blockers not by management escalation but by collaboration? This section gives practical advice and highlights gotchas to remember when making an InnerSource contribution. It enables you and the host team to have as pleasant an experience as possible, setting the foundation for more contributions and great collaboration.
LearnContributors are the life blood of InnerSource projects. Every project that is run as an InnerSource project comes both with the promise and with the ultimate goal of expanding their development team beyond the original founders, tapping into the potential of further collaborators amongst users (also sometimes referred to as customers in corporations) of that project.
LearnThanks for reviewing the Contributor segment of the InnerSource Commons Learning Path. With this section you’ve learned about the Contributor role - the life blood of InnerSource projects. Contributors are external to the component owners' team, and they bring additional valuable input to the project.
Learn