The purpose of this document is to provide a roadmap for the development of
Uptimed.
 
Please add your name to items you wish to work on in the future, so other
developers know they have to contact you before starting on an item. Put
your name in capitals in case you _are_ working on an item, so other
developers know they should leave that functionality alone. Communicating
your efforts on uptimed-devel@lists.capsi.com might not be a bad idea
either.
 
- not implemented
? bug is fixed, not confirmed yet (remove entry upon confirmation)
v implemented, not confirmed yet

Bugfixes
--------

- When the system hangs during a write, the logfile can get corrupted.
  Solution: use two logfiles, check validity and use the most recent one.

For 0.1.x
---------

- configurable layout (ability to make the headers centered)

For 0.2.0
---------

- Write ncurses uprecords and split uprecords into uprecords.cgi and ncurses
  uprecords if necessary
- Include KDE panel applet GUI (cap)
- Improve mailing option for uptimed.

For 0.3.0
---------

- Cool Gnome/WM progs that play a happy sound or pop-up when breaking the
  record or reaching a milestone. Contributions in this area would be very
  much appreciated. I will create the KDE applet myself.

For 0.x.0
---------

- More portability? (BSD, Solaris, Windoze??)
- Networking, kinda like rwhod. Uptimed broadcasts to localnet
  (configurable??) and listens as well. Every machine has info for the
  entire broadcast range (/var/spool/uptimed/host.records). Uprecords can be
  called/configured to list: this machine only, a specified host or all. I
  might drop this option or delay it and instead code in support for the
  www.uptimes.net project, although I do like the idea of a rwhod alike
  implementation.
- Add reason to save_records (SIGTERM/SIGHUP==reboot, none==CRASH??)

For 1.0.0
---------

- Have all that included and still have the GPL as biggest file in the
  package. ;-)
