Here’s something that doesn’t happen every day. Twenty-three years after its inception, the PHP license is officially retired. The PHP Group, responsible for one of the most ubiquitous server-side scripting languages on the planet—the engine behind WordPress, for crying out loud—has officially ditched its idiosyncratic licensing in favor of the battle-tested BSD 3-Clause.
This isn’t just a minor bureaucratic reshuffle. It’s a profound architectural cleanup, a shedding of legacy baggage that has, for years, created friction for developers and distributors alike. Ben Ramsey, a release manager with PHP, penned the initial announcement, and it was cemented with a formal notification to the Open Source Initiative (OSI) license review mailing list. The message was stark: PHP License 3.01 is out, and the BSD 3-Clause is in. The project now actively discourages the use of the old license for new work.
Why the change? It boils down to practicality, and frankly, a bit of historical artifacting. The original PHP license, born from Rasmus Lerdorf’s modifications to Apache 1.0 in 1998, was eventually joined by the Zend Engine License. This dual-licensing approach, while perhaps sensible at the time, became unwieldy. The Zend Engine License, never OSI-approved and not GPL-compatible, only covered a portion of the codebase. Meanwhile, condition 4 of the PHP License itself—which restricted derived products from using the name “PHP”—created significant ambiguity, particularly for Linux distributions like Debian that routinely patch and redistribute software.
Ramsey himself elaborated, noting the absurdity: “The Zend Engine, once imagined as a separable product, had been inextricably bound to PHP for 25 years; the notion that it required its own license had become a historical artifact.” Exactly.
And stripping away the PHP-specific and Zend-specific clauses from both original licenses? What remained was, essentially, the BSD 3-Clause all along. It’s like finding an old, overly ornate key that only opens a door you can now simply push open. The move is a win for simplicity and, by extension, for the entire open-source ecosystem.
A Standardization Win for Open Source
The OSI’s long-standing mission has been to promote adoption of existing, well-understood licenses, rather than the creation of new ones. The PHP Group’s decision aligns perfectly with this philosophy. By adopting BSD 3-Clause, they’re opting for a license that is widely understood, permissive, and compatible with the GPL. This means fewer headaches for companies integrating PHP into their products and less confusion for individual developers contributing to or building upon the language.
This isn’t just about cleaning up old code. It’s about removing a subtle, yet persistent, barrier to entry and adoption. For years, the PHP license (and its companion) represented a tiny island of custom licensing in a sea of standardized, permissive open-source agreements. Now, that island has been submerged, and PHP joins the vast continental shelf of BSD-licensed software.
Why Does This Matter for Developers?
For many developers, especially those working with PHP, this change is less about philosophical shifts and more about practical benefits. The BSD 3-Clause is known for its simplicity and permissiveness. It allows for wide use, modification, and distribution, including in proprietary software, with only minimal requirements for attribution. This drastically reduces the legal overhead and compliance concerns that might have previously accompanied deep integration of PHP.
Think about it: the days of poring over obscure license clauses to ensure compliance are, at least for PHP, largely over. This fosters a more welcoming environment for contributions and commercial adoption. It’s a signal that the PHP project is serious about modernizing and streamlining its development and distribution model. It aligns PHP with a significant portion of the open-source landscape, making it an easier, more predictable choice.
A Look Back: The Quirks of PHP Licensing
It’s worth a brief moment to appreciate the historical quirkiness of the PHP license. Unlike the clean, philosophical purity of the GPL, or the straightforward permissiveness of the MIT license, the PHP license (and its Zend Engine sibling) always felt a bit… bespoke. It was a product of its time, evolving organically from early web development’s less standardized approach. But as the web matured, and open-source licensing became more codified and understood, these older, custom licenses began to stand out for all the wrong reasons.
Ramsey’s chronicle of the journey, spanning multiple years and involving various stakeholders, is a proof to the dedication of the community to address this legacy issue. It’s a reminder that even established projects must periodically re-evaluate their foundational elements to stay relevant and accessible.
So, the PHP license is dead. Long live the BSD 3-Clause. It’s a sensible, pragmatic, and long-overdue evolution.
🧬 Related Insights
- Read more: Vercel AI SDK in Production: Unseen Pitfalls
- Read more: Caddy Tunnels Private Servers Over QUIC
