From: Ben Bleything <ben@...>
Date: 2009-01-08T09:59:38+09:00
Subject: Re: WANTED: need a real web API for rubyforge.org

On Wed, Jan 7, 2009 at 11:12 AM, Daniel Berger <djberg96@gmail.com> wrote:
> The best approach, in my opinion, is to:
>
> 1) Register http://www.rubyforge2.org using Redmine.
> 2) Encourage people to register their projects there instead of the
> current system.
> 3) After about 6 months, if all goes well, ban new project creation on
> the current Rubyforge (though leaving everything else intact).
> 4) Strongly encourage people to migrate their projects over to the new
> system.
> 5) After 3 (4, 5?) years, shut down the old RubyForge, making
> rubyforge2.org an alias for rubyforge.org.


I think this is a *terrible* idea.  The last thing we need is further
division in the community about where projects live.  Don't get me
wrong, I think the spirit is right, but doing it *in this manner*
makes me uncomfortable.

It would be far better IMO to build a new RubyForge from the ground
up, and when it's reasonably feature-complete and the community
agrees, migrate over and shut the GForge instance down.

> I don't think there's any hope of "migrating" projects from the
> current system to Redmine, though. Perhaps as a paid service, but
> while tickets might be easy, mailing list archives and wiki
> information would be especially difficult. Maybe I'm wrong, though.

I don't necessarily agree that Redmine is the right solution to this
problem, but I believe that any replacement needs to be relatively
transparent... which means everything that's on RubyForge now needs to
be migrated.

Ben