Re: [RFC] Updating the PHP License
| From: | Ben Ramsey | Date: | Fri, 27 Feb 2026 22:29:13 +0000 |
| Subject: | Re: [RFC] Updating the PHP License | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-130202@lists.php.net to get a copy of this message | ||
On 2/27/26 06:20, Tim Düsterhus wrote:
Attachment: [application/pgp-signature] OpenPGP digital signature OpenPGP_signature.asc
Hi Am 2026-02-27 05:47, schrieb Ben Ramsey:I planned to add the PDFs to the website, similar to how we keep an artifact of the original Zend Grant there: https://www.php.net/license/ZendGrant/index.php If you think the policies repo is a better place for these artifacts, then we can put them there instead. Cheers, BenThe 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.pdfThank 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 alicense.rstwith 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
Attachment: [application/pgp-signature] OpenPGP digital signature OpenPGP_signature.asc