I liked this feature, but I think it makes sense for them to remove it. To me it highlights the fact the Github has grown way beyond just hosting Ruby projects.
I'm currently in Rio for the Lua Workshop and many people here have said they'll be moving their projects from CVS or SVN over to Git and Github. I am guessing that within a few months Github will be the defacto standard place to host Lua projects just like it is for Ruby. Hopefully they have at least 50 megabytes of free space to accommodate all of us. ;-)
"I liked this feature, but I think it makes sense for them to remove it. To me it highlights the fact the Github has grown way beyond just hosting Ruby projects."
Then another option would have been to do the same thing for non-Ruby projects. Integrate with CPAN; build eggs (or whatever it is that Python uses); create Cabal packages.
That was the conclusion we came to: either do them all or none of them.
The problem is with the amount of time we spent working on, maintaining, and fielding support requests for rubygems, the last thing we wanted to do was multiply that work supporting additional systems.
This decision wasn't made lightly, but the service and support will be better off with it gone.
I'm currently in Rio for the Lua Workshop and many people here have said they'll be moving their projects from CVS or SVN over to Git and Github. I am guessing that within a few months Github will be the defacto standard place to host Lua projects just like it is for Ruby. Hopefully they have at least 50 megabytes of free space to accommodate all of us. ;-)