<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Jeff Bailey | InnerSource</title><link>https://jeffbailey.us/categories/innersource/</link><description>This website contains learning resources, opinions, and facts about software-related technology.</description><language>en</language><generator>Hugo</generator><atom:link href="https://jeffbailey.us/categories/innersource/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><item><title>What Is InnerSource?</title><link>https://jeffbailey.us/blog/2026/10/31/what-is-innersource/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2026/10/31/what-is-innersource/</guid><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>What X</category><category>InnerSource</category><category>Open Source</category><description><![CDATA[<p>Picture a company where five teams have each built their own logging library. Nobody knew the other four existed, so each team spent weeks solving problems a neighbor had solved months earlier. The company now pays to maintain all five.</p>
<p>InnerSource is a practice built to stop this from happening. It takes the way open source projects collaborate and applies it to the code inside your company: readable code, pull requests from outsiders, and maintainers who review and mentor. By the end of this article, you&rsquo;ll understand where InnerSource came from and the problem it solves. You&rsquo;ll also know the roles and principles that make it work, and where it falls short.</p>]]></description></item></channel></rss>