On Thu, 5 Sep 2019 at 12:27, Côme Chilliet <c...@opensides.be> wrote: > > PHP have no control over github, and cannot know how it will evolve. > > (they can change the platform tomorrow and internal won’t be able to do > anything about it). >
Those are hypothetically problems. But they do not appear to be currently problems. I'm pretty sure that if new problems with a medium were encountered, we could adapt to either work around them or move to a different system. And in case anyone says "some people might not be able to comment on Github" the same is true for our email lists. The signup process was apparently broken for ages, and I've seen multiple people ask for how to persuade the system to accept their messages. Which probably means there are more people who never contributed because they couldn't get past that first barrier. Actual problems I can see with having the discussion on github: i) There is no off-topic space. For example, apparently some people don't understand the RFC and could do with a brief explainer on type systems. Doing that inline to the github comments would make the on-topic discussion harder to read. ii) It means that the discussion is harder to track. However.....that is already a problem. When I was putting together the info for https://github.com/danack/RfcCodex which attempts to document why certain ideas that keep coming up haven't succeeded yet, it was a massive pain trying to track email threads to the RFC. Both of those things are not really technical problems. They are documentation problems. They would be best solved (imo) by having a paid member of staff on the PHP project writing lots of words. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
