A board member's perspective of the RubyGems controversy

(apiguy.substack.com)

104 points Qwuke | 2 comments | 21 Sep 25 19:20 UTC | HN request time: 0.419s | source

Show context

baggy_trough ◴[22 Sep 25 17:22 UTC] No.45336634[source]▶

Locking out a guy like David Rodriguez (the main person I see doing bundler commits) in a dramatic fashion just seems like absolute craziness. I can't fathom doing it without a very good reason, which has yet to be revealed if it exists.

replies(2): >>45338423 #>>45344443 #

1. byroot ◴[23 Sep 25 08:47 UTC] No.45344443[source]▶

>>45336634 #

He's specifically among the 3 people still owner of the bundler gem [0], they were 6 just a few weeks ago [1]

[0] https://rubygems.org/gems/bundler

[1] https://web.archive.org/web/20250824033341/https://rubygems....

replies(1): >>45346027 #

2. baggy_trough ◴[23 Sep 25 12:24 UTC] No.45346027[source]▶

>>45344443 (TP) #

He said this on the Bundler discord yesterday:

'My work in Bundler & RubyGems is completely halted, including the Bundler 4 project which I expected to complete in the next ~2 months. The immediate reason for this is simple: my commit access to the repository has been revoked, so I can no longer do the job anymore. The more fundamental reason is that I completely lost motivation after all the recent events, regardless of whether work is paid or not.

I'll be happy to resume my work in Bundler & RubyGems if maintainer ownership prior to September, the 9th is restored, and thus the previous maintainer's team is allowed to continue building a transparent and democratic governance model for the project.'

↑