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 Goals to achieve during the 6.xx cycle
7 --------------------------------------
11 Status: the current implementation has both a 'Contacts' personal
12 folder and a 'Global Address Book' -- both which contain vCards. WebCit
13 can use them, and Kolab-compatible clients seem to be able to access them
16 We should integrate the address books more tightly into Citadel dialogs
17 such as recipient auto-completion, etc.
19 * Better UI presentation for delegated access to mailboxes. (In IMAP this
20 will be easy because of "other users namespace" support.)
22 * Additional LDAP integration
24 Status: the current implementation can populate an external LDAP directory
25 with Citadel user data.
29 Status: full functionlity is present in the current implementation, including
30 the ability to keep a personal calendar, send/receive invitations, manage
31 attendees, check free/busy times, etc. It is fully usable via WebCit
32 and also works with both Aethera and Kolab1 (vCalendar over IMAP for the
33 calendar store, and vCalendar over HTTPS for checking other users' free/busy
36 Doing CAP or WCAP seems less important now that vCalendar-over-IMAP seems
37 to be the emerging standard for open source groupware. We will monitor the
38 direction the community takes and follow along. Specifically, we will
39 probably implement whatever Mozilla Calendar ends up supporting.
41 There is also the possibility of implementing the WebDAV/XML schema exposed
42 by Exchange [ http://tinyurl.com/23bcn ] which would give us transparent
43 compatibility with Evolution and Entourage (but ironically, not with
46 * Move the WebCit presentation mode from frames to CSS.
51 * Configuration front ends (particularly in WebCit) for the new feature
52 that allows a shared room to have different names at each end of the link.
54 * Support recurring events in the calendar service. (These currently can
55 be submitted via external clients such as Aethera, but they aren't handled
56 properly by WebCit and they don't show up in freebusy.)
58 * RFC 2180 compliance -- do something predictable when more than one client
59 has a mailbox open and one tries to rename or delete it. The easiest thing
60 to do would be to simply deny the operation. This should probably be done
61 across the entire Citadel system rather than only in IMAP.
63 * Reminder: after the next non-beta version of the Citadel server is
64 released, email the IMAPcopy people for inclusion on their web site.
65 (Follow-up: we've done this twice now and received no answer.)
67 * Land a book deal with O'Reilly. :)
69 Items recently removed from TODO list
70 -------------------------------------
72 * WebCit support for HTTP transactions performed by Kolab1 clients
73 (The current WebCit build works with the Kolab1 klient, and with Aethera,
76 * RFC 2739 compliance (provide calendar free/busy URL's in vCard and LDAP)
77 (If anyone knows of clients that make use of this, let us know / test it)