Planning - Roadmap.
This is the intended and very loose 'Roadmap' - a guide to what we think will
happen in the project and when.
Our current stage is the beginning. We are discussing what to include and exclude,
and how to go about 'doing stuff.'
Below shows a chart tracking our position. The green row indicates our current
state.
Date |
Stage |
Comments |
2002 May 29th |
Planning |
We know what we want to achieve, we've just got to
set it down in the form of a web site to promote our ideas and provide a
reference to ensure we do indeed achieve what we set out to do. Project
members are coming forward with offers of thoughts and ideas, and graciously,
time. |
2002 June early |
Document initial classes that should make up the basis for the code |
This code should underpin the work of the API and must be thoroughly documented.
Every variable coming in to and out of a function should be documented to
remove any abiguities. |
2002 June middle |
Create initial skeleton classes |
Core of the project should be started. Basic code necessary, as necessary
to have a clear idea as to how things operate. |
2002 June late |
Core classes should be somewhat useful. Create intial cut at database
schema and add basic template support |
Moving beyond the initial code we should be able to progress to fleshing
out some of the functions and ensuring they can interact in sane manner.
Various object properties should be being worked out and the API built up. |
2002 July early |
Should have the ability to 'plug' the code into a dummy website and have
it do something useful. This requires only a skeleton database design and
templates. |
Should finally be capable of something useful in a 'foreign' environment
- that of another person's website. |
2002 July late |
First cut at an alpha or beta release |
The code should do something pretty useful by now, and have a moderate
amount of documentation. The API should be at least 50% complete and documented. |
|