Open-source maintainers get a funding model that might hold
A consortium of large users will pay for maintenance of the libraries their products depend on, with no say over the roadmap.
The structure is unusual in the detail that matters: money goes in, governance does not come out. Contributing companies fund a pool, an independent board allocates it, and sponsors get no vote on direction.
The problem being solved is well documented. A striking share of commercial software depends on components maintained by a handful of unpaid people, and the failure mode is not a dramatic breach so much as quiet abandonment.
Allocation will prioritise libraries with high dependency counts and low contributor counts — the exact overlap that keeps security teams awake.
Maintainers have responded with cautious interest. Previous attempts foundered either because the money came with product demands, or because applying for it took more time than the maintenance itself.
The test will be year three. Funding programmes of this kind are easy to launch during a good quarter and quietly dropped during a bad one.
