@chris@skc@ramsey Since I came back from the Rubyverse to WordPress, I have had the hunch that the WordPress project itself, its monolithic structure and its multiple appendices is deliberately designed to prevent a successful fork from ever seeing the light of day.
@alpha1beta@chris@ramsey@skc Most forks of #WordPress start out strong but fade away over time either because @WordPress rolls their best features into the core (I think this happened with WordPress MU) or lack of support & interest from the community overall.
@alda@chris@ramsey I know someone you can reach out to about this if your company says you can’t work on core stuff. They will cover your salary if you get in trouble for talking to them. /s
@chris@skc@ramsey And I must ask, where is the joy or reward in contributing to this codebase?
Many of us need to argue for contributing to open source being a part of our nine-to-five. Even during my time at Automattic, fixing blocking bugs in the WP core was considered extracurricular or "not a good use of your time".