Project HQ

Well, I've just completed the upgrading of the portions of Project HQ code to Pylons 0.9.7, so the next step is upgrading the templates to the next version of WebHelpers.

Things are moving a little slow at the moment, due to a number of commitments I have, but I'm hoping to take some time off in the new year to devote to developing Project HQ.

Once I've completed the upgrade, there are a couple of issues that I'm aware of that I'm going to tackle, and then I'm going to release Project HQ 0.1.1.

That's all for now.

With the pending releases of Pylons 0.9.7 and WebHelpers 0.6, I am going to be upgrading Project HQ to use the new versions of these libraries. Unfortunately that's going to mean that Project HQ will not be backwards compatible with Pylons 0.9.6.x and WebHelpers 0.3.

This is also going to be a fair amount of work while I work out all the kinks and bugs introduced with the upgrade.

Once I've upgraded Project HQ, I will release version 0.1.1.

I've mostly finished the work I wanted to do for the next release, version 0.1.1. I have done the permissions system and, apart from the occasional link, it's working. I've also introduced the concept of themes (which I have wanted to do from the very beginning).

I've updated the demo site to the latest version of Project HQ (you can find the login details in the documentation). It now includes permissions and roles, it has a configuration screen where you can set the theme as well as the site title and slogan.

I've also setup a script, which runs every 2 hours, to restore the database. This means every 2 hours the database will be wiped clean and the default project, milestone, tasks and users will be restored.

This weekend I worked on the permissions and have implemented most of the internal functionality. In order to make the menus more flexible, and to be able to add permissions and dynamic menus in, I moved the menu items to the database.

Unfortunately I'm one of those folks who likes to have his fingers in a lot of pies. That means that from time to time I'm spread a little thin.

But the last few days have been a little quieter, and I've started doing some work on the permissions and roles in Project HQ, which will eventually allow an administrator to govern who has access to what and where.

I've just finished getting the demo and the project page systems up and running. The demo is for folks to look at and play around with. If you encounter any bugs, please report them in the bug reporting forum.

The details for the demo system can be found on the Demonstration page in the documentation.

I've completed the migration of the subversion repository to the "new" Project HQ code. I have tested the code out, and it seems to work fine. If you have any issues, please let me know.

I'm also wanting to move to a friendlier url for the repository. "svn.projecthq.org" is aliased to "openpm-org.svn.sourceforge.net" at the moment (and will be updated when the project's SF.net unix name changes). So you should be able to type

If there seems to be nothing much in the subversion repository, it's because I'm busy migrating the code from "openpm" to "projecthq." On top of that, I've been having hassles connecting to SourceForge.net's subversion repository.

It seems that for whatever reason, the link between South Africa and SourceForge.net is very flaky at the moment. I keep on getting timeouts and reset connections. So please bear with me over the next few days while I try to get the repository migrated.

I thought I would start with the obligatory "Hello World" post. This is my first blog post of the newly named Project HQ project.

Welcome to the Project HQ site. This is the home of Project HQ, the open source web-based project management system written in Python and Pylons. We have some forums, and the beginnings of documentation, but at the moment that's it. We'll be updating the site as things progress.