Daniel Ribeiro wrote on 24/10/2014 19:52:
*Disclaimer: *I wanted to bring this discussion inside the internals mailing list not only because of the fact that the PHP.net website's source code on GitHub doesn't have issues enabled, but especially because I think it's part of the PHP environment, just like the spec or the actual C code itself.
In case you hadn't seen it already, there's a list of all the mailing lists for PHP here: http://php.net/mailing-lists.php
In this case, I would have thought either php.webmaster or php.doc would be more appropriate than php.internals, which really does tend to focus on the internal implementation of the language, rather than how it used or documented.
Meanwhile, I agree with both Kris and Andrea's responses: you need to be specific about what problems you propose to fix, and you need to be extremely wary of breaking existing functionality just because it's "interesting" or "modern".
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
