new stuff for vamsas hack.

[vamsas.git] / docs / TODO.readme

diff --git a/docs/TODO.readme b/docs/TODO.readme
new file mode 100644 (file)
index 0000000..1e8a4f9
--- /dev/null
+++ b/docs/TODO.readme
@@ -0,0 +1,26 @@
+VAMSAS Library ToDO list\r
+------------------------\r
+\r
+Begun for the VAMSAS hackathon/sprint/fest/thing (13-15 December 2006)\r
+\r
+This file is a tabbed list of things that have to be implemented or \r
+tested in the SVN package. Check for updates regularly and \r
+add/modifiy it everytime you do something.\r
+\r
+Number - goes up by one for each item. If you delete an item, don't renumber stuff.\r
+\r
+Status tells us how far we've got on that item. Words like the following please:\r
+* - or nonexistent: its just been made up, nothing has been done on it yet\r
+* designed - someone has an idea how this item is going to be implemented (and ideally, they can describe it to someone else)\r
+* specified: prototyping has been done and checked in, either a text/graphic description is written down somewhere for anyone to access or abstract classes and interfaces have been declared.\r
+* implemented: code has actually been written to do what this Item requires done.\r
+* tested: the implementation is as bug-free and stable as we can make it (notwithstanding anything else that it depends on).\r
+\r
+Package/Classes/Path tells us where to go to find the relevant bits for this item in the repository, and an items package/class set might be written explicitly into the dependencies column of another item.\r
+\r
+Who - you, me or anyone else dealing with this item, or blank if no-one has got to it yet.\r
+\r
+Item - brief name for the development task.\r
+\r
+Dependencies - names of other items, or description of other things that have to be done before this Item can be finished (ie tested and completed).\r
+\r