|7eter l-|. l3oling 🧰
Many questions about the new Gem Coop (replacement of rubygems.org) are answered by @martinemde here:https://martinemde.com/2025/10/05/announcing-gem-coop.html
#Ruby #RubyGem
| GitHub | https://github.com/martinemde |
martinemde
- 59 Followers
- 17 Following
- 29 Posts
Many questions about the new Gem Coop (replacement of rubygems.org) are answered by @martinemde here:https://martinemde.com/2025/10/05/announcing-gem-coop.html
#Ruby #RubyGem
@lucian i appreciate your level headed approach in Short Ruby to a messy situation.
> first, reflect on your own perspective; second, consider all parties involved and their motivations; third, focus on identifying agreed facts and disputed details; finally, review all information with this context in mind to better understand the situation, even as it remains uncertain.
Thank you for being a part of this community.
@drbrain this is really kind and you express succinctly what it is that I like about André. Not everyone agreed with him, it wasn’t always smooth, and yet we now recognize that paying maintainers to contribute to open source is a cornerstone of maintaining secure open source projects.
At the time this upset people and it took time to get the messaging clear and unambiguous, but the intention was positive through and through. Thank you.
drbrainI think Andre saw a community in Ruby that he wanted to contribute to beyond just software. He brought his passion for Ruby to RubyGems and Bundler and more than helped continue their success.
He recognized that the way open source software was developed and maintained, typically through volunteer time, was not sustainable and left it vulnerable. Then he put a framework in place to help it be sustainably maintained.
I know Andre led a lot of other work, but RubyTogether may have been his best
I merged the policy on restricting committer access to RubyGems after a fruitful discussion with other committers. At that time we wanted to prevent things that we now call supply chain attacks.
I would categorize this specific PR as Andre bringing maturity of process to RubyGems.
Andre created the framework for me to make an orderly departure from RubyGems maintainership and I think we all can’t thank him enough for that
https://mastodon.social/@searls/115282174363254250
@mischif @segiddins That's understandably confusing, but that post is old. A lot has changed in 2 weeks.
Most of the maintainers feel a sense of responsibility to the Ruby community, and would suffer a lot of unpaid work on nights and weekends. One of the painful things about OSS is how your sense of responsibility can be co-opted by others to take advantage of volunteer and underpaid contributors. We often stick around for free because the alternative, failing everyone, seems unthinkable.
@segiddins wait, again? I remember something like this happening last year.
Samuel GiddinsNothing says "we will ignore everything that is said in a Q&A" like scheduling it over Rosh Hashanah.
Aaron Hhttps://github.com/rubygems/rfcs/pull/61 -- This was @martinemde 's proposal for a governance model in #rubygems
Proposal for RubyGems Organizational Governance by martinemde · Pull Request #61 · rubygems/rfcs
As an organization that has long held its governance in trust by the maintainers of the project, I propose that we establish a transparent public governance plan. It would be beneficial for everyon...
@segiddins @mischif I did a lot of free work previously, Samuel did orders of magnitude more (hat tip). What I’m saying by leaving rubygems is that I will not contribute to the projects any more (barring some miracle of oss governance). Neither paid nor free.