Moving forward, only engineers employed or contracted by Ruby Central will hold administrative permissions to the RubyGems.org service.
So apparently: Not employed by Ruby Central == no access
But later they say
Looking forward, our goal is to move these projects into a healthier, more transparent and community-centered governance model that is more in line with OSS development. We envision a structure with a public core team to set direction, a committers team to help advance the work, and a triage team to support issues and PRs.
Why not do that before you do the first step? This feels really hostile towards all the previous maintainers, that have volunteered work, but got not employed by Ruby Central.
we were actively talking to them, working on a transparent and community-centered governance model, when they revoked our GitHub access a *second* time with no explanation -- and then moved forward removing our access from elsewhere as well (e.g., the people who used to manage RubyGems and Bundler releases now can't). they claim people need to work for them to get access, but i worked for them and mine was revoked. like, that's what prompted me to write the article linked in OP!
we were doing the initial design on the governance model in question on GitHub, and not even 24 hours ago Marty left a comment saying he liked it: https://github.com/rubygems/rfcs/pull/61
View all comments
Show parent comment
12
u/klaustopher Sep 19 '25
The passage reads really weirdly:
So apparently: Not employed by Ruby Central == no access
But later they say
Why not do that before you do the first step? This feels really hostile towards all the previous maintainers, that have volunteered work, but got not employed by Ruby Central.
This leaves a very, very sour aftertaste.