One of my jobs is to help software development teams in the .NET space improve their efficiency by revisiting their tools, processes, architecture and infrastructure. Collaboration between teams is often a struggle because of the way teams are organized, the tools they are using and the mindset they are following. Inner Sourcing is the idea of applying the best practices of successful open-source projects on your software development team(s).

In this talk, I'll talk about the role of source control, how to run efficient reviews, what to document and what not, relevant design patterns, package dependency management, unit testing, code quality, branching and versioning strategies, build scripts and more. In essence, I'll share everything I know that can help developers to deliver high-quality code to other developers without unnecessary ceremony.

Takeaways
Ways of working, technical patterns and tools to build components and packages that software teams can share and evolve, without hand-offs and complicated team dependency management.

Session outline
• What a high-quality code repository should look like
○ Read-me
○ Build scripts
○ Unit tests
○ Branching & versioning
○ Issue tracking and collaboration
• Tools
○ The role of a good source control system in efficient collaboration (e.g. forks, pull requests)
○ Review procedures, contribution guidelines, templates
○ Static code analysis & coding conventions
○ Release note generation
○ Documentation sites
○ Roslyn / .editorconfig / prettier
○ API snapshot testing
• Design principles
○ Abstractions and boundaries
○ Principles of successful component/package management
Versioning boundaries