Josef Šimánek
@retro-rubies.bsky.social
I have plan to automate this actually and run it like bi-monthly for top 200 (maybe extend the scope later) RubyGems.org gems by monthly downloads, excluding Rails, Ruby Core, AWS, Google and other huge/stable vendors (they have own processes on this). 🙏🤖📦✅
October 20, 2025 at 10:59 AM
I have plan to automate this actually and run it like bi-monthly for top 200 (maybe extend the scope later) RubyGems.org gems by monthly downloads, excluding Rails, Ruby Core, AWS, Google and other huge/stable vendors (they have own processes on this). 🙏🤖📦✅
> "Owner as the Ruby Central board member who represents the board on the open source committee"
Which means exactly no mandate to change any ownership in RubyGems GitHub organization. That's nothing to justify RC amoral act of using pure evil force to achieve that.
Which means exactly no mandate to change any ownership in RubyGems GitHub organization. That's nothing to justify RC amoral act of using pure evil force to achieve that.
September 28, 2025 at 7:10 PM
> "Owner as the Ruby Central board member who represents the board on the open source committee"
Which means exactly no mandate to change any ownership in RubyGems GitHub organization. That's nothing to justify RC amoral act of using pure evil force to achieve that.
Which means exactly no mandate to change any ownership in RubyGems GitHub organization. That's nothing to justify RC amoral act of using pure evil force to achieve that.
And even that all is true (which is not), you or anyone from RC had no mandate to remove any maintainer's access to RubyGems/Bundler or RubyGems.org codebases on GitHub in RubyGems organization.
September 28, 2025 at 7:04 PM
And even that all is true (which is not), you or anyone from RC had no mandate to remove any maintainer's access to RubyGems/Bundler or RubyGems.org codebases on GitHub in RubyGems organization.