update / merge todo list

define DBMS configurations prototype

1 files changed, 23 insertions, 0 deletions

diff --git a/fml/lib/FML/Ticket/00_DESIGN.txt b/fml/lib/FML/Ticket/00_DESIGN.txt
index 415de9e3..e7af69ef 100644
--- a/fml/lib/FML/Ticket/00_DESIGN.txt
+++ b/fml/lib/FML/Ticket/00_DESIGN.txt
@@ -15,3 +15,26 @@ Ticket::Model::toymol   Ticket::Model::toymol2   .......
 	$ticket = new Ticket::Model::toymodel;
 	$ticket->asign($curproc, $args);
 	$ticket->update_cache($curproc, $args);
+
+
+=head1 REFERENCE
+
+=head2 ticket status ("RT" case)
+                
+A Request will always be in one of the following four states:
+
+    Open -- the Request is expecting imminent action a/o updates
+ Stalled -- the Request needs a specific action or piece of
+            information before it can proceed
+Resolved -- the Request has either been answered or successfully
+            taken care of, and no longer needs action
+    Dead -- the request should not have been in the ticketing system to begin
+            with and has been completely purged.
+
+=head2 "REQ" case
+
+       Another somewhat hardcoded features is the "status" field.
+       We're not exactly sure how to use this yet,  but  normally
+       use  "stalled" to indicate that this request isn't one can
+       make any progress at the moment, thus isn't worth  picking
+       from the queue to work on.