This guide explains PHP's transition to the BSD 3-Clause license, a significant change that simplifies compliance for downstream projects and Linux distributions. The previous license, PHP License 3.01, contained specific restrictions and was not compatible with the GPL.
The transition to the BSD 3-Clause, a widely recognized permissive license, offers greater clarity and support for tools. This change is beneficial for developers, package maintainers, and projects that incorporate or redistribute PHP code.
The BSD 3-Clause license is now the official license of PHP, replacing the previous custom licenses. This transition formalizes PHP's alignment with open-source standards.
Prerequisites
- Operating System: An operating system compatible with PHP
- PHP: Updated version of PHP with BSD 3-Clause license
- Zend Engine: Version compatible with the new license
- Development Tools: Text editor or IDE for code modification
- Internet Access: To download any updates or documentation
Procedure to Update Your PHP Project's License
By the end of this guide, you will have updated your PHP project's license to BSD 3-Clause, aligning it with PHP's new official license.
- Verify the current license version of your PHP project. This step is crucial to understand if an update is necessary.
- Update your project's license file. Replace the content with the text of the BSD 3-Clause license.
- Modify the header files of your PHP scripts. Ensure each file contains the new BSD 3-Clause license text.
- Check the project documentation. Update any references to the old PHP 3.01 or 3.0 license with the new BSD 3-Clause.
- Verify compatibility with other projects. If your project interacts with libraries or frameworks that require specific licenses, ensure that the BSD 3-Clause is compatible.
- Communicate the change. Inform users and project collaborators about the license update.
Verification and Troubleshooting
By the end of this section, you will be able to verify the correct functioning of the PHP license change and resolve any issues.
How to Test if It Works
- Verify the Current License: Access the official PHP website and check the license-dedicated section to confirm that the BSD 3-Clause has been adopted as the new license.
- Check Repositories: Verify that the official PHP and Zend Engine repositories use the new BSD 3-Clause license.
- Documentation: Read the official documentation to ensure that all mentions of the old PHP 3.01 license have been removed or updated.
What to Do if It Fails
- Compatibility Issues: If you encounter compatibility issues with other licenses, consult the BSD 3-Clause documentation to understand how to resolve any conflicts.
- Community Support: Contact the PHP community through official forums or support channels to get assistance with any license transition issues.
- Updates: Ensure you are using the latest versions of PHP and Zend Engine to avoid issues related to outdated versions.
By the end of this guide, you will have understood the importance of PHP's transition to the BSD 3-Clause license and the advantages this transition offers to the open-source community.
To consolidate what you have learned, we invite you to put the following points into practice:
- Consult the official PHP documentation for further details on the new license.
- Participate in PHP community discussions to contribute to the continuous improvement of the project.
This transition simplifies compliance for downstream projects and Linux distributions, making PHP more accessible and compatible with other open-source tools.
Editorial Note and Disclaimer
The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.
GoYou does not constitute a journalistic publication or an editorial product pursuant to Law No. 62/2001 and does not perform real-time information activities.
The GoYou project does not provide professional, technical, legal, or financial advice and disclaims all liability for the misuse of the information published.
In the Crypto sector, every investment involves risks: readers are invited to always inform themselves independently before making any decision.