From: Luis Lavena <luislavena@...>
Date: 2009-11-23T12:30:10+09:00
Subject: Re: RubyForge gem index is no more

On Nov 22, 11:00 pm, Tom Copeland <t...@infoether.com> wrote:
> On Nov 22, 2009, at 3:05 AM, Luis Lavena wrote:
>
> > 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.
>
> Yup, please see my other post about some of the thoughts behind that.
>

Tom, I'm not arguing why the communication was in the background or
not, I'm cool with Gemcutter and really like it.

The issue, from my PoV is other.

I've closed several bug reports and responded several emails about 500
errors and 403 errors when installing gems.

Is not that these users didn't connect properly to the new server, but
they had an older version of RubyGems as part of the combo with other
issues that I couldn't replicate

A better heads up, not just for Ruby gem authors for community as a
whole using channels like RubyForge, Ruby-Lang and Ruby-Talk would
have been great.

Anyhow, canned a template answer with links to either my own posts and
Gemcutter ones for the time being.

Thank you for your time answering my comments.

--
Luis Lavena