We seem to have had the same idea. =) I've been writing a repository replacement in ruby on rails for several months. An incomplete version is already uploaded and working at http://roborumble.org, with a domain and VPS that I got specifically for this project. I'm not sure how we should proceed from here. If you're just at the planning stage or haven't written much code, would you consider helping me with the one that I've started? I'd be happy to have another person working on it. If you've already invested a lot of time into it, I don't really know what a good solution is. It seems silly to have two repositories, but I'd also hate to have all the work and money I've put into roborumble.org go to waste, and I'm sure you feel the same about your new rails repository. Any thoughts?
Good to see people helping the community. I'm pretty much going to redo the site anyway just for the sheer pleasure of programming. I'd be willing to grant svn access to others who would like to refine or add new site features after I get it launched. If we have multiple people supporting the site then it will much less likely fall into disrepair. It should be pretty easy to work with the source code - I'm using best practice RESTful + MVC design principles. The code is extremely clean so far. I appreciate your investment in the roborumble site - I've made the same investment. With the new robocoderepository RESTful/webservice API, you could actually use robocoderepository as an ActiveResource? source of data for your own site. Then you could build any rumble-specific features into your own site. ...or add them to robocoderepository itself.