Considering this previous post of mine, seeing me announce something brand new has to seem more than slightly wrong. After all, why make a new item, rather than extend an existing one? How can I justify making Bit Vizier (AKA yet another issue tracker) when I just condemned making yet another framework?
In this case, I have two reasons for doing so. The first is that the other issue trackers out there fall broadly into two categories:
- Code I do not wish to extend. I'm a Python developer, so tools like Request Tracker and Redmine do not appeal to me due to their language choice. The products may well be wonderful, but if I hate working in the codebase, I'll never do anything with it.
- Systems that I would have to nearly reinvent anyway. Trac is a marvelous tool. But for me to carry my issue tracker to completion (as I see it), I would have to alter so much of the core of Trac that it would no longer be Trac.
- The ideas would require significant modification to the Trac core components.
- Making those modifications, and getting them accepted, would basically mean you would have to become a member of the core Trac team.
- Becoming a member of that team is extremely difficult.
- These ideas go against what the Trac team wants to do, and are not likely to be implemented by them any time soon.
On the other hand, the ideas standing on their own have merit. I've at least set up a website for the project (yes, I'm using Trac until this is self-hosting. I believe I mentioned that Trac is excellent, didn't I? They just won't like my ideas), along with a Mercurial VCS that can be cloned. With any luck, I'll even be doing a talk on it at Pycon in Atlanta, GA.
As a very quick overview of my plans: I'm looking to make a shared issue tracker, built on top of TurboGears. The ultimate goal for it will see me able to integrate with a variety of tools, and even use Bit Vizier as the basis for other tools I've been thinking of for a few years. The pieces are finally coming together for me.
For now, take a look at the site, and tell me what you think.