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 thatGemCutter 
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

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.

My $0.02--rubyforge was good but could easily go away. That being
said,
I do find it useful for file distributing [i.e. I typically know where
to go to download non gems, like rubygems-1.3.5.tgz], and several
people
still use it for publishing documentation (their own style, their own
way, not mass produced like allgems.ruby-forum.com or rdoc.info). I
therefore would move it not be abandoned entirely yet, which is
apparently already in your plans
Thanks for the good work there and keep it up.