You can use both, that's what for example Scala IDE does. Assembla has a lot more to offer than what you get with Github. http://scala-ide-portfolio.assembla.com/spaces/scala-ide/github_tool
I want avoid that information is spread out over many different places, Code hosting: * SVN * Git * Advanced merge requests for Git, pull and test changes, vote on the request; request comment will http://blog.assembla.com/assemblablog/tabid/12618/bid/80158/Announcing-Advanced-Merge-Requests-for-Git.aspx This feature is excellent for open source projects, since the project members can directly vote on features within the request UI, no need to have long voting threads in mailing lists. Build tool integrated * http://www.assembla.com/spaces/breakoutdocs/wiki/Build_Tool_Overview Assembla collaboration features * Wiki * Files tool (upload and store files, integrated with Google Docs) * Messages / message board http://www.assembla.com/features/collaboration?locale=en#3 * Standup reports * Group chat with video * Work as a team - activity stream (real time feed of all activities, can be be filtered based on source, e.g. Wiki, tickets, etc., email alerts, Twitter activity integration, WebHook to post activites to an external system) * Email integration (create tickets through emails, attachments will be added to Files tool automatically) Team and project management * Time tracking * Reporting Most of these tools can be configured for the project workspace, only adding to the UI what you need. I think GitHub isn't nearly as powerful as Assembla, and since we are not going to work full time and paid on a fork, I have the feeling that Assembla might be useful. I especially like the Google Docs integration, since I've been using Google Docs a lot instead of Wiki pages in the past year. Raju
