|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.
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
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...
This renders good, well formed markdown (unlike most ERb generated markdown:
```md
# MDPhlex
- [Docs](https://github.com/martinemde/mdphlex/blob/main/README.md)
- [RubyGem](https://rubygems.org/gems/mdphlex)
- [Source](https://github.com/martinemde/mdphlex)
```
Check it out. https://github.com/martinemde/mdphlex
When I made MDPhlex I didn’t realize Rails 8.1 was adding native `to_markdown` convention.
Make organized Markdown (like /llms.txt) generation easy with MDPhlex and Phlex components.
🛎️ Bright Sunny `STUDIO` 🌞 – $0/mo
Turn any CLI command into a one-room MCP server. Clean, compact. Move-in ready.
`gem install studio`
🔗 https://github.com/martinemde/studio
Turn any CLI command into a one-room MCP server. Clean, compact. Move-in ready.
`gem install studio`
🔗 https://github.com/martinemde/studio
`params.expect` is not a silver bullet for the JSON juggling attack proposed in this article, but taking close look at whether you expect an array or a hash in your params is a good start to avoiding this vulnerability. https://nastystereo.com/security/rails-_json-juggling-attack.html