The Xwiki project has spawned a number of related projects. One of the recent offspring is Chronpolys, a wiki-based project management site. It still doesn't have a 1.0 release, but it is in release candidate phase. It felt a bit more like a beta, but it had a lot of promise.
It calls itself wiki-based project management, but the wiki is really just one part among many. It combines a solid feature set including timelines, versioned documents, email notifications and of course a wiki. It has an attractive Ajax-full interface though it suffers from some organizational challenges and some interface clutter. Much of the success of Project Pier (or its predecessor ActiveCollab or paid counterpart BaseCamp) may be attributed to the simplicity of their interfaces. Chronopolys has them all beat on feature set, and the interface is slick, but it needs some simplification.
Chronopolys comes in a self-contained zip package that allows you to launch it on Windows, Linux or Mac OS by simply launching a script. This made it great for testing. After a quick configuration you can access the overview/dashboard.

Which can be viewed by timeline (above) or by asset type.

From there you can delve into the details of an individual project. This is presented in a useful fashion at first glance. But the interface for adding or manipulating resources is confusing.

It tries to strike a balance between displaying all of the information about your project and keeping a clean interface. But as the number of assets grow the interface begins to get cluttered and could be challenging for users to find the information that they need.
The wiki is based on xwiki, which is really quite good. And in fact having a wiki as a central part of a project management suite seems like a good idea.

Mindquarry tried that, and unfortunately failed. I hope that Chronopolys can succeed. Most of what it needs is a little less rather than a little more. A little refinement and documentation and this could be a great product.
Shortly after my recent Elgg review, Elgg announced that they are starting a new codebase and forking the current codebase into Elgg Classic. This new version will be more modular and they will package several configurations for different purposes. The only down side seems to the that setting up a Elgg-based site in the short term is a bit dicey, though they claim the data is portable. The long view is quite positive and worth keeping an eye on.
It calls itself wiki-based project management, but the wiki is really just one part among many. It combines a solid feature set including timelines, versioned documents, email notifications and of course a wiki. It has an attractive Ajax-full interface though it suffers from some organizational challenges and some interface clutter. Much of the success of Project Pier (or its predecessor ActiveCollab or paid counterpart BaseCamp) may be attributed to the simplicity of their interfaces. Chronopolys has them all beat on feature set, and the interface is slick, but it needs some simplification.
Chronopolys comes in a self-contained zip package that allows you to launch it on Windows, Linux or Mac OS by simply launching a script. This made it great for testing. After a quick configuration you can access the overview/dashboard.
Which can be viewed by timeline (above) or by asset type.
From there you can delve into the details of an individual project. This is presented in a useful fashion at first glance. But the interface for adding or manipulating resources is confusing.
The wiki is based on xwiki, which is really quite good. And in fact having a wiki as a central part of a project management suite seems like a good idea.
Mindquarry tried that, and unfortunately failed. I hope that Chronopolys can succeed. Most of what it needs is a little less rather than a little more. A little refinement and documentation and this could be a great product.
Shortly after my recent Elgg review, Elgg announced that they are starting a new codebase and forking the current codebase into Elgg Classic. This new version will be more modular and they will package several configurations for different purposes. The only down side seems to the that setting up a Elgg-based site in the short term is a bit dicey, though they claim the data is portable. The long view is quite positive and worth keeping an eye on.