Open source is famous for being unowned, but the best-kept parts of the commons are held by somebody. A foundation is the institution that holds what a decentralized project cannot hold itself: the trademark, the accumulated copyrights, the servers, the legal standing, and above all the patience to outlast the contributors' day jobs.

The binder files several kinds of holder. The Apache Software Foundation, the Linux Foundation, the Mozilla Foundation, the Eclipse Foundation and the Free Software Foundation all hold different assets and answer to different governance, but they share the same structural job.

The assets in the drawer

The foundation's drawer contains the things a repository cannot keep. The trademark is the most visible: the name Apache, the penguin's home, the Firefox logo, all registered and defended so that the word means something when it is used. Then the copyrights, where the project has asked contributors to assign or license them into a single holder who can enforce the license in court. Then the infrastructure: the mailing lists, the build machines, the domains, the accounts, the legal address where a subpoena or a donation can land.

A commons without a holder depends on the goodwill of whoever happens to control those assets today.

The governance it provides

A foundation also manufactures legitimacy. When a company wants to know that a project will be here in ten years, the answer is rarely the code alone; it is the foundation's charter, its board, its published rules about how decisions are made and how the project may be governed. The Apache Software Foundation's meritocratic rules, the Linux Foundation's project governance models, the Eclipse Foundation's working groups: these are instruments for making a commons legible to the institutions that fund it.

The governance is also where a foundation earns or loses the community's trust, because the rules decide who has a say when the project and its funders disagree. A foundation that only exists to collect sponsor logos is a different thing from one that actually governs, and the binder reads the difference in the charter, not the letterhead.

The money underneath

The funding model also explains the variety of foundations on the shelf. The Linux Foundation is a trade association that hosts projects; the Apache Software Foundation is a membership charity that stewards them; the Free Software Foundation is an advocacy organization that assigns and defends copyright. They all hold commons, but they are not the same kind of institution, and the difference shows in what they are willing to defend.

Foundations are funded by members, sponsors and grants, and the money buys the things volunteers cannot reliably supply: paid infrastructure staff, legal review, trademark defense, event coordination, and sometimes the maintainers' salaries themselves. The funding model quietly shapes the governance. A foundation whose budget comes mostly from a small number of large sponsors will govern differently from one supported by thousands of small members, and the binder reads the sponsor list as part of the license story.

When the holder is a company

Not every holder is a nonprofit. A single company can hold a project's trademark, domain, and copyright assignments, and many important projects are held exactly that way. The difference matters when the holder's interests change. A foundation is chartered to hold the commons in trust; a company holds it as an asset, and an asset can be sold, relicensed, or abandoned. The relicensing wave of the late 2010s, when companies changed their projects' licenses under pressure, is partly a story about which kind of holder was standing behind the code.

This is the quiet reason foundations exist at all. A project held by an institution answers the question of succession: what happens to the code when the company pivots, is acquired, or closes. The commons has outlived many of its corporate holders precisely because the foundation was standing behind it.

The record of stewardship

The binder's measure of a holder is the record. Did the foundation defend the trademark when it mattered? Did it keep the infrastructure running when the money thinned? Did it let the community govern, or govern it? The great foundations have decades of answers on file, and the answers are public, which is itself part of what a foundation is for: to make the holding visible.

What the reader takes away

The license says what you may do with the code. The foundation decides whether anyone will still be keeping it in ten years. Reading a project means reading both: the text of the license, and the structure of whatever holds the project up. A license on a repository with no holder is a promise; a license held by an institution is a promise with a custodian, and the custodian's character is part of the instrument.

The foundation is the shelf's slowest instrument. It does not write code, it does not ship releases, and it does not appear in the commit log. What it does is still be there when the people who did those things have moved on, and on the record that constancy is the whole job.

What the text grants

A holder for the assets a commons cannot hold itself: trademark, copyright, infrastructure, and legal standing.

What a reader should check

Who holds the assets, how the holder is governed and funded, and what its record of stewardship looks like.

The limit of this reading

A foundation protects the institution of the project, not its technical direction or its funding indefinitely.