On 18/06/2026 7:42 am, Nick Sdot wrote:
I think co-locating would add a lot of value, while still achieving the
goal you propose.
Admittedly, this approach would require slightly more coordination than
your proposal. It, however, would also serve as a great first filter to
evaluate which extensions are still maintained, hence worth documenting
(promoting), and which not. The initial move could be automated with PRs
to the extension repos. I'd argue the extra effort is negligible and the
upsides outweigh it.
Thoughts?
--
Cheers
Nick
I am not against this proposal. I would even encourage extension
maintainers to host their own docs. However given we have historically
offered a space for third-party extension maintainers to host their
docs, it would practically be impossible to get all (or some)
maintainers on board. Both not from a moral and a practical perspective.
At first we would have to contact each and every extension maintainer to
see if they have interest in moving the docs to their own space. Given
not all extension maintainers reply, or are interested; we can't just
abandon the extension for reasons I have described in my previous reply
to Kamil. In short, a lack of recent updates does not necessarily
mean an extension is no longer functional with current PHP versions.
If however we can get it in practice for /some/ extensions we could use
Git submodules (or something similar) to pull third-party extensions
into the PHP managed monorepo.
So very practically speaking, this would still require this RFC to pass
as it allows us to lift and shift extensions to a doc-contrib
repository. Which then if an extension maintainers decides, "I want to
host my own docs", they are free to do so while we can look for ways to
pull them into the doc-contrib repo.
--
Regards,
Jordi Kroon
