The Linux Foundation Forms from a Merger of Two Rival Consortiums

On January 22, 2007, the Open Source Development Labs and Free Standards Group announced that they would merge into the Linux Foundation. The organizations had overlapping members and ecosystem goals, but complementary emphases: OSDL supported Linux development/adoption, while FSG concentrated on standards and cross-distribution compatibility.

Calling them “rivals” captures institutional overlap more than a documented feud. The merger was presented as consolidation, not one consortium defeating the other.

OSDL supplied development and industry infrastructure

OSDL had been formed in 2000 with backing from technology companies to accelerate Linux in enterprise computing. It supported kernel developers and initiatives around data centers, carrier-grade/desktop Linux, legal/IP issues and adoption. Linus Torvalds became an OSDL fellow in 2003, giving him institutional support while he continued maintaining the kernel.

OSDL did not own the Linux kernel or control which patches Torvalds/subsystem maintainers merged. Corporate sponsorship and technical maintainer authority were separate.

FSG focused on standards

The Free Standards Group housed the Linux Standard Base and OpenI18N efforts. LSB specified interfaces/behavior intended to make applications more portable across conforming Linux distributions, supported by tests/certification. FSG also worked around internationalization and related standards coordination.

Standards could reduce fragmentation for software vendors, but they did not make distributions identical. Package managers, release policies, kernels, libraries beyond the specified baseline and administrator configuration still differed.

The January 2007 organization combined both missions

The new Linux Foundation described its role as promoting, protecting and standardizing Linux while providing resources/services for open-source collaboration. Jim Zemlin, previously FSG executive director, became executive director of the merged organization.

Industry members from hardware, enterprise software and Linux distribution businesses backed the foundation. Their participation provided funding and coordination but also made transparent project-specific governance important.

Trademark ownership remained distinct

Linux is a trademark of Linus Torvalds. The Foundation supports trademark administration/protection through established arrangements, but saying the merger transferred ownership of “Linux” to one corporate consortium would be wrong.

Likewise, kernel copyrights remain distributed among contributors under the kernel’s licensing structure. The Foundation is not a copyright owner for all Linux code.

The kernel retained its maintainer model

The kernel project continued to use mailing-list review, subsystem maintainers/trees and Torvalds’ mainline tree. The Foundation could employ/support people, fund infrastructure/events/legal programs and represent ecosystem interests; it did not become a product manager ordering kernel releases.

This separation is central to Linux governance: a neutral nonprofit can support shared infrastructure without replacing technical decision-making inside hosted/supported projects.

Standards remained part of the inheritance

The Foundation retained LSB/FHS and other referenced specification work. Over time, deployment portability increasingly also depended on language runtimes, containers, Flatpak/Snap and cloud-native APIs, while LSB adoption changed. The standards history still matters for ABI and filesystem-layout expectations.

The merger did not solve compatibility once and forever. Standards require versioning, conformance tests, implementer adoption and maintenance.

The umbrella expanded beyond Linux

The Foundation later hosted/founded many project foundations and initiatives, including the Cloud Native Computing Foundation in 2015, as well as projects in networking, security, embedded systems, supply chain and standards. Each uses its own charter/governing/technical structures; “Linux Foundation project” does not mean kernel maintainers govern it.

That growth made the 2007 merger an organizational ancestor of a much larger open-source institution, even though the initial name/mission centered on Linux.

Why the consolidation mattered

By 2007 Linux was critical commercial infrastructure. Funding maintainers, legal/trademark support, events, certification/standards and vendor coordination through two overlapping organizations created duplication. One institution could pool staff/member support and present a clearer interface to industry and community programs.

The evidence-backed conclusion is narrower than “Linux got one headquarters.” The merger created a shared institutional home for support and standards, while source ownership, distribution businesses and technical governance remained decentralized.

Related:

Sources: