On Thu, 5 Sep 2019 at 14:29, Brent <bre...@stitcher.io> wrote: > > I believe GitHub is the way to go. Several large communities manage their OSS > on it and have proven it works, PHP should simply do the same.
At the risk of giving advice, you will find conversations are far more productive if you ask why something can't be done, rather than just stating it will be simple. Not only will that elicit more useful information to you, it avoids being subtly insulting, as you're implying that something will be easy and people are being stupid for not doing it*. In this particular case you could have asked "what would be the problems with moving the build systems to github?", and the answers would include: * PHP has karma (aka permissions) system which github could not support. I don't know how that could be solved/avoided. * There is very strong reluctance to be dependent on other people's infrastructure for things that could take a long time to migrate. e.g. we can move discussions from one medium to another, by just telling people to go talk over there. But for actual software CI, it's a big deal to move from one system to another. btw it's not obvious that the projects you linked actually have their build systems integrated with Github. I'm pretty sure you're making assumptions about how simple their systems are. cheers Dan Ack * in pithier form: https://signalvnoise.com/posts/439-four-letter-words -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
