Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129471 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id EA1421A00BC for ; Fri, 28 Nov 2025 21:38:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1764365906; bh=jOuR/umUvqDZ2mm9gA64YmyfeEFgW4eoE3XzHEFLw/M=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=RFaNDmNypbVat3cUecyvdvnd0ifAg+AfkxJaFwDDlgeHG4JHwwMgm5BDpgVvUu9E5 Xcbs8MkVP98GSPPMDuSXEgWcbaUYCEzohFTHZsVf8XVECOYwDz/QhEGH8Ds/kaCUIh IjTCsQmTGG6SKeVX649s3jmzjRHVYzmyheSMMNRWTbWvCsbegwTOMMmvBwSGqG2bD6 chg6qOMqH0FGhV6La73NaS+i2g9vPBQdHFLYCoZuzeqVvqL+VsENYuCZisvjDpNl00 SIcstVoS9anJgAN2TRRAdyLDiiNs/O9Pm87a8Yq8C4LqsrlGb7w+rvo+ASBKTpe5C8 QjQzkQefOVd1A== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B523D180077 for ; Fri, 28 Nov 2025 21:38:24 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=BAYES_50,DMARC_NONE, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 28 Nov 2025 21:38:24 +0000 (UTC) Received: by mail-ot1-f44.google.com with SMTP id 46e09a7af769-7c75fc222c3so763289a34.0 for ; Fri, 28 Nov 2025 13:38:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764365898; x=1764970698; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=sbf3zyaPDF3QTG90kZr8Hoe+T9xhxiT56PzWTSNCk70=; b=FZihdBWg7fwEhqQvkXTPfL+ihr14YEx/u2SEtIDDSlSdKyiXV2GHw9M4rHChtXuje3 PXPhvoMqzBVMXtGjvdz8xauF923F2i58U9DWwd+qF1qolIW4aCDsNiqt/5DWFgLn604V cixQITdzaoBsKlM349pepnEEEbnEFtnnVBfNMjTwKhk8pcbGn2cQwOYjsgNaPXtpNO6O A++fspz624kUUvdqnrQoORiH5EvarmoYn/Q/sWq67v5HSao6qsoWvPAIukKgV6CI9bMk cJeUrQVNKq5VKOz4Fypt6THIWxOtMyXcXQiO68EOhssMpbrabq3tpT85+e4jfRtzxarL mt/A== X-Gm-Message-State: AOJu0YyadC0tye8YYZJiutVyrvsS64ugbsjknj7I8uAXzB18K+eISQ0e /x0LSAm1Dk+bJ+de3TSyYHP80nqwzPj1ApMcRIf9Fd8RtpvglEx7as62d1X4TxSH02jcBxiKq7A 9IJ0am3Y7o3IxQuPh0nO0gJsdfmx5Bo7RWIoX X-Gm-Gg: ASbGncvRTg69gsp3NRtF1HAWfiRsldwH1AJ0awYCMaeACX90XKjzlrFaaEPh5FA2Oml j9DfzhBtw3y1f6d0rr+bUkGQXHQ/3jMizp5MGCjwIaJEu+EDwKELD47yhVtc51sTqekdtIDt3Bg pOSg8zAhHoLhqVknABrekLt0HdApzZMduMaF0IRRayFY5V2oaaHT9G+uw5Zmckb6cv/biDGxNCe aPBSdKT4XqUiKqhMveKMaJbI9YW8WyQfwzdp7Zx2x3/zwgJJlgSUdb4EOEp41PJHX1zq2s= X-Google-Smtp-Source: AGHT+IHK4qzUZdhl1LlD1RSdu845jnNyvL95nYoZExmEtDMZHPLfow/xgXhCe9/0yDD7PLM9n3HYpOzTFwyk4uhU9Jo= X-Received: by 2002:a05:6808:4fd1:b0:442:e596:1189 with SMTP id 5614622812f47-45115ade50fmr10910699b6e.45.1764365898543; Fri, 28 Nov 2025 13:38:18 -0800 (PST) Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 References: <70DC3FB4-C98E-4C79-AB2C-F2B65AE8B9F1@php.net> <20251128202403.65F631A00BD@lists.php.net> In-Reply-To: <20251128202403.65F631A00BD@lists.php.net> Date: Fri, 28 Nov 2025 22:38:07 +0100 X-Gm-Features: AWmQ_bmz5LO_UX5sgWsvtJGyi0jwF-59DUaD46q-Vpm4rDgPiEqa0L0j6D0S-f0 Message-ID: Subject: Re: [PHP-DEV] [RFC] Updating the PHP License To: Ben Ramsey Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="000000000000a2f4540644ae72dd" From: bukka@php.net (Jakub Zelenka) --000000000000a2f4540644ae72dd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Fri, Nov 28, 2025 at 9:26=E2=80=AFPM Ben Ramsey wrote: > On 7/9/25 22:22, Ben Ramsey wrote: > > Hello internals, > > > > I=E2=80=99m opening discussion on an RFC proposing that we relicense PH= P under > > the Modified BSD License (SPDX identifier: BSD-3-Clause), starting with > > PHP 9.0. This change simplifies and modernizes our licensing, > > addressing long-standing issues while preserving the rights of both > > contributors and users. Below is a quick summary of what the RFC > > proposes and what it means for developers. > > > > - Proposes that PHP 9.0 adopt the Modified BSD License (BSD-3-Clause), > > replacing the current PHP and Zend Engine licenses. > > - The Modified BSD License is OSI-approved, GPL-compatible, and widely > > recognized in the open source community. > > - Your rights as a developer=E2=80=94use, modification, distribution=E2= =80=94remain > > unchanged. > > - Extensions and tools may adopt BSD-3-Clause in place of the outdated > > PHP License. > > - The update removes confusing legacy clauses tied to branding and > > permissions. > > I read it through and it's really nice! +1 on this. I already started using BSD License for some of the new stream changes - we are not required to use PHP license and other licenses are already contained in it - mainly BSD (e.g. FPM) and Apache. FPM is actually 2-Clause BSD: https://github.com/php/php-src/blob/php-8.5.0/sapi/fpm/LICENSE . It might make sense to cover it in the RFC and update it to 3-Clause as well maybe? Also we should add headers with SPDX tag to its files where it's missing completely - see https://github.com/php/php-src/blob/php-8.5.0/sapi/fpm/fpm/fpm.c#L1 for example. Assuming that it's fine to change it because the project is under that license..? > > > I=E2=80=99ve spoken with all members of the PHP Group, and each has voi= ced their > > approval of this proposal. The Perforce legal team has also informally > > approved, and I will be working with them to get a formal letter of > > approval soon. > > It would be good to get this stored somewhere so we have got proof of it. It can be done privately but the point is that more people would have access in case it is ever needed and you are not available. It could be slightly clearer in the RFC that you have already all approvals from PHP Group members - it just talks about how many of them might be needed and then list them as approved without saying that it is all covered= . I guess the vote can start without the formal approval from Perforce but the actual change should wait for it. > > The RFC is available at: https://wiki.php.net/rfc/php_license_update > > > > Discussion will remain open for at least six months to ensure all > > interested parties have an opportunity to respond. > > > > Cheers, > > Ben > > > > P.S. For legal questions or concerns, I=E2=80=99m working with Pamela C= hestek > > of Chestek Legal on behalf of the PHP > > Group. You may be familiar with her work as chair of the license > > committee for the Open Source Initiative. > > The only feedback I've received thus far regards the proposed PHP > version. After thinking on it a bit, I agree with changing the proposed > PHP version from 9.0 to the next version of PHP, whether that's 8.6 or > 9.0. I've updated the RFC to reflect this. > > You should just target just PHP 8.6 which is the automatic next version unless there is an RFC that would change it to 9.0. Kind regards, Jakub --000000000000a2f4540644ae72dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Fri, Nov 28, 2025 at 9:26= =E2=80=AFPM Ben Ramsey <ramsey@php.net= > wrote:
= On 7/9/25 22:22, Ben Ramsey wrote:
> Hello internals,
>
> I=E2=80=99m opening discussion on an RFC proposing that we relicense P= HP under
> the Modified BSD License (SPDX identifier: BSD-3-Clause), starting wit= h
> PHP 9.0. This change simplifies and modernizes our licensing,
> addressing long-standing issues while preserving the rights of both > contributors and users. Below is a quick summary of what the RFC
> proposes and what it means for developers.
>
> - Proposes that PHP 9.0 adopt the Modified BSD License (BSD-3-Clause),=
>=C2=A0 =C2=A0 replacing the current PHP and Zend Engine licenses.
> - The Modified BSD License is OSI-approved, GPL-compatible, and widely=
>=C2=A0 =C2=A0 recognized in the open source community.
> - Your rights as a developer=E2=80=94use, modification, distribution= =E2=80=94remain
>=C2=A0 =C2=A0 unchanged.
> - Extensions and tools may adopt BSD-3-Clause in place of the outdated=
>=C2=A0 =C2=A0 PHP License.
> - The update removes confusing legacy clauses tied to branding and
>=C2=A0 =C2=A0 permissions.
>

I read it through and it's really = nice!=C2=A0+1 on this. I already started using BSD License for some of the = new stream changes - we are not required to use PHP license and other licen= ses are already contained in it - mainly BSD (e.g. FPM) and Apache.

FPM is actually 2-Clause BSD: https://github.com/php/= php-src/blob/php-8.5.0/sapi/fpm/LICENSE . It might make sense to cover = it in the RFC and update it to 3-Clause as well maybe? Also we should add h= eaders with SPDX tag to its files where it's missing completely - see <= a href=3D"https://github.com/php/php-src/blob/php-8.5.0/sapi/fpm/fpm/fpm.c#= L1">https://github.com/php/php-src/blob/php-8.5.0/sapi/fpm/fpm/fpm.c#L1= for example. Assuming that it's fine to change it because the project = is under that license..?
=C2=A0

> I=E2=80=99ve spoken with all members of the PHP Group, and each has vo= iced their
> approval of this proposal. The Perforce legal team has also informally=
> approved, and I will be working with them to get a formal letter of > approval soon.
>

It would be good to get this stored so= mewhere so we have got proof of it. It can be done privately but the point = is that more people would have access in case it is ever needed and you are= not available.

It could be slightly clearer in th= e RFC that you have already all approvals from PHP Group members - it just = talks about how many of them might be needed and then list them as approved= without saying that it is all covered.

I guess th= e vote can start without the formal approval from Perforce but the actual c= hange should wait for it.


> The RFC is available at: https://wiki.php.net/rfc/ph= p_license_update
>
> Discussion will remain open for at least six months to ensure all
> interested parties have an opportunity to respond.
>
> Cheers,
> Ben
>
> P.S. For legal questions or concerns, I=E2=80=99m working with Pamela = Chestek
> of Chestek Legal <https://www.chesteklegal.com> on behalf= of the PHP
> Group. You may be familiar with her work as chair of the license
> committee for the Open Source Initiative.

The only feedback I've received thus far regards the proposed PHP
version. After thinking on it a bit, I agree with changing the proposed PHP version from 9.0 to the next version of PHP, whether that's 8.6 or =
9.0. I've updated the RFC to reflect this.


You should just target just PHP 8.6 wh= ich is the automatic next version unless there is an RFC that would change = it to 9.0.
=C2=A0
Kind regards,

Jakub
--000000000000a2f4540644ae72dd--