We are continuing to figure out our email plan. Here was the last,
most complete summary (from Sheila) of the various 'Email - Bridging
the Gap' options we have available to us: http://
lists.osafoundation.org/pipermail/design/2006-August/005225.html
The two candidates at the top of our list is subscribing to IMAP
folders and implementing special Chandler headers so that Chandler
clients can communicate with each other directly, without forcing
users to pull down all the email in their Inbox.
Brian Kirsch has proposed a stop-gap measure for IMAP folders, which
is perhaps even better than allowing users to pull down arbitrary
IMAP folders.
When users fill out IMAP account information, we provide them with an
option to set up special "Chandler IMAP folders" that allow them to
not only add messages from their email clients into Chandler, but
also to specify whether they want the message to be added to the Task
list or Calendar. (All messages are automatically added to Mail.)
(The option should probably be checked by default, with a [Configure]
button that allows the user to choose which of the 3 folders they want.)
The 3 folders would be:
+ Chandler Mail: Messages in this folder are added to the Mail Dashboard
+ Chandler Tasks: Messages in this folder are added to the Task
Dashboard
+ Chander Calendar: Messages in this folder are added to the Calendar
Dashboard
This of course, doesn't allow users to add the same message to both
the Task list or Calendar. But it's a huge improvement to not being
able to specify a context at all.
For mock-ups, see: http://wiki.osafoundation.org/bin/view/Journal/
UnifiedDataInAndOutProposal#CommentsSection
Brian also raised the excellent question of: will our target users
have IMAP accounts? How widely deployed is IMAP amongst small
workgroups with scarce IT resources?
Thx,
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
