We were three engineering teams at GitHub, all jumping into the same product space at the same time. Multiple concurrent work streams, tight timelines, and a shared codebase. Everything was moving ...

February 17, 2026 I’ve been asked this question more times than I can count. It usually comes up right after someone pitches an InnerSource program, gets conditional approval, and then gets told t...

CODEOWNERS files are one of those things that start out accurate and slowly drift. People change teams, leave the company, or shift responsibilities - but the CODEOWNERS file stays frozen in time. ...

If you manage dozens or hundreds of repositories, it’s surprisingly hard to answer a simple question: are all of them keeping their dependencies up to date? Some repos might have Dependabot enabled...

Understanding who contributes to your projects - and how - is essential for maintaining healthy open source communities. But getting a clear picture of contributor activity across repositories isn’...

How quickly does your team respond to issues? How long do pull requests sit before getting their first review? These questions matter for both open source maintainers and internal engineering teams...

Organizations accumulate repositories over time. Some are actively maintained, but many become abandoned - no commits, no issues, no activity. These stale repos clutter your catalog, confuse new te...

Running an Open Source Programs Office means juggling a lot of operational tasks: tracking repository health, monitoring contributor activity, ensuring dependency hygiene, and measuring how well yo...

InnerSource practices don’t just improve collaboration - they can directly improve your security posture and code quality. When teams share code across organizational boundaries, more eyes review c...

If you’re running an InnerSource program, one of the hardest questions you’ll face is: “How do we know it’s working?” The answer requires defining what InnerSource means for your organization and t...