1 This isn't an official list of plans. It's basically just some notes on where
2 we want to be going. It's something to consult when sitting down to write
3 some code and deciding what to work on.
6 Recent goals achieved (in tree, not necessarily published yet)
7 --------------------------------------------------------------
9 * GroupDAV and "webcal" (icalendar over dav) support
10 * Updated schema for publishing Citadel address book data into an
11 external LDAP directory
12 * Internationalization (WebCit is now available in several languages.)
13 * Per-user auto-handling of inbound mail. (Sieve + rules editor)
16 Goals to achieve during the 7.xx cycle
17 --------------------------------------
19 * CalDAV support (Eventually. Since both the protocol itself and the people
20 designing it are incredibly ugly, it keeps changing, and implementations
21 keep breaking. When the spec is finalized, we will implement enough of
22 CalDAV to provide compatibility with any major client packages which use
25 * Integration of CMS and social software features (more on this later).
27 * Further internationalization (for example, in the citserver).
29 * Address books: build dialogs to integrate personal address books into
30 mail recipient boxes, auto-completion, etc. Use AJAX for this.
32 * Better UI presentation for delegated access to mailboxes. (In IMAP this
33 will be easy because of "other users namespace" support.)
36 Miscellaneous "wish list" items
37 -------------------------------
39 * Smart callback hook mechanism reducing traffic between citadel and the Database
41 * Alarms. Trigger popups etc. for users via the chat-keepalive
42 * Chat. don't query the db on and on for this.
43 * Modify a list of rooms with new items for the logged in users to do things like:
44 * Print the number of new mails onto the Webcit menu
45 * change the roomlist / treeview according to new unread messages in the rooms
47 * bright new world to the tui too!
51 * more persistant css usage in webcit
53 * backtraces in the log in case of panics, etc.
55 * auto-login should move from compile to installtime.
57 * scheduled restarts there should be a way to notify all users
58 (whether via imap or webcit) that citadel is going to be unavailable.
60 * there should be a way to set a 'service unavailable because of' message,
61 for people connecting via webcit, so they can see this is a scheduled
62 downtime (so they don't take further actions like anoying the admin
63 (you) via phone or restart citadel...
65 * there should be a way to keep citadel from starting while you're db recovering etc.
66 (perhaps something like the pre-shutdown state would be cool, with a
67 message? so you tell it "sysadmin is reworking the database" as param
68 to the server, it will close the db, but keep open the port, and
69 print out your message as error message. this should last until citserver
70 receives a kill signal, and then terminates.)
72 * citserver should bypass some bdb errors and symptoms. it should remember
73 the actual berkeley db version in its state file, and in case of an up/downgrade
74 moan this to the user / logfile. bdb upgrades should trigger a mail to aide.
76 * easy management of external room access. there should be a gui way for room aliases.
78 * backcheck of aliases. citadel must check, if on save of the aliases there will be a
79 race between other users / users aliases.
80 -> citadel must check while saving the aliases, if the mail delivers yet to another
81 person than the one just saving the aliases. if yes, it should do something like
82 mail to foo@bar.org is already delivered to joeblow@bar.org
84 * uid to name in webcit / imap; citadel shouldn't display something like uid.room
85 to other users, if they share it to others. it should do something like username/room
86 where username should be a floor.
88 * webcit should be made more resistant to html injections, especialy the chat window.