Unfuddle vs Assembla: Git Support

Assembla seems to be having problems with their git service, and that’s too bad; now, I’m going to go use Unfuddle instead. The forums suggest that this has been an issue that started maybe a couple weeks ago. Of course, had I known this, I wouldn’t have spent the better part of yesterday and a couple hours today, banging my head against the wall.

I did, however, become much more well versed in the distributed source management system known as git. By the way, GitCasts is like the best thing to learn git from, I just hope that one day we’ll see all the commands that were used during the screencasts for easier consumption. Even as this project is going to most likely stay a solo venture, the saner branching/merging I keep hearing about makes my heart flutter.

But less about git, and more about the services that are providing git hosting: I liked Assembla because of their integration with Trac, one of my favorite bug tracking tools. I wasn’t familiar with Unfuddle’s or Assembla’s own milestone/scrum/chat/ticket system, and so I wanted to just keep using Trac. After tonight’s mess, I think I’m going to go and stick with Unfuddle for the time being and just try to start using their refreshingly different UI for all things project management. After all, I can move the entire repository with a single clone anyway.

Assembla: "Backpack" for Software Engineering and FREE

I’ve found myself need a full toolkit for software development as I move forward with HanMeta. This list includes goodies like:

  • Wiki/Documentation
  • Bug Tracking
  • Source Code Management
  • Chat/Communication Tool
  • AND something to put all of this together.

Assembla has been working well. It’s kinda like basecamp for software developers. The application just screams Rails and lickability.

I have a couple of issues with using Assembla though. For one, I don’t like how I’m not in charge of my own data. Sure, with Subversion and Trac, I can just export the codebase back out using the standard interfaces they offer, but they have their own built in wiki and messaging system. I don’t see an easy way to export that data, because it would be nice to have a backup of the data… I don’t know how that would look like, since all of this data that exists on their servers is going to be in some proprietary format anywa.

The funny thing is for my job at NCSA, I had to do the same thing for the Blue Waters Project. I was in charge of looking into some project management, bug tracking, source control system. In the end, the suite of applications at Atlassian seemed to be the best bet. Since money wasn’t a problem, this was the valid choice.

Since all the funding for HanMeta is coming out of my pockets, it’s pretty important for me to keep my costs down. Using Assembla, I can effectively outsource all of the pain of maintaining and dealing with multiple tools. Plus, it was easy to get started.

I bet I won’t be saying the same when the Assembla servers go down… but that’s another story.