From: Tom Copeland <tom@...>
Date: 2009-11-23T11:00:16+09:00
Subject: Re: RubyForge gem index is no more


On Nov 22, 2009, at 12:36 AM, James Britt wrote:

> Gregory Brown wrote:
>> Honestly, even if there was an announcement here, I might have missed
>> it, I'm just lucky to have vigilant users on Prawn who noticed our gem
>> hadn't updated :)
> 
> I don't think there was much of any discussion or announcement on ruby-talk about moving gems off rubyforge and having gemcutter take over.

I think the hope was that for most people nothing would change, since gems.rubyforge.org was repointed to the new box.  So "gem install rails" keeps on working.   Also, Ruby Central is running the gemcutter app instance that's serving everything, so that's the same also.   Many gem publishers are affected by the move... although many had already moved over to gemcutter (or first to github and then to gemcutter).  Hopefully everyone else will see the recent ruby-talk traffic and the mass email to all RubyForge admins.  

I guess the idea was that this was more of a service improvement that most Ruby users wouldn't notice, except for the improvements.  Instead of a static gem index with a 5 minute delay and no user interface, there's now an excellent site that can actually be searched effectively.

But I agree - more comms on ruby-talk would have been good.

Yours,

Tom