Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130186
Precedence: list
MIME-Version: 1.0
Date: Fri, 27 Feb 2026 13:20:32 +0100
To: Ben Ramsey <ramsey@php.net>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Updating the PHP License
In-Reply-To: <20260227044731.8AAC61A00BD@lists.php.net>
References: <70DC3FB4-C98E-4C79-AB2C-F2B65AE8B9F1@php.net>
 <20260227044731.8AAC61A00BD@lists.php.net>
Message-ID: <932849a166a6b7aab853cc895a95e37c@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2026-02-27 05:47, schrieb Ben Ramsey:
> The important thing in this message is the link to the Zend consent 
> letter:
> 
> https://static.ben.ramsey.dev/php/rfc/license-update/zend-technologies-php-license-consent.pdf

Thank you, this is great news.

As for the two consent letters: Would it make sense to push the two PDFs 
(Perforce and PHP Group) to the policies repository at 
https://github.com/php/policies/ to make them permanently available to 
the PHP project (i.e. independent of your personal web host)? The 
policies repository is probably the most appropriate location to store 
them. Possibly in a “license” subdirectory that also contains a 
`license.rst` with instructions on how to correctly apply the license to 
newly created files (i.e. the “New X Source File Header” snippets from 
the RFC).

Best regards
Tim Düsterhus