Moves docs for extensions maintained outside php-src out of the PHP manual to a separate home run by the extension maintainers.
This poll has closed.
This poll has closed.
This poll has closed.
The main vote passed 26 to 1, with 1 abstaining, well above the two-thirds majority it needed. Voting closed on July 3, 2026.
Two secondary votes needed a simple majority:
www.php.net/manual/extensions/ won 15 to 8 over contrib.php.net, with 6 abstaining.The PHP manual documents the language itself, but it also documents a long list of extensions that live outside php-src, like imagick, redis, mongodb and memcached. This RFC from Jordi Kroon moves the documentation for those third-party extensions out of the main manual and into a separate home run by their maintainers.
Right now the PHP docs team maintains pages for code it doesn't own. That makes it hard to verify facts, and changes can sit in review for a long time. Some extension maintainers don't respond, and some have abandoned their extensions entirely. Keeping these pages in the official manual also suggests the extensions are part of PHP when they aren't.
The people who write an extension know it best, so the RFC hands its documentation to them.
ext/pdo, ext/curl and ext/mbstring, remain in the manual.mcrypt and ext/mysql.The migration is a straight copy. Pages move one to one with no rewrites, and the docs team handles the work one extension at a time.
Your code doesn't change. If you read the docs for a third-party extension, you'll find them at a new address. If you read them in a language other than English, that translation goes away. And if you want to fix those docs, you'll send changes to the new repository instead of the main manual.