📝 Document history of why this exists #5
Merged
+40
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull request overview
This PR adds a "Why?" section to the README documenting historical context around controversies in the Ruby community related to RubyGems organization governance in 2025. The content is placed in a collapsible details section.
Changes:
- Adds a new "Why?" section with historical background about RubyGems governance disputes
- Includes multiple reference links to external sources documenting these events
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | 📍 NOTE | | ||
| |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | RubyGems (the [GitHub org][rubygems-org], not the website) [suffered][draper-security] a [hostile takeover][ellen-takeover] in September 2025. | | ||
| | Ultimately [4 maintainers][simi-removed] were [hard removed][martin-removed] and an reason has been given for only 1 of those, while 2 others resigned in protest. | |
There was a problem hiding this comment.
The text contains a grammatical error. The phrase "an reason has been given" should be "a reason has been given" - the article should be "a" not "an" before a word starting with a consonant sound.
Suggested change
| | Ultimately [4 maintainers][simi-removed] were [hard removed][martin-removed] and an reason has been given for only 1 of those, while 2 others resigned in protest. | | |
| | Ultimately [4 maintainers][simi-removed] were [hard removed][martin-removed] and a reason has been given for only 1 of those, while 2 others resigned in protest. | |
| | RubyGems (the [GitHub org][rubygems-org], not the website) [suffered][draper-security] a [hostile takeover][ellen-takeover] in September 2025. | | ||
| | Ultimately [4 maintainers][simi-removed] were [hard removed][martin-removed] and an reason has been given for only 1 of those, while 2 others resigned in protest. | | ||
| | It is a [complicated story][draper-takeover] which is difficult to [parse quickly][draper-lies]. | | ||
| | Simply put - there was active policy for adding or removing maintainers/owners of [rubygems][rubygems-maint-policy] and [bundler][bundler-maint-policy], and those [policies were not followed][policy-fail]. | |
There was a problem hiding this comment.
The text contains a grammatical error. The phrase "there was active policy" should be "there was an active policy" or "there were active policies" to be grammatically correct.
Suggested change
| | Simply put - there was active policy for adding or removing maintainers/owners of [rubygems][rubygems-maint-policy] and [bundler][bundler-maint-policy], and those [policies were not followed][policy-fail]. | | |
| | Simply put - there was an active policy for adding or removing maintainers/owners of [rubygems][rubygems-maint-policy] and [bundler][bundler-maint-policy], and those [policies were not followed][policy-fail]. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.