Intergrated test scripts with automake

[gnucomo.git] / TODO

diff --git a/TODO b/TODO
index ccf001c..c24bab0 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,16 +1,43 @@
 
- - multiline log entries in gcm_input.
- - several files don't have version identifiers; a simple $Id: TODO,v 1.2 2003-02-05 09:57:15 arjen Exp $ in the
+ - several files don't have version identifiers; a simple $Id in the
    comment would help in finding packaging bugs. (Also recommended for
    the documentation files)
- - Some files have lines longer that 80 characters.
  - Most makefiles and stylesheets miss a copyright header. 
- - There is no reference to the gnucomo website.
- - There is no list of required and recommended software.
- - A step-by-step installation guide is missing.
- - The installation description in the manifest must be
-   updated to include the ./configure script.
- - The input filename for gcm_input can be a command argument.
- - Both the web interface and gcm_daemon use similar PHP classes.
-   These classes should be unified one day and stored in a single
-   directory.
+
+Documentation:
+ - There is no reference to the gnucomo website in the manifest, design,
+   README.
+
+Web Interface: 
+ - A page with notification (independent of object) (with sort capabilities
+   and grouping per urgency).  (PR 7)
+ - With an object one should be able to indicate what OS is being used
+ - Webpages should look more 'sexy'
+ - Draw graphs of DYNAMIC properties.
+ - Use XML/XSLT technology for the web interface.
+ - Create valid XHTML.
+ - Edit the range of DYNAMIC properties for each parameter.
+
+  Whish (future):
+
+ - Linking database users to objects (only certain objects can be shown to certain users)
+   (PR 3)
+
+GCM_INPUT:
+ - Make a proper master daemon for the Gnucomo server. This daemon handles
+   authorization of clients, scheduling and dispatching.
+ - The input filename for gcm_input can be a command argument. (PR 9)
+ - When gcm_input can not make a connection to the database, its input
+   message will be lost. In such a case, gcm_input should store the
+   message in a spool directory for a retry later on. (PR 10)
+ - Indicate to gcm_input what type of data is delivered (PR 11)
+ - Update statistics in the object table when a new parameter is entered
+ - Update statistics in the object table when a new notification is entered
+
+
+GCM_DAEMON:
+ - Build IP-database on the basis of whois
+ - Create mechanism for starting and ending the daemon.
+ - Performance check on the gnucomo-database
+ - Detect traces of log entries and use these traces to create notifications.
+ - Trend analysis of DYNAMIC properties.