Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128041
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: [PHP-DEV] [RFC] Updating the PHP License
Date: Mon, 14 Jul 2025 12:41:42 -0500
References: <70DC3FB4-C98E-4C79-AB2C-F2B65AE8B9F1@php.net>
 <f9aed61d-9f76-7a4b-f995-f55cef50e091@php.net>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <f9aed61d-9f76-7a4b-f995-f55cef50e091@php.net>
Message-ID: <0380F6C9-1462-4ECF-A5B9-21A4693CAF57@php.net>
From: ramsey@php.net (Ben Ramsey)

> On Jul 14, 2025, at 08:13, Derick Rethans <derick@php.net> wrote:
>=20
> On Wed, 9 Jul 2025, Ben Ramsey wrote:
>=20
>> The RFC is available at: https://wiki.php.net/rfc/php_license_update
>>=20
>> Discussion will remain open for at least six months to ensure all=20
>> interested parties have an opportunity to respond.
>=20
> Thanks for tackling this. Licensing issues can be thorny.
>=20
> I only really have one comment =E2=80=94 why wait until (specifically) =
PHP 9,=20
> and not PHP-next (the one after 8.5)?
>=20
> cheers,
> Derick


I don=E2=80=99t think there are any technical or legal reasons for this. =
When I began discussing this with others a few years ago, the next major =
version (PHP 9) seemed like the right time to make a major licensing =
change.

If others think PHP-next (i.e., either 8.6 or 9.0, whichever comes =
first) is the right version for this change, then I=E2=80=99m okay with =
that.

Cheers,
Ben