-multiline log entries in gcm_input.
+ - 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.
+
+Documentation:
+ - There is no reference to the gnucomo website in the manifest, design,
+ README.
+ - There is no list of required and recommended software. (PR 5)
+ - A step-by-step installation guide is missing. (PR 6)
+ - The installation description in the manifest must be
+ updated to include the ./configure script.
+
+Web Interface:
+ - A page with notification (independent of object) (with sort capabilities
+ and grouping per urgency). (PR 7)
+ - A page with detailed object-data (PR 3)
+ - With an object one should be able to indicate what OS is being used
+ - Webpages should look more 'sexy'
+
+ Whish (future):
+
+ - When looking at a logline it is usefull to see the related log_adv records
+ (PR 8)
+ - Linking database users to objects (only certain objects can be shown to certain users)
+ (PR 3)
+
+GCM_INPUT:
+ - multiline log entries in gcm_input. (PR 2).
+ - 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:
+ - Process e-mails
+ - Create indexes on log_adv_daemon_email
+ - Build IP-database on the basis of whois
+ - Work on undetected kernellines
+ - Create mechanism for starting and ending the daemon.
+ - Performance check on the gnucomo-database