On Wed, Oct 2, 2024, at 12:17 PM, Deleu wrote: > It's 2024. If the foundation is hiring developers to improve the language > across the board (internals, docs, website, processes, marketing, visibility, > etc),
As Jim has already stated, the Foundation is not hiring developers for any of the categories you mentioned other than internals, and build chains tools. Maybe it should, but as far as I am aware, the choice not to is due to lack of sufficient funding. Moreover, hiring for documentation is tricky, as one must be able to cross-reference the source code to verify the behaviour, on top of having technical writing skills, and working with our tooling. > it makes no sense that these folks (or any volunteer for that matter) be > explicitly and unquestionably denied the opportunity or conversation to > modernize the system which PHP tooling is built upon. The only contention I have encountered with modernizing tooling has been about the use of Composer or PHPUnit for PhD. Which would be resolved by this RFC. As Andreas pointed out, the php.net websites are mostly static, and I don't see how a full-fledged framework would help us. Especially as we have decommissioned some of the more clunky websites like bugsnet or gcov. *Maybe* a micro-framework to handle php.net accounts and Documentation notes handling makes some sense. As always in these sorts of discussions, people make out that the reason *they* do not contribute to a php.net related project is because of "XYZ". Where XYZ can be anything. And yet, we consistently get new contributors that get up to speed and help to modernize different codebases in the matter of weeks without issues, and more importantly, *without* wanting to rewrite everything from scratch in their favourite thing that many of us have no idea how to use. Best regards, Gina P. Banyard
