So far the responses to the survey have been overwhelmingly positive and encouraging. There has, however, been a few detractors with some noteworthy comments.
The main complaint I’ve seen so far is from people getting the impression we want to somehow “reimplement” Rubyforge or create another repository for gems or plugins1. I can’t imagine something like this could be of any real benefit to Ruby, or Rails.
There’s already a list of plugins, There’s all ready rubyforge, there’s this, there’s that. We don’t want to take away from any of that. We want to tie them all together—and make it easy. That’s the most important bit, making it easy. Easy to find. Easy to keep up with. Easy to change.
I think the “forge” in “RailsForge” is causing a visceral reaction in some people, and I understand that. Perhaps “RailsForge” is misleading. It seemed an easy and available choice for a name, but maybe not the best.
—
1There’s some debate about plugins and gems, or “plugins vs. gems” I should say. I’ve got to say straight up I side with the concept of sharing code between apps using the gems system.
0 Responses to “The Direction of RailsForge”