project flow & tracker

Project Flow & Tracker basic (non-UI) installation profile on GitHub - Status update for early-December 2010

Project Flow & Tracker installation profile is now ready in basic, non-UI form at https://github.com/victorkane/ProjectFlowAndTracker/tree/6.x-1.0-alpha1 on the 6.x-1.0-alpha1 branch. Be sure to change to that branch after cloning the project or else before downloading the tarball. Instructions are on the README.md file for that branch.

The installation profile includes the following:

Project Flow & Tracker "Chicago" ready for basic use and download - Status update for mid-November 2010

Now close to "Chicago" release candidate and more usable than ever, the Project Flow & Tracker project has been made public and promoted to front page so you can browse the read-only functionality. I believe browsing from business model to roles to user stories to constituent tasks and back again is the best way (in theory and in practice) to understand what has been achieved at this point.

Much greater usability has been achieved, which is something that will be receiving a great deal of attention as a jQuery based UI layer is implemented in the next phase.

Features driven development -- the nitty gritty and thoughts on the future of sustainable "in code" development

Features driven development in the Drupal sense involves placing code into versionable text files and packaging functionality into reusable components rather than relying on error prone user interface based configuration with scripting stored in the database along with the content rather than in code. It has been a great step forward for Drupal developers. It is simply a joy to once again be able to develop without infecting the code repository with database dump blobs. And to be able to install functionality in multiple servers running different applications irrespective of the content production workflow. But it is not without its contradictions and limitations, which I would like to mention in this article for the sake of discussion. However, while I will propose ideas for a better solution, I am mostly concerned with leveraging development in code right now by finding a comfortable process for using features driven development today, based on the promise of Adrian Rossouw's now classic "Database Is Silver, Code Is Gold" article The Development -> Staging -> Production Workflow Problem in Drupal.

Project Flow & Tracker Chicago - Status update 20100928

Even though I'm being very quiet about this until I can launch a fully usable staging, good solid progress is being made thanks to the productivity of Panels Everywhere and the panel layout plugins from the Precision theme:

Project Flow & Tracker Chicago - Roadmap and Status

Planning to be in Chicago to present new version of Project Flow & Tracker ("Chicago").

It should be basically usable in a couple of weeks. It's based on Panels Everywhere and OG, and a sub-theme of NodeOne's Precision theme.

An exclusive theme, logo, icons and graphic design work is being done by Buenos Aires designer Juan Villegas.

Functionality basically the same as always, now a little more Scrum'd up I would think. Full details available soon.

Subscribe to commits: http://github.com/victorkane/ProjectFlowAndTracker/commits/master.atom

From the Github README:

"The all new ProjectFlowAndTracker Chicago based on Panels Everywhere and OG

PFT is bootstrapping itself, being used for its own creation, and will be usable soon.

Syndicate content