Our company (which runs an ASF project you probably have heard of as SaaS for enterprise customers) is pretty well-separated. Separate bug trackers with dual tickets, separate mailing lists, etc. The problem is that our corporate developers make up about 80% of the developers on the upstream ASF project. We took the ASF developers and hired them.<p>There are people who want to get things done in the upstream project, and they try... but they just don&#x27;t have the resources, because most of the people on the project are busy doing their jobs.<p>Excluding corporate-support-contract-of-this-project employees from having contributor rights to the upstream project might work, but then you get the opposite problem: a downstream that&#x27;s increasingly diverged from the upstream (because if the customers want a feature, but upstream won&#x27;t take the patch, forking is pretty much necessary) where the &quot;free core&quot; of the upstream begins to stagnate because (in relative terms) nobody&#x27;s eyes are on that code.