RE: https://fosstodon.org/@php/117642403343089560
This is also the first generally available #PHP release under the 3-clause BSD license, which sadly didn’t get a mention on the “what’s new in PHP 8.6” page or in the changelog.
RE: https://fosstodon.org/@php/117642403343089560
This is also the first generally available #PHP release under the 3-clause BSD license, which sadly didn’t get a mention on the “what’s new in PHP 8.6” page or in the changelog.
Just to be clear, I’m not salty or upset about this. Licensing isn’t glamorous or exciting, and most people don’t need to or shouldn’t need to care about it. That’s sort of the point.
@ramsey Thank you for your efforts on this.
@ramsey Thank you for your work with this. I feel like it's flying beneath most radars.
@ramsey But it still is important. So thank you!
@ramsey i was surprised that choice didn't get reversed. seen a lot of projects switch to gpl just to "fight ai"
@bobmagicii There’s no way to switch a project of this size with this many contributors to GPL.
@bobmagicii worth a read: https://ben.ramsey.dev/blog/2026/05/the-php-license-simplified
You don't simply pick a license of your choosing when relicensing software, you have a lot of legal compliance that have to agree on that pick.
@bobmagicii @wouterj So was the PHP license. There’s no real change in the permissions granted.
@ramsey @wouterj the old php licence had that cause about how you can't use "php" in your product name. its a shame we can no longer debate if phpbb should be forced to rename because of different opinions on if the wording meant a fork of php can't use "php" in the name or a thing written in php. we had many fun times enforcing nothing! bsd-3c c-3 only vaguely makes it more clear lol.
@bobmagicii @wouterj That clause only prevented you from naming your project “PHP whatever” if it was based on the PHP source code. HipHop for PHP is one example; they called it “Hyper PHP” (i.e., HPHP) inside Facebook before releasing it, but they changed the name for the license. FrankenPHP and NativePHP arguably shouldn’t have used PHP in their names, according to the old license, but the issue is moot now.
@ramsey @wouterj depends how loose the digestion of "to endorse or promote derived products" is today in the third clause of bsd. if i was bored enough i could argue FrankenPHP is using the name of PHP in an attempt to gain search traction through implied associative endorsement.
but i myself am just an unlicenced .php file don't actually really care.
@bobmagicii @wouterj The BSD specifically says you can’t use the names of the copyright holders or contributors to endorse derivatives. This clause is largely assumed unnecessary, since most jurisdictions also have laws to protect against this anyway.
@ramsey thank YOU!
@ramsey No change in NEWS/UPGRADING about this topic. This makes it easy to forget about for the folks that worked on the release page.
If you had mentioned it during the preparation of the page, I'm sure it would've been included.
@timwolla Like I said, I’m not upset. I’ve been too busy, so I wasn’t involved in preparation of the page, and I don’t feel comfortable adding my own work to the NEWS file, so that’s on me.