RubyForge now has Git support

Folks using RubyForge have been requesting alternatives to CVS and Subversion for a while - there are feature requests in for Mercurial, Monotone, Darcs, and Git.  Of those, Git seems to be the most popular at the moment, so thanks to Garry Dolley's excellent tutorial on Gitosis, RubyForge now supports Git as one of the SCM choices.    Huzzah!   Garry not only put up the tutorial, he also volunteered EBay4R as the first project to use Git and helped me work through the initial configuration.  Thanks, Garry! 

This Git support is still pretty new, so I'm not quite sure if we've got all the right things set up.  But you should be able to start a project, select Git as the SCM, and push to and pull from a repository on RubyForge, and the Git repos are part of the nightly backup job.  There are nine projects so far that have established Git repositories, so something must be working.  Also, I've put up some notes in the RubyForge FAQ on getting started with a repository. 

Dr. Nic Williams posted some helpful notes on using RubyForge Git repositories.  He's also got some ideas on RubyForge supporting both Svn and Git for a project which are being discussed in a support ticket. 

Another thing I'm thinking about is providing a sort of pseudo-SCM that lets you say "the source for this project is hosted on GitHub or Gitorious or some other place".  Does anyone think that'd be useful?

Comments and suggestions are always welcome, and as they say on the Rails Envy podcast, let's git 'er done!   

Comments

[Dr Nic]

Huzzah indeed!

[Trevor Turk]

This is great news. Personally, I would like to have an option to note that your SCM is elsewhere. I've settled into github pretty well, although I'd like to maintain my project's presence on RubyForge.

[raggi]

Absolutely fantastic, any distributed system would have made me happy, but git saves me harddrive space too...

Many, many thanks.

[raggi]

Sorry for the double post, but Dr. Nic - you can have multiple remotes, it's a distributed system :)

You can also have the two repo locations sync up, or use the github post-commit hooks to do a push or instanciate a pull. A simple pull-request POST form on rubyforge might also be a good idea, maybe.

[Martin]

As answer to the question about the pseudo-SCM-link thing, and to quote the Electric Six: It would be AWSOME!

[Marty]

I'd be supportive of the pseudo-SCM option. I can see that being useful.