zlacker

>>jolux+(OP)
There is some more context on a post[1] in /r/ruby, including the fact that the maintainers and others had been working on a proposal[2] for a formalized organizational governance structure as recently as yesterday. The latter also adds some context into Mike McQuaid's involvement: the proposal was influenced by the structure put in place by the Homebrew project.

[1]: https://old.reddit.com/r/ruby/comments/1nkzszc/ruby_centrals...

[2]: https://github.com/rubygems/rfcs/pull/61

>>ilikep+x31
I'm trying to help, where I can, to mediate. On a call right now about this. Had 4 in the last 24 hours with affected parties past and present on both sides.

I'm not involved beyond just caring a lot about Ruby.

>>mikemc+qd1
Posted an update in a thread (or whatever you're meant to call it) on Bluesky: https://bsky.app/profile/mikemcquaid.com/post/3lz7klsyue22f

TL;DR: I've been given a lot of private nuance from both sides here but, even just based how the two sides have treated me personally, it's very hard not to put the blame primarily on RubyCentral. I've been a maintainer on Homebrew for 16 years: it's a hard job. If in doubt: I'll side with maintainers.

>>mikemc+zz1
Sure, but it's two different things. Maintainers are in charge of their projects, and Ruby Central is in charge of the package index. Each has different priorities, which is fine. If they can't find a way to live with each other, maybe a parting of the ways is required.

>>yawara+vK2
Parting of ways? Sure. In this case they are in charge of the package index but have removed most maintainers from their projects, implicitly taking charge there too. This is a problem.

>>mikemc+D43
How can they remove maintainers from their own projects? If my project is yawaramin/foobar, how can Ruby Central remove me as the mantainer from there?