All of the infrastructure used by Ruby developers today, including Bundler, RubyGems, and RubyGems.org has been maintained and developed for many years entirely by volunteers. While it’s good that no one company controls resources shared by the community, it’s terrible that the only people who work on our shared infrastructure are doing so for free, in their spare time.
Note: Here’s another guest post from André Arko, who leads the Bundler core team and builds web applications for clients at Cloud City Development in San Francisco.
Note: Our good friend André Arko, who also happens to be one of the maintainers of Bundler wrote this great post for us about the state of Rubygems. He is currently working with a grant from Ruby Central to make Rubygems awesome. Yay for community posts, and thanks André!
Bundler, Rubygems, and rubygems.org are vital infrastructure that every Rubyist uses just about every day. Over the last year, that infrastructure has seen a huge amount of change. This is a review of those changes, an update on where things are now, and an explanation of where we’re going soon.
Note: Friend of Engine Yard André Arko, a member of Bundler core, wrote this insightful piece for us about little-known tricks in Bundler. Check out his own site here.
This post comes from guest community contributor and Engine Yard alumni Andre Arko. Andre has been building web applications with Ruby and Rails for five years, and is a member of the Bundler core team. He works for Plex, tweets as @indirect, and blogs at andre.arko.net.
Managing software packages on Unix has always been, to put it politely, a giant pain, and most Linux distributions are built around the different ways we’ve all been trying to alleviate that pain. In this post, I’ll walk you through Homebrew, a fantastic new option for package management made simple.
