The PHP community has officially opened a vote on a Request for Comments (RFC) to transition the project’s core licensing from its long-standing custom terms to the industry-standard BSD 3-Clause license. Led by release manager and contributor Ben Ramsey, the initiative seeks to replace the current bifurcated licensing model with a unified framework by the conclusion of the voting period on April 4, 2026.
This transition addresses nearly two decades of administrative complexity stemming from the project’s reliance on the PHP v3.01 license for core code and the Zend v2.0 license for the Zend Engine. According to reports from LWN and Noise.getoto, this dual-licensing structure has become a significant source of confusion for legal teams and developers alike since its establishment in 2006. By adopting the Modified BSD license, the project aims to align with the modern open-source ecosystem, reducing the legal friction associated with custom licenses that have not been updated to reflect current industry norms.
Structural Changes and the Transition Roadmap
The core of the proposal involves a move from the split PHP v3.01 and Zend v2.0 licenses to a unified BSD 3-Clause model, also known as the New BSD or Modified BSD license. Currently, the PHP source tree is divided, with the bulk of the language governed by the PHP License while the Zend directory—which houses the engine that executes the code—operates under its own specific Zend Engine License. As noted by Scinet, this unification will treat both components under the same legal text, effectively streamlining the project’s intellectual property profile.
The implementation timeline for this change is tied directly to the project’s versioning cycle, with the new terms slated to take effect in the next PHP 8.x release. This means that existing versions of PHP, such as 8.2 or 8.3, will continue to operate under their original licenses until the transition version is officially tagged and distributed. The license change becomes legally relevant for a user or organization as soon as they begin distributing versions of the software that contain the updated license text.
For enterprise organizations, the “next PHP 8.x” milestone is a critical marker for maintenance schedules and internal compliance audits. Since many large-scale operations rely on stable, long-term support versions of PHP, the shift to BSD 3-Clause will likely be integrated into future security patches and minor updates. This allows organizations to plan for the legal change alongside their standard technical upgrade paths, ensuring that no sudden or unexpected compliance requirements are forced upon current production environments.
The PHP project leadership determined that the historical need for “custom licensing” has passed, as the industry has coalesced around a few well-understood, permissive licenses. While the original PHP and Zend licenses were crafted to address the specific needs of the web in the early 2000s, they are now viewed as outliers in an ecosystem dominated by MIT and BSD terms. By moving to a standard Open Source Initiative (OSI) approved license, PHP removes the “license proliferation” burden, making it easier for corporate legal departments to approve the use of the language without requiring a custom review of unique terms.
This roadmap also ensures that the project remains accessible to the widest possible range of contributors and distributors. By selecting the BSD 3-Clause license, the project maintains its permissive nature while adopting a text that is universally recognized by automated license scanners and compliance tools. This reduces the operational overhead for distribution maintainers who previously had to account for two different, non-standard licenses within a single software package.
Leadership and the RFC Legislative Process
Ben Ramsey, a prominent figure in the PHP development community, is serving as the lead organizer and director of the transition initiative. His role involves steering the RFC through the community’s established governance model, which relies on a formal voting process to enact major changes to the language or its administration. According to Noise.getoto, the current RFC is the culmination of an effort to simplify the project’s legal standing after years of internal discussion regarding the complexity of the 2006-era terms.
The RFC process is a transparent legislative mechanism where contributors discuss the merits of a proposal before casting their votes. The active voting window, which is currently open, provides the community with a clear timeframe to voice support or concerns before the April 4 deadline. This democratic approach ensures that the transition to BSD 3-Clause is not a top-down mandate but a consensus-driven move supported by the individuals who actively maintain and build the language.
The historical context of the 2006 licensing decision explains why the project remained static for two decades. At that time, custom licenses were a common way for open-source projects to define specific usage rights and brand protections. However, as the open-source landscape matured, these bespoke licenses began to create “license silos,” where code could not easily be shared or integrated between projects due to minor textual differences. The current vote represents a formal acknowledgement that the specialized protections of the old PHP and Zend licenses are no longer necessary for the project’s success.
Governance in the PHP project is structured to prioritize stability, which is why a license change requires such a high level of community engagement. By utilizing the RFC system, Ramsey and other proponents of the change are providing a documented audit trail of the decision-making process. This transparency is vital for downstream users, such as Linux distribution maintainers and cloud service providers, who need to understand the legal provenance of the software they provide to millions of customers.
Impact Assessment for Developers and Technical Operations
For the vast majority of developers writing PHP applications, APIs, or client-side projects, the transition to the BSD 3-Clause license will have no technical impact. Scinet reports that the change involves no modifications to the language’s runtime behavior, deployment strategies, or hosting requirements. Developers can continue to write and execute PHP code exactly as they do today, without worrying about how the underlying engine is licensed at the source level.
Crucially, there is no requirement for application developers to relicense their own application code. The change to the PHP core license does not “leak” into the software built on top of it. This means that developers building proprietary, closed-source applications using PHP are not forced to open-source their work, nor are they required to adopt BSD terms for their own repositories. The relationship between the language license and the user’s code remains strictly separated, preserving the permissive environment that has fueled PHP’s adoption.
The lack of impact extends to the Composer ecosystem and general package management. Since the license change affects the PHP binary itself rather than the libraries and frameworks written in PHP, the thousands of packages available via Packagist will remain under their own respective licenses. This ensures that the transition will not cause a cascade of licensing updates across the global PHP dependency graph, allowing the ecosystem to remain stable during the project’s legal modernization.
Standard users who do not distribute the PHP binary itself are essentially encouraged to take a “do nothing” approach. If an organization simply uses PHP to serve a website or run internal scripts, they are not considered “distributors” under the terms of the BSD 3-Clause license. Consequently, the new requirements for notice and attribution do not apply to these users, as they are not passing the software on to third parties. The transition is designed to be invisible to the end-user, focusing instead on the legal relationship between the project and those who redistribute the language core.
Compliance Requirements and Legal Limitations
While most users will see no change, entities that distribute PHP binaries, such as those creating custom Docker images or operating system distributions, must adhere to specific obligations under the BSD 3-Clause terms. The most significant requirement is the inclusion of the original copyright notice and the list of conditions within the distribution. According to Scinet, this ensures that the original authors receive credit and that the terms of the license remain attached to the software as it moves through the supply chain.
The BSD 3-Clause license also includes a specific restriction regarding the use of project or contributor names. Organizations are forbidden from using the names of the PHP project or its contributors to endorse or promote products derived from the software without prior written permission. This “non-endorsement” clause is a standard feature of the Modified BSD license and serves to protect the reputation of the core developers from being unfairly associated with third-party commercial offerings.
For enterprises, these requirements represent a shift from the older, more ambiguous custom terms to a set of clear, actionable rules. However, failure to include the necessary notices in redistributed versions of PHP could create compliance risks. Legal and security reviews within large corporations often flag missing license files or incorrect attribution as blockers for software deployment. Therefore, teams responsible for packaging PHP for internal or external distribution must update their build pipelines to ensure the new BSD 3-Clause text is correctly included.
The drive toward a standard license is largely motivated by the desire to avoid this type of “avoidable friction.” Legal teams are generally more comfortable with the BSD 3-Clause license because its implications are well-understood and have been tested in various jurisdictions. By moving away from the custom PHP v3.01 and Zend v2.0 licenses, the project eliminates the need for lawyers to interpret unique phrasing, thereby speeding up the adoption of new PHP versions in highly regulated corporate environments.
Closing
The transition of the PHP project to the BSD 3-Clause license represents a significant step toward legal modernization and community unification. By moving away from the dual-licensing model that has governed the project since 2006, PHP is removing historical confusion and aligning itself with modern open-source best practices. The outcome of the current vote, which concludes on April 4, 2026, will set the stage for the next phase of the language’s development under a simplified legal framework.
As the community monitors the final days of the RFC process, the focus remains on ensuring a smooth transition for the upcoming PHP 8.x release. This move not only simplifies the project’s administration but also reinforces PHP’s position as a permissive and developer-friendly language. Ultimately, the shift to an industry-standard license like BSD 3-Clause ensures that PHP remains a viable and legally sound choice for the next generation of web development.
