Re: [RFC] Separation of Third-Party Extension Documentation
| From: | Larry Garfield | Date: | Fri, 29 May 2026 16:10:08 +0000 |
| Subject: | Re: [RFC] Separation of Third-Party Extension Documentation | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131061@lists.php.net to get a copy of this message | ||
On Thu, May 28, 2026, at 2:15 PM, Jordi Kroon wrote:
> Hello,
>
> I've opened an RFC to separate third-party extension documentation
> (imagick, redis, mongodb, etc) from the official PHP manual, while
> keeping the existing DocBook tooling and infrastructure.
>
> Bundled extensions (pdo, curl, etc) are out of scope and stay in the
> official PHP manual.
>
> https://wiki.php.net/rfc/third_party_ext_documentation
>
> --
> Regards,
>
> Jordi Kroon
I support this. Having first-party extensions and seemingly abandoned third party extensions in the
same list has always struck me as very misleading. Just the benefit for documentation readers alone
makes it worth it, IMO.
Question: What about comments on any of the to-be-moved pages? My vote would be to just nuke them
from orbit in the process, as manual comments have about a 1% "usefulness" rate. In fact
I'd be completely on board with not enabling comments on the contrib-docs built at all and
making it strictly readonly, with links to GitHub if someone is in a contributing mood.
--Larry Garfield