Fr though, I’ve been asking myself this all day — what would I do if I were still working there? Probably be torn between resigning and trying to make things right. I think there is a potential outcome where everyone can come together and build back in a more transparent, community-led fashion. This doesn’t have to be a travesty for the ecosystem. Fundamentally I think *everyone* wants Ruby to continue to grow and thrive and be secure and get adopted by more companies and have more diverse funding sources. There has to be a path where this can end up being a good outcome. For RC, why *not* use this as a moment to step back and say, okay, whatever actually happened, whatever our intentions, we’ve gone off the rails (lol) — community trust is lost, we’re not operating in a way that is in line with open source values… This is a wake up call. Let’s own this. Then open things up. Bring sponsors to the table. Bring community members to the table. Bring maintainers to the table (if they’re willing to join) and discuss what next steps could look like if we collectively built the future the ecosystem needs and deserves. Find a path that builders could get behind and feel inspired by and that sponsors would be willing to put money behind. Let go of ego. Don’t be afraid to let go of old ideas and assumptions and approaches. And then become the force that pushes it forward. Maybe RC needed a reckoning to get back on the right path and be what the ecosystem actually needs it to be. Because it was floundering for a while. People would constantly come up to me and ask me “what is Ruby central even” “what are you guys even doing” etc etc. For anyone paying attention, the community seemed to have lost confidence in Ruby central a while ago or just moved on — people would also tell me they stopped coming to our conferences, didn’t think we were relevant anymore, etc. So whatever the details behind what happened in this instance, RC was just not in a good place. Period. And it was clearly operating from a place of fear and scarcity for some time. And a course correction was absolutely necessary. I think one problem was they were desperately trying to over-correct in certain areas. Things were messy with compliance and operations and to fix it they went WAY too corporate and lost the authenticity and transparency that is necessary for leading an open source project. It’s an organization that clearly lost its soul and lost its way and became massively disconnected from maintainers and the community it exists to serve. And maybe changes to the team or board are necessary. Idk. But most of all they need a new vision. They need to be inspiring again. Because if they can’t inspire and help lead the ecosystem, what’s the point? Now *I* have gone off the rails with this stream of consciousness I did not intend to be writing at midnight (especially after I fully promised myself I would stay out of this discourse! 🫠) Idk maybe I’m naive or overly optimistic but I feel like we need SOME optimism here.