Open Source Foundations Compared: The Governance Story Headlines Overlook

Archi3 min read

open-sourcegovernancenonprofits

Contents
  1. The Part of Open Source Governance Nobody Headlines
  2. Three Models, Three Sets of Rules
  3. Money and Influence
  4. The Contributor License Question
  5. What the Press Releases Leave Out
  6. How to Choose

The Part of Open Source Governance Nobody Headlines#

When a project joins the Linux Foundation (LF), picks up an Apache license, or signs a contributor agreement with the Software Freedom Conservancy (SFC), the press release usually mentions scale: number of contributors, lines of code, corporate members. The details that actually shape a project's future stay buried in bylaws and budget documents. Those details are where the three organizations split most sharply, and where teams choosing a home for their code should look first.

Three Models, Three Sets of Rules#

The Linux Foundation is a federation of funds and projects. It hosts thousands of projects, from the kernel to CNCF, and its operating model is corporate membership: companies pay dues, seats on governing boards follow the money, and project budgets often come from member contributions. LF projects typically keep their own technical charters, but the foundation controls trademarks, events, and the legal umbrella. The Apache Software Foundation (ASF) is a membership corporation run by individual contributors, not companies. Its board is elected by ASF members, and its projects follow the Apache Way: consensus voting, public mailing lists, and no corporate seats. The SFC takes a different tack. It is a small nonprofit that provides fiscal sponsorship and legal defense for projects that want to stay independent, including high-profile copyright enforcement work on behalf of its members.

Money and Influence#

Headlines about LF membership dues rarely explain what those dues buy. In practice, member companies get board representation that can shape foundation priorities, event access, and early input on initiatives. That is not automatically bad: corporate funding pays for legal staff, security audits, and infrastructure that volunteer projects struggle to afford. But the trade-off is visible in project roadmaps when a funder's priorities pull one way and a community's maintenance needs pull another. The ASF avoids this by design. It accepts corporate sponsorships but does not sell governance seats, which keeps the member base individual and slow to change. The SFC's model is leaner still: it takes a small administrative cut and leaves project decisions to the project.

The Contributor License Question#

One practical difference affects every developer who submits a patch. Apache projects require a Contributor License Agreement (CLA) that grants the foundation broad rights to the code. LF projects vary by project charter, and many use a Developer Certificate of Origin (DCO) instead, which is lighter but offers less legal certainty for corporate adopters. The SFC generally opposes CLAs that assign copyright away from contributors, arguing they weaken the copyleft bargain. The practical result: if your company's legal team wants clear patent grants and relicensing rights, an Apache-style CLA is familiar ground. If your contributors care about retaining copyright, an SFC-sponsored project may fit better. Neither choice is free. Each shifts risk to a different party.

What the Press Releases Leave Out#

The bigger story is fiscal health. The ASF runs on donations and sponsorships and has periodically warned about budget pressure as its project count grows. The SFC operates with a handful of staff and depends on individual donations and litigation settlements. The LF's corporate dues give it the largest balance sheet, but that scale also means its projects compete for attention inside a large portfolio. A project that joins a big foundation may get marketing reach and legal cover while waiting longer for dedicated community funding. A project that stays independent may keep its identity and move faster, at the cost of absorbing legal risk alone.

How to Choose#

Three questions separate the options. First, who decides? If corporate members will control the board, expect roadmap pressure when budgets tighten. If individual members decide, expect slower consensus and less cash. Second, who owns the trademark and the code? A foundation that holds the trademark can protect users from a hostile fork, but it can also block a community's preferred name. Third, what happens if the money stops? The ASF has survived lean years by shrinking; the SFC has survived by staying small; LF projects have sometimes been spun out or archived when sponsors left. Ask for the exit plan before you sign.

The headlines count contributors and stars. The bylaws decide who can say no, who pays for the lawyers, and who keeps the name if the project splits. Read those before the press release.

More articles