Re: Updating the PHP license

> On May 21, 2024, at 11:49, Richard Laager <[email protected]> wrote:
> 
> On 2024-05-19 14:53, Ben Ramsey wrote:
>> One of my goals with the RFC is to get rid of the idea of a “PHP License,” so it deprecates the PHP License and *replaces* it with the BSD 3-Clause License. I don’t want there to be a “PHP License, version 4.0.” I think that will continue to cause confusion in the community.
> 
> You (the copyright holders) could do both. That is, the PHP 4.0 license would be the same wording (other than the name) as BSD 3-Clause. That way, you trigger the "any subsequent version" clause, but then you also subsequently relicense PHP itself under BSD 3-Clause directly. This would indicate a clear intention that the PHP License is deprecated, while still getting the "any subsequent version" benefits for existing software.
> 
> Of course, this assumes that you WANT to trigger that option for third-party projects, which you may or may not. (I think you should want that, but it's not my code, so my opinion doesn't really matter.)


Honestly, I hadn’t considered this option before mailing this list, so I’m glad I mailed this list. :-)

After thinking it over, I do think we want to trigger this option for third-party projects, so that they have a clear path to upgrade the BSD 3-Clause license.

Cheers,
Ben

-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCZk1DRAAKCRCwLZeYnIwH
G5KPAP9Zf/isppoyO+OH6U1xRJTb7oxnSeIdzqSrnKdCHUdrnQD/bQjcfKM7FLun
5ulmDrxsasWUwDWSfy/balr7GNOkUVY=
=prcR
-----END PGP SIGNATURE-----