This isn't an official list of plans.  It's basically just some notes on where
we want to be going.  It's something to consult when sitting down to write
some code and deciding what to work on.


 Recent goals achieved (in tree, not necessarily published yet)
 --------------------------------------------------------------

* GroupDAV and "webcal" (icalendar over dav) support
* Updated schema for publishing Citadel address book data into an
  external LDAP directory (still awaiting enterprise number from IANA)
* Internationalization (WebCit is now available in several languages.)

 Goals to achieve during the 7.xx cycle
 --------------------------------------

* Aliases, virtual addresses, and distribution lists
  (We ought to be able to handle all three of these using the same facility.)

* CalDAV support (eventually -- since the protocol is so ugly and needlessly
  complex, the draft authors are still arguing over small details -- once the
  draft is finalized, we will implement enough of CalDAV to support the two
  major client packages currently using it)

* Integration of CMS and social software features (more on this later).

* Further internationalization (for example, in the citserver).

* Per-user auto-handling of inbound mail.  Simple handlers such as an "out
  of office reply" should be easy for users to set up.  More complex handlers
  such as the automatic sorting of inbound mail into various folders based
  on sender, subject, etc. should also be possible.

* Address books: build dialogs to integrate personal address books into
  mail recipient boxes, auto-completion, etc.  Use AJAX for this.

* Better UI presentation for delegated access to mailboxes.  (In IMAP this
  will be easy because of "other users namespace" support.)


 Miscellaneous "wish list" items
 -------------------------------

* Smart callback hook mechanism reducing traffic between citadel and the Database
  to do things like:
  * Alarms. Trigger popups etc. for users via the chat-keepalive
  * Chat. don't query the db on and on for this. 
  * Modify a list of rooms with new items for the logged in users to do things like:
    * Print the number of new mails onto the Webcit menu
    * change the roomlist / treeview according to new unread messages in the rooms

* bright new world to the tui too!
  * Calendar mechanism
  * vcards...

* more persistant css usage in webcit

* backtraces in the log in case of panics, etc.

* auto-login should move from compile to installtime.

* scheduled restarts there should be a way to notify all users 
   (whether via imap or webcit) that citadel is going to be unavailable.
   
* there should be a way to set a 'service unavailable because of' message, 
  for people connecting via webcit, so they can see this is a scheduled 
  downtime (so they don't take further actions like anoying the admin
  (you) via phone or restart citadel...

* there should be a way to keep citadel from starting while you're db recovering etc.
  (perhaps something like the pre-shutdown state would be cool, with a 
   message? so you tell it "sysadmin is reworking the database" as param
   to the server, it will close the db, but keep open the port, and 
   print out your message as error message. this should last until citserver
   receives a kill signal, and then terminates.)

* citserver should bypass some bdb errors and symptoms. it should remember 
  the actual berkeley db version in its state file, and in case of an up/downgrade
  moan this to the user / logfile. bdb upgrades should trigger a mail to aide.


