From: Daniel Berger Date: 2009-01-08T10:26:07+09:00 Subject: Re: WANTED: need a real web API for rubyforge.org Ben Bleything wrote: > On Wed, Jan 7, 2009 at 11:12 AM, Daniel Berger 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. I'm not sure how division in the community over where projects live matters in any practical sense, except for Rubygems and your GEM_PATH setting. Even then, Tom could make it so that you wouldn't need to change anything, as he could script where the gems actually live. > 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. Oh, yeah? Who's gonna build it? And even _if_ someone undertook the project, no one is going to agree on how it should look, feel and act anyway, so it will _still_ result in division no matter how you slice it. Regards, Dan