[ruby-core:26344] RubyForge and RubyGems and GemCutter...

Hi all -

This has been announced in various forums, but we should have sent a  
message here in the initial flurry.  To summarize, some major gem  
indexes are going to be consolidated - GemCutter and  
gems.rubyforge.org will move to rubygems.org and form one massive gem  
index.  This index will be fronted by Nick Quaranto's excellent  
GemCutter rails app.  This app will be running on Ruby Central's  
infrastructure at Rackspace.

The entire announcement, more details, and a comment thread with some  
discussions here:

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

As part of this transition, RubyForge is going to be slowly stood  
down.  It won't simply be turned off, of course; we could see it  
staying in read-only mode for quite a while.  But that's where things  
are headed.  The community hub functions of RubyForge will not go  
away.  Community features that RubyForge uniquely provides (or should  
provide) will be added to the source base of the app that GemCutter  
started with and will be maintained on github.

This is a change; but it's one that we at Ruby Central feel is  
important.  We want to provide the community with what it needs.  With  
services that Github, the new SourceForge and Google Code provide we  
feel that source management, mailing lists and bug tracking are being  
better provided by others.  We want to focus on community features.   
We will be developing those quickly and that will all hub at RubyGems.org 
.

Yours,

Rich Kilmer
Ruby Central