Project HQ

To those folks who celebrate Christmas, I'd like to wish you a merry Christmas. To my fellow Christians, I hope that you remember the real reason for Christmas, and I wish you a blessed day.

Just a quick update for those folks visiting the site and wondering if the project is dead, the good news is that it isn't. The bad news, however, is that with the arrival of my son at the end of July, I haven't had as much chance to work on Project HQ as I'd like.

As someone pointed out in the IRC channel, there have been no apparent updates to Project HQ in a while. Unfortunately I haven't been able to devote as much time to Project HQ recently as I have been before, but I am still working on it!

Currently I'm busy doing some minor internal re-architecture, changing the way things work a little, to make it easier and faster to work with. It also provides a nice validation framework for both client side (JavaScript) and server side (Python) validation.

I've just released version 0.1.3 of Project HQ, with the new ticketing feature!

Please note that you will need to download TurboMail 3.0b2 and install it via easy_install.

Well, I've successfully added uploading of attachments to tickets. You can even add additional attachments by updating the ticket. In addition to that, if you upload source code, it is viewable and it's syntax is even highlighted.

At the moment only HTML, PHP, CSS, Python, Perl, Ruby, Javascript and Pascal are supported, but I'm busy working on supporting more languages.

I've updated the demo for those who want to play around with it, and I'll release an egg file once I've done a little more testing and bug fixing.

Well, after a weekend of hacking, I have some basic ticketing working. You can see what I've done on the demo site.

At this stage you can't upload attachments, but that's the next step. After I've sorted that out, I'll be implementing the e-mail notification system, which will notify you of anything assigned to you, or anything you create or edit.

I've also "wikified" a number of the text fields, so you can put wiki text into some of the description fields, and it will be rendered correctly.

The last 2 weeks I've managed to get some time to work on Project HQ, and I've made a start on the ticketing part of it. Folks will be able to do their bug tracking in Project HQ at the end of this.

At the moment I've got the adding of tickets working. The next part to get working is viewing/updating. I've modeled the ticketing mostly after a combination of Trac and Launchpad, while taking a little inspiration from other issue tracking software like RT and the commercial JIRA (which we use at my day job).

Just an update for those folks who come across this site, I haven't done much work on Project HQ in the last few months due to time constraints.

I'm still passionate about this project, and I'm planning on getting the ball rolling again soon, but for the moment I've put development on hold because of a few commercial projects I've been asked to do and work on a couple of other open source projects.

I'm leaving my current job at the end of this month, and moving to a new company in April. Because of this, I don't have much work to do at the moment, so I'm trying to keep myself busy.

One of the things that needs work in Project HQ is the wiki syntax parser. It's very basic, and doesn't even handle things like paragraphs correctly. So I've been working on it in an effort to keep busy.

For me, a project management system is not complete without a bug tracking system. So my next step is to implement bug tracking in Project HQ. I've looked at a few bug/issue tracking systems, and I've decided to model mine after the one in Trac.

So far, I have completed the database design, and my next step is to start implementing the bug tracking in Project HQ. Thanks to SQLAlchemy I don't have to actually worry about creating the tables, as they are created when I do a "web setup."