Hi!
It might just be an illusion, but it feels like all three projects have a lot more resources to spend on all this than PHP does; Rust has "Working Groups", Kubernetes has "Special Interest Groups", and PHP struggles to assign each module a single maintainer. How that affects our tooling requirements, I'm not sure, but I suspect new contributor experience should be high on our priority list, either in terms of user interface or just documentation.
Great survey. I do not have much experience with others, but from my observations about Prow it's a software system of its own which needs its own configuration, setup, maintenance, and everything else that's involved in setting up and maintaining CI/CD system. Github provides a nice GUI for it but there's much more that is happening behind the scenes than the GUI. Prow itself is pretty nice to use, once you learn how to work with it, but we need to be aware that if we want something with Prow capabilities, we'd need somebody willing to support this system, so we're back to the same place we departed from.
-- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
