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 Kolab-compatible clients (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.
41 This needs some research, but I think it's technically going to be more
42 trouble than it's worth. -IO
48 * PLAIN and CRAM-MD5 authentication mechanisms
49 (Status: PLAIN is done; CRAM-MD5 will arrive a little later.)
51 * WebCit support for HTTP transactions performed by Kolab clients
52 (Status: DONE! The current WebCit build works with the KDE Kolab klient