Many of the most important open source projects belong neither to a person nor to a company, but to a foundation. For people using that software the difference may seem irrelevant: the code is the same, and so is the license. In reality, the presence of a foundation changes who controls the project's name, where donations go, how conflicts are resolved and how likely the project is to survive changes in strategy by those who fund it.
What a foundation actually does
Activities vary widely, but some functions recur:
- it holds the trademarks: the project's name and logo belong to the foundation, not to a single participant, and nobody can take them over;
- it manages money: it receives donations and sponsorships, and pays for infrastructure, travel, security audits or developers;
- it provides legal support: it answers licensing questions, handles any disputes and sometimes holds copyright or broad licenses on the code;
- it guarantees neutrality: competing companies contribute to the same project knowing that none of them can take control of it;
- it defines processes: rules on governance, releases, security and a code of conduct shared by all hosted projects.
The main foundation models
Not all foundations work the same way. A few types can be distinguished.
Foundations with a defined development model
The best-known example is the Apache Software Foundation. Each hosted project is run by a project committee, new projects go through an incubation period and the foundation promotes a set of community principles often called the «Apache Way»: public decisions, consensus, and individuals taking part in a personal capacity rather than as representatives of their employer.
Company consortia
Other foundations are organised as trade associations: companies pay membership fees and, in return, sit on the governing bodies. The Linux Foundation is the most obvious case and hosts, besides the kernel, a large number of projects and sub-foundations dedicated to individual ecosystems. The advantage is the ability to raise significant funds; the perceived risk is that the largest companies carry more weight.
Fiscal sponsors
Finally, there are organisations that give projects an «administrative home» without imposing a technical model. This is called fiscal sponsorship: the foundation receives and administers funds on the project's behalf, signs contracts and holds assets such as domains and trademarks, leaving technical management to the maintainers. The Software Freedom Conservancy is a well-known example of this approach.
Stewardship organisations
There are also bodies that do not host projects in the strict sense but look after definitions and principles: the Open Source Initiative maintains the Open Source Definition and approves conforming licenses; the Free Software Foundation promotes free software and maintains the GNU licenses.
Comparing the models
| Model | Who decides on code | Main source of funds | Weight of companies |
|---|---|---|---|
| Foundation with defined model | Project committees | Sponsors and donations | Indirect |
| Company consortium | Project technical bodies | Member fees | High in governing bodies |
| Fiscal sponsor | Project maintainers | Donations to the project | Low |
When a project joins a foundation
A project usually approaches a foundation at one of these moments:
- it becomes infrastructure for many organisations asking for guarantees of continuity;
- a company wants to donate it to attract contributions from competitors;
- the maintainers receive funds and do not want to manage them personally;
- disputes arise over the name or control.
Joining brings obligations: transferring trademarks, adopting governance rules, sometimes changing infrastructure. For a small project the organisational cost can outweigh the benefits; a fiscal sponsor is often a lighter compromise.
What it means for adopters
If you have to choose a component to build a system on for years, the presence of a foundation is a positive signal but not an absolute guarantee. It is still worth checking:
- that the project has active maintainers from several organisations;
- that the foundation actually holds the trademark and infrastructure;
- that releases and security fixes follow a public process;
- what stage the project is at, because some foundations distinguish between incubating, mature and archived projects.
A project archived by a foundation remains available but no longer receives development: treat it as abandoned software.
In short
- Foundations hold trademarks, manage funds and guarantee neutrality between contributors.
- There are foundations with their own development model, company consortia and fiscal sponsors.
- Joining a foundation brings stability but involves rules and transferring assets.
- For adopters, a foundation is a good sign, to be checked against the project's real activity.
