Hypothetically lets assume you’re a gamer with an idea for a game. This should be easy to imagine. You want to make a game but have no money. Once you have chosen your team, and gotten some idea of what you are building (with a game design document), and picked your distribution/coding platform, you realize that you need to keep track of a lot of different kinds of information. Specifically bug and issue tracking.
There are many great services out there with the ability to track issues, but there is another method which is often overlooked. You can build your own bug tracker using sites.google.com. As we were starting the ZoRTS project the Lead Coder asked me to find bug tracker to use. As a manager on a project with no money something with low cost is ideal. The following video on youtube provided the answer.
- Works with other Google services
- Cheap! As in free.
- Hand built to do exactly what you need it to do.
- There are other methods which may be better
There are a couple factors left out of the pros and cons. For example using sites.google.com as your issue tracker takes effort to build and maintain. You have to have and idea of what kinds of things you need to track ahead of time, and how the page is going to be used. The ZoRTS website includes an example page so that you can get an idea of the kinds of columns that you might need. However this is a moot point as you still need to spend time and effort updating and recording in any bug tracker. It might just take a minute or two more to use google sites.
So what do you use to provide an infrastructure for communication of issues, bugs, design changes? Why do you like to work with it? If you have experience in the area please leave a comment below, let us know your opinion.