Dan Newcome, blog

I'm bringing cyber back

Distributed issue tracking

leave a comment »

I was checking out one of Zed Shaw’s latest projects, MulletDB when I realized that the project used Fossil, a source control system that I had never heard of before.

As I checked around the Fossil site, I realized that this is just what I needed for a lot of my projects. I want to keep the development notes and track issues right with the project itself. This means that you have to have some kind of bug tracker or wiki set up so that it can be run from the working folder, and the database must be checked into version control. This possibly means that in order to commit changes to the bug tracker you might have to stop the server, which would be just one more step in the check-in dance.

I’m sure that Fossil is a nice SCM, and having been developed by the creator of Sqlite, it probably is a very thoughtfully designed piece of software. However, I’ve become invested in git, and with Github being the SCM hosting provider of choice I’d really like to see something like this that uses the git repository format on the back end so that everything can be distributed and versioned using git. Even better would be if Github would update its own issue tracker when you pushed issues using git.

– Update: I just found TicGit, which stores all of its data in a special branch of your existing git repository. Bugs Everywhere is another interesting project, although I don’t think it uses git.

Advertisements

Written by newcome

May 29, 2010 at 2:44 pm

Posted in Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: