Open source project leaders have faced heavy challenges over the last decade and a half. It seems every language community has had conflicts with its leadership: Python with the struggles of the Python 2 to 3 migration; Node.JS and the community's conflict with Joyent; Rust and their handling of trademarks and IP; Wordpress and their conflict with WPEngine; and of course Go and their conflict around dependency management (and error handling). Now we've added another: the recent conflict between Ruby Central and the community.
In this episode, Kris, Matt, and Steve discuss these conflicts and what they tell us about the way we've come to see leadership within open source projects, where the blame actually lies, and what changes we can make to avoid these issues in the future.
We continue this discussion in this week's episode of Break! We get into some of the topics briefly mentioned during the main episode. Watch it on YouTube or listen with your favorite podcasting app! Learn more by going to https://break.show.
For our supporters, we have extra chapters about the sustainability of the current model and where we should place blame for the current problems. Not a supporter yet? You can fix that by heading over to https://fallthrough.fm/subscribe where you'll get not only extra content but also higher quality audio. Sign up today!
Thanks for tuning in and happy listening!
Show Notes:
Table of Contents:
Hosts