From: Luis Lavena <luislavena@...>
Date: 2009-11-22T17:05:05+09:00
Subject: Re: RubyForge gem index is no more

On Nov 22, 2:36 am, James Britt <james.br...@gmail.com> 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.
>

No, there wasn't, as all the communications about the move, the
decision and everything happened in the background.

Just to summarize:

August 26, 2009:
Nick Quaranto posted his proposal to replace the canonical gem serving
with Gemcutter.

http://rubyforge.org/pipermail/rubygems-developers/2009-August/004914.html

October 26, 2009:
Nick Quaranto announced that conversation with Ruby Central about
shutting down certain services of RubyForge having Gemcutter taking
over some of them:

http://update.gemcutter.org/2009/10/26/transition.html

Then, November 16, this post:
http://update.gemcutter.org/2009/11/16/moving-forward.html

And that's all.

Of course, there was lot of twitter noise about it, lot of disruption
about gem service that mistakenly got reported to RubyInstaller and
RubyGems projects.

A trend or practice that is getting used in Ruby-land:

http://blog.mmediasys.com/2008/12/29/guas-giving-unwanted-advice-series-2/

--
Luis Lavena