Development Roadmap

This is subject to change at any time.

• Asterisk voicemail integration (completed in 7.22)

• Aggregation of mail from remote POP3 accounts (partially completed in 7.22)

• Authentication against an LDAP server without requiring PAM-LDAP

• Server-side tuning/bugfix as needed in order to support the needs of the Outlook client which is being implemented by a third party. (Completed; however, further improvements are possible.)

• Bring an XML parser into the build – probably Expat due to its small footprint. This will be needed for the next two items… (Completed.)

• Move the RSS feed reader into the server so that it doesn't require an external utility and can be configured from within Citadel. (Completed.)

• Implement enough of CalDAV to support deployed clients such as Sunbird and Evolution. (Why a partial implementation? Because CalDAV is so grotesquely overenginnered that a full implementation is practically impossible. We will focus on client compatibility.)

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

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

• 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.

• 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.

• easy management of external room access. there should be a gui way for room aliases.

• backcheck of aliases. citadel must check, if on save of the aliases there will be a race between other users / users aliases.

• citadel must check while saving the aliases, if the mail delivers yet to another person than the one just saving the aliases. if yes, it should do something like mail to foo@bar.org is already delivered to joeblow@bar.org

• uid to name in webcit / imap; citadel shouldn't display something like uid.room to other users, if they share it to others. it should do something like username/room where username should be a floor.

• webcit should be made more resistant to html injections, especialy the chat window.