I think ccrb should have picked github to host instead of rubyforge, because of graphs like these [1], other slick interface features, and the general momentum behind the community there. Also, there are multiple [2] outdated forks there already, including mine, and AFAIK there is no easy automated way to sync. I'd have to cron a "sync" job with a local repo pulling from rubyforge and pushing to github. I also don't know of (or see why they would provide) options to do this automatically from either rubyforge or github.
[1] http://github.com/thewoolleyman/cruisecontrolrb/network [2] http://github.com/benburkert/cruisecontrolrb/network _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
