Motivation to use Assembla or a similar service: If the community forks the project, we should spend as little time as possible on infrastructure, and still make it as easy as possible to communicate with other team members and the community. Sourceforge can be relatively complicated, with a lot of manual work due to the bad integration between the SVN server and Trac.
Assembla supports things like group chat, Skype integration, Eclipse IDE integration into the ticket system, Git, SVN. I think migrating the OL code to a Git repository would be big plus. Why the Assembla.com based URL might not be good idea? The project will probably be less visible than at the big open source hosting services. Here are some blog post listing reasons to use a service like Assembla instead of sourceforge: http://community.impresscms.org/modules/imblogging/post.php?post_id=199 "Assembla adds some interesting features not present in other hosted code repositories - there is group chat, skype integration, stand up reports (if your a Scrum developer, you'll recognize this), Plus, the subversion and ticket integration is an essential piece for us. Sourceforge, sadly, fell down on this one. Also, this new environment will allow Eclipse users (or any other IDE that uses MyLyn) to tie into the ticket system, not just the code!" http://theoreticalecology.wordpress.com/2010/02/16/sourceforge-vs-google-code-assembla/ Indefero is interesting since the software is open source. That means, we could start out with a hosted package for the first 6-12 months, and then set up our own server if we want to. And here is a list of alternatives to Sourceforge: http://alternativeto.net/software/sourceforge/ Raju
