But Is It Open?The online edition
Type & theme

Make yourself comfortable

Page color
Text size
20 px
Reading width
Ask about this chapter ↗

Your settings and place stay in this browser.

Chapter 3 · Timothy O’Brien

Who Stewards Open Source?

7 minute read29 source notesFree online edition

Pick a piece of open-source software you depend on and open the files that ship with it. If it’s Kafka or Tomcat, the NOTICE file names the Apache Software Foundation. If it’s Kubernetes, the project lives under the Cloud Native Computing Foundation, which is part of the Linux Foundation.1 If it’s one of the GNU tools, the Free Software Foundation often holds the copyright.2 And if it’s a small library someone put on GitHub, there may be no organization behind it at all, just a name and an email address.

Most people never look. I think the names are worth knowing, because these organizations sit near the center of open source. They can hold assets, document contributors’ grants, support enforcement, and set rules for how a project is run and who gets a say. When a new law touches software, some of them send people to talk to Congress, the European Union, and legislatures elsewhere.

What the plumbing looks like

A project’s license continues to grant rights whether or not it has a foundation. Enforcing those rights and looking after shared assets takes resources. A foundation can hold a project’s trademark, so nobody else can ship a fork under the same name. It can collect contributor agreements, so that years later there’s a clear record of who granted which rights to whom, and it can give the project a bank account and a lawyer to call.

There’s a quieter job too. When rival companies send engineers to work on the same code, competitors end up in the same room, and that raises antitrust questions. The Linux Foundation publishes an antitrust policy for exactly this reason. It encourages participants to get their own legal advice and says outright that nothing in its policies stops members from building, selling, or competing with their own products.3 Its European arm has a similar policy.4 It’s dull reading. It helps rivals manage the antitrust risks of building shared infrastructure.

The Apache Software Foundation

The Apache Group formed the ASF in 1999.5 Its governance is designed to keep control with individual contributors rather than corporate sponsors.

The ASF describes itself as a charitable nonprofit that supports communities of open-source projects through collaborative, consensus-based development.6 By its own count it had about 10,000 committers (people with permission to change a project’s code directly) across roughly 300 projects at the end of its 2026 fiscal year.7 Each project is run by a Project Management Committee of active contributors. The committee answers to a board elected by the foundation’s members, and the members are individuals, not companies. A company can employ half of a project’s contributors and still get no seat for it. Its engineers take part as individuals.8

Apache calls the culture around this “the Apache Way,” and some of its habits are concrete enough to describe. Decisions are supposed to happen on public mailing lists. The community has a saying for it: if it didn’t happen on the list, it didn’t happen.9 Votes are cast in the open as +1, 0, or -1, and a -1 on a code change is a veto that counts only if it comes with a technical reason.10 New projects start in an incubator. Before one graduates to a full Apache project, part of the check is whether its contributors are spread widely enough that no single company could walk away and leave the project dead.11 The foundation’s motto for all of this is “community over code.”8

The ASF also has a code of conduct, which expects people to argue about the work and leave each other out of it.12 That matters because a project’s future gets decided in public, on the list.

The Linux Foundation

The Linux Foundation was founded in 2007. It provides organizational, legal, financial, and infrastructure support around the kernel and many other projects, and Linux creator Linus Torvalds is a Fellow.13 Its project-hosting page lists around 850 projects, including Kubernetes, Node.js, and a growing number of AI and data efforts. It now hosts open standards and specifications as well as code.14

It’s built differently from Apache. Under the US tax code, the Linux Foundation is a 501(c)(6), the category for trade associations and similar membership groups, while the ASF is a 501(c)(3), a charity.15 The difference shows up in funding and in who sits on the board.

The Linux Foundation is also the clearest example of a steward doing advocacy. When policy touches open source, it engages with governments, including the United States and the European Union. A lawmaker drafting cybersecurity or AI rules needs someone who can explain what an open-source maintainer actually controls. The European Union’s Cyber Resilience Act, which sets cybersecurity requirements for hardware and software products sold in the EU, is a recent case: several foundations pushed to change how the law would treat open-source developers.16 You don’t have to follow those bills, but someone is.

The Open Source Initiative

Eric Raymond, Bruce Perens, and others founded the OSI in February 1998, and it became the steward of the Open Source Definition.17 The definition lists ten criteria a license must meet to be called open source, and the OSI reviews licenses against it and approves the ones that pass.18

For the influence it has, the OSI is a small organization. It’s a California public-benefit corporation with 501(c)(3) status and an elected board.19 It also published the Open Source AI Definition, which much of the second half of this book turns on.20

The Free Software Foundation

The FSF came first. Richard Stallman announced the GNU project in 1983 and founded the FSF in 1985.17 It wrote the GNU General Public License, the best-known copyleft license (one that preserves recipients’ source rights when covered versions are distributed), and it frames software freedom as users’ rights to run, study, change, and share software.21 It’s a 501(c)(3) charity, and much of its support comes from individuals.22

The FSF and the OSI approve many of the same licenses but differ on why those permissions matter. The FSF still maintains a large body of GNU software and speaks for a rights-centered view that many people hold deeply.

Creative Commons

Creative Commons does for creative work roughly what the others do for software. Its licenses cover text, images, music, video, teaching materials, and datasets. They aren’t meant for software.23 It was founded in 2001, with Lawrence Lessig among its founders.24

It belongs in this chapter because AI openness involves more than code. Training data, documentation, model cards (the short documents that describe what a model is and how it was made), and the cultural works models learn from raise their own rights questions. Creative Commons supplies a shared vocabulary for many of them. It also speaks up for the people who use its licenses and argues for more openness in general. A written policy bars donors and sponsors from controlling its vision, programs, or events.25

Other stewards, including Eclipse, Mozilla, the Software Freedom Conservancy, and MLCommons, appear later in the book.

The money, and the case against

The money comes from corporate memberships and sponsorships, grants, events, training and certification, and individual donations. Membership levels affect who can participate in governance. A company can join a foundation at a top tier and help fund the whole organization. The Linux Foundation, for example, has Platinum, Gold, and Silver tiers, plus a no-cost associate membership for qualifying nonprofits, open-source projects, and governments.26 An individual can make a much lighter contribution, such as an FSF associate membership27 or a donation to the OSI or Creative Commons.

Funding buys more than a logo. At the Linux Foundation a Platinum membership comes with a board seat, and Gold members can elect board representatives.28 Large sponsors get keynotes, visibility, and easier access to staff. That pays for shared infrastructure, but board participation at that price is expensive for small companies and individuals. The Apache model is partly an answer to this: sponsors fund the foundation, but project decisions are supposed to stay with the people doing the work.29

Many projects have no umbrella organization, board, or advocate in a policy debate. A project’s license does not establish that any of those supports exist. Foundations matter, but joining one is only one way to organize the work.

The most important participant

The licenses grant their rights whether or not you support a steward. If you want to participate, time can matter as much as a donation. You can file a careful bug report, answer someone’s question, review a pull request, fix the documentation, or read a project’s mailing list for a few weeks until you understand how its decisions get made. The longer you do it, the more obvious it becomes that these institutions are made of people, some of them volunteers and many of them engineers whose employers pay them to work on shared code.

Knowing who maintains open source is half the picture. The word “open” also gets attached to a lot of things that have little to do with any of these organizations or their licenses, and the next chapter sorts out what open source is not.

Notes

  1. Cloud Native Computing Foundation, “Who We Are,” https://www.cncf.io/about/who-we-are/. ↩

  2. Free Software Foundation, “Why the FSF Gets Copyright Assignments from Contributors,” GNU Project, https://www.gnu.org/licenses/why-assign.html. Developers of a GNU package can choose to assign copyright to the FSF or keep it. ↩

  3. Linux Foundation, “Antitrust Policy,” https://www.linuxfoundation.org/legal/antitrust-policy. ↩

  4. Linux Foundation Europe, “Antitrust Policy,” https://linuxfoundation.eu/policies/antitrust-policy. ↩

  5. The Apache Software Foundation, “History of the Apache Software Foundation,” https://www.apache.org/history/ (incorporated June 1999 as a 501(c)(3)). ↩

  6. The Apache Software Foundation, “About,” https://www.apache.org/foundation. ↩

  7. The Apache Software Foundation, FY26 announcement, https://news.apache.org/foundation/entry/the-apache-software-foundation-advances-open-source-infrastructure-and-celebrates-community-growth-in-fy26 (10,225 committers across 302 projects). ↩

  8. The Apache Software Foundation, “A Primer on ASF Governance,” https://www.apache.org/foundation/governance/; The Apache Software Foundation, “Briefing: The Apache Way,” https://www.apache.org/theapacheway/ (individuals participate, not organizations; no organization gains control through employing committers or sponsorship; “Community Over Code”). ↩1 ↩2

  9. Apache Community Development, “Mailing lists,” https://community.apache.org/contributors/mailing-lists.html. ↩

  10. The Apache Software Foundation, “Apache Voting Process,” https://www.apache.org/foundation/voting.html. A veto without a technical justification is invalid. ↩

  11. Apache Incubator, “Guide to Successful Graduation,” https://incubator.apache.org/guides/graduation.html (a diverse community has at least three legally independent committers and no single company or entity vital to the project’s success). ↩

  12. The Apache Software Foundation, “Code of Conduct,” https://www.apache.org/foundation/policies/conduct. It lists personal attacks among unacceptable behavior, puts enforcement first with each PMC, and sends foundation-wide matters to the ASF President or board. ↩

  13. Linux Foundation press release on Linus Torvalds, https://www.linuxfoundation.org/press/press-release/linux-creator-linus-torvalds-honored-by-nec-cc-foundation; CIO Staff (IDG News Service), “OSDL, Free Standards Group to Merge,” CIO, 22 January 2007, https://www.cio.com/article/264947/linux-osdl-free-standards-group-to-merge.html (the merger that formed the Linux Foundation in 2007; secondary source). ↩

  14. Linux Foundation, “Project Hosting,” https://www.linuxfoundation.org/projects/hosting. Project counts are the foundation’s own and change often. ↩

  15. Linux Foundation bylaws, https://www.linuxfoundation.org/legal/bylaws; The Apache Software Foundation, “Sponsorship,” https://www.apache.org/foundation/sponsorship.html. ↩

  16. Dirk-Willem van Gulik, “Save Open Source: The Impending Tragedy of the Cyber Resilience Act,” The ASF Blog, written ahead of the July 2023 ITRE committee vote, https://news.apache.org/foundation/entry/save-open-source-the-impending-tragedy-of-the-cyber-resilience-act (describes work by the ASF, Eclipse, the Linux Foundation and others on the draft); European Commission, “Cyber Resilience Act: Open source,” https://digital-strategy.ec.europa.eu/en/policies/cra-open-source (the final Regulation (EU) 2024/2847 excludes non-monetized FOSS and creates a lighter “open-source software steward” category); European Commission, “Cyber Resilience Act,” https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act (mandatory cybersecurity requirements for manufacturers of hardware and software “products with digital elements”). These sources document the advocacy, not how much of the final text it changed. ↩

  17. Open Source Initiative, “History of the Open Source Initiative,” https://opensource.org/about/history-of-the-open-source-initiative (founded by Eric Raymond and Bruce Perens in late February 1998); Richard Stallman, “Initial Announcement,” GNU Project, 27 September 1983, https://www.gnu.org/gnu/initial-announcement.html (work began in January 1984); Richard Stallman, “The GNU Project,” https://www.gnu.org/gnu/thegnuproject.html (FSF created in 1985). ↩1 ↩2

  18. Open Source Initiative, “The Open Source Definition,” https://opensource.org/osd; OSI, “License Approval,” https://opensource.org/approval. ↩

  19. Open Source Initiative, “About,” https://opensource.org/about; OSI, “Welcoming Duane O’Brien as Executive Director,” https://opensource.org/blog/welcoming-duane-obrien-as-executive-director-of-the-open-source-initiative. ↩

  20. Open Source Initiative, “The Open Source AI Definition 1.0,” https://opensource.org/ai/open-source-ai-definition. ↩

  21. Free Software Foundation, “What is Free Software?,” GNU Project, https://www.gnu.org/philosophy/free-sw.html; GNU General Public License, version 3, https://www.gnu.org/licenses/gpl-3.0.html. ↩

  22. Free Software Foundation, “Financial information,” https://www.fsf.org/about/financial. ↩

  23. Creative Commons licenses are designed for creative works and are not recommended for software; see https://creativecommons.org. ↩

  24. Creative Commons, “History,” https://creativecommons.org/mission/history/ (founded in 2001 by Lawrence Lessig, Hal Abelson, and Eric Eldred; first licenses published in 2002). ↩

  25. Creative Commons, “Contributions Policy,” https://creativecommons.org/support-cc/creative-commons-contributions-policy. ↩

  26. Linux Foundation membership agreement, https://cdn.platform.linuxfoundation.org/agreements/tlf.pdf. ↩

  27. Free Software Foundation, “FSF associate membership,” https://www.fsf.org/associate/. ↩

  28. Linux Foundation, member benefits deck, https://www.linuxfoundation.org/hubfs/lf_mem_benefits_0010625.pdf. ↩

  29. The Apache Software Foundation, “Sponsorship,” https://www.apache.org/foundation/sponsorship.html. Whether sponsorship ever turns into governance influence in practice is worth examining case by case. ↩

From But Is It Open? by Timothy O’Brien (Discursive, 2026). © 2026 Timothy O’Brien. All rights reserved.

Chapter 37 min leftNext →

The book, chapter by chapter.

Source note

Go to the notes & sources ↓

The vocabulary.

A short guide to the book’s recurring terms. Follow each chapter for the argument and its sources.

Open weights
A release makes a trained model’s learned parameters available. The accompanying terms decide what you can do with them. Access to weights alone does not provide the training data, code or recipe. Read the chapter →
Copyleft
A way of using license conditions to preserve recipients’ freedoms when covered software is passed on. The obligations depend on the license and on what you distribute or make available. Read the chapter →
Permissive licenses
Licenses such as MIT and Apache 2.0 grant broad reuse rights with comparatively few conditions. Notice obligations still apply, and a software license does not automatically cover a release’s data or other components. Read the chapter →
Reproducibility
The ability to reconstruct and examine how an artifact was produced using the resources that are published. Running an existing checkpoint is a different achievement from rebuilding its training. Read the chapter →
Governance
Who can participate, who makes decisions, and how authority over a project or release is shared. A right to use the code does not by itself create a voice in upstream decisions. Read the chapter →
Training data
The examples used to train a model. Publishing the data, documenting its provenance and describing how it was filtered are distinct kinds of disclosure; privacy and other rights may limit what can be shared. Read the chapter →

A passage worth sharing.

Select a passage in the chapter, or share the one you’re reading.