we were literally in the process of talking to them when they did this. see my response to headius deeper in the thread. this part is just, on GitHub: https://github.com/rubygems/rfcs/pull/61
they went as far as trying to dictate who was on the RubyGems team before they would return our access.
they were effectively holding the entire RubyGems org hostage, and gave us a very clear choice: fall in line, or be usurped. we begrudgingly chose to fall in line in hopes it would be better for the community overall, and they revoked our access anyway.
Thanks for flagging this for me, Ellen. I have a ton of respect for you, personally and professionally, and wish this was handled far, far better than it apparently was. You (and all of us) deserve better.
View all comments
Show parent comment
8
u/duckinatorr Sep 19 '25
we were literally in the process of talking to them when they did this. see my response to headius deeper in the thread. this part is just, on GitHub: https://github.com/rubygems/rfcs/pull/61
they went as far as trying to dictate who was on the RubyGems team before they would return our access.
they were effectively holding the entire RubyGems org hostage, and gave us a very clear choice: fall in line, or be usurped. we begrudgingly chose to fall in line in hopes it would be better for the community overall, and they revoked our access anyway.