From: Luis Lavena <luislavena@...>
Date: 2010-09-11T05:05:26+09:00
Subject: Re: rubyforge <-> gemcutter issues

On Sep 10, 4:37 pm, "ara.t.howard" <ara.t.how...@gmail.com> wrote:
> > I disconnected gem publishing to RubyForge and now gems are pushed to
> > gemcutter only while .zip and tar to RubyForge for OS packagers.
>
> > That is what I understood and assumed.
>
> agreed - but i cannot push to any of the gems i used to own, otherwise
> that would be an option.  i honestly don't completely understand the
> whole set of problems, but i think they fall into 4 categories
>
> 1) ownership after transfer

This could be related to the email/account records at RubyForge versus
the ones at rubygems.org. I had problems with this too and requested
the merge of these two accounts (both using the same email address) to
solve it.

> 2) syncing rubyforge -> gemcutter

Perhaps a failure on #1 could have rendered your old gems never to
appear in rubygems.org

> 3) gems never synced


> 4) lack of a simple README re: how it supposed to work.

Indeed.

Seems to me that the most grief about changes in the Ruby community
are associated with the lack of visibility and communication of those
changes.

I share my thoughts on that before gemcutter/rubygems conversion and
how things supposed to work afterwards.

--
Luis Lavena