Take a look at where we're headed.
Today, Ruby Together is committed to improving the three most widely-used core Ruby tools:
- Bundler, the Ruby dependency manager, used by every Ruby project to manage and install gems
- RubyGems, the code that makes it possible to create gems in the first place
- RubyGems.org, the website that provides free hosting for public gems
As time and funding permits, the Ruby Together team will:
- Roll out a new gem index that will make installing gems two to ten times faster than today
- Migrate all of RubyGems.org to the Fastly CDN, providing dramatic speed improvements when downloading gems and gem data
- Build a gem caching server to easily allow data centers and offices to cache local copies of the gems they need, whether public or private
- Improve RubyGems.org, adding search, statistics, and more gem information to every page
And there will be more! We start new projects based on community need and Ruby Together's available funding.
- Hire a second full-time dev to focus on Ruby, Rails, & other projects
- Hire a full-time dev to improve gem tools
- Create a public Ruby ecosystem analytics dashboard
- Merge Bundler and RubyGems into a single, unified project
- Expand RubyBench to comprehensively cover Ruby, Rails, and Bundler
- 3 devs at 1-2 days per week
- Maintain Bundler, RubyGems, and RubyGems.org
- Continuous improvements, as long as nothing unusual goes wrong
- 2-3 devs at 5 hours per week
- Maintain Bundler and RubyGems.org
- No maintenance on RubyGems
- Improvements only from volunteers
- Maintenance as time permits
- Fixes take days or weeks
- Improvements take months or years
We have ambitious fundraising goals, and as we hit them we will kick off even bigger projects:
- Create a public Ruby ecosystem analytics dashboard, including Ruby version usage, Bundler version usage, and dramatically expanded statistics for each gem
- Merge Bundler and RubyGems to stop bugs due to mismatched versions forever
- Expand RubyBench.org into a public benchmark for every commit of Bundler, Rails, and Ruby itself
When we hit $35k per month, we'll not only have developers maintaining every core tool, we'll have someone working to improve those tools full time as well. When we hit $50k per month, we'll hire a second full-time developer to focus on maintaining and improving Rails and Ruby itself.
Ruby needs this, and your help is critical to get it done.