Notes

Impromptu discussion with Brian K, Grant, Lisa, Katie, Mimi and Priscilla re: email goals for 0.7 and beyond. Now that Brian K will be working Cosmo, what is the plan for email and resourcing.

What is the ultimate goal for Email in Chandler 1.0?

• Chandler is primarily used for task management, calendaring and collaborative information and task management and experimental usage of managing Web 2.0 data types.
• Email is used to support these other workflow areas
• A means of "item sharing"
• Support scenarios around shared "mailing list management"
• For many users, Chandler will NOT completely replace your existing email client for reading and writing emails

• Ideas for better integration of Chandler with people's existing email clients
• Create an IMAP folder of flagged items which Chandler subscribes to
• Users can set rules to auto-stamp
• Chandler can detect ical attachments - promoted to events
• Chandler can detect file attachments, ie docs and images and promote them to first-class Chandler items
• Support drag and drop of individual mails into Chandler

• What are we going to interoperate with?
• IMAP
• Not POP

What workflows do we think we need to support in 1.0?

• Scanning email
• Email status - read/unread/draft/queued/error
• SPAM

• Communicating
• Reply (0.7)
• Reply All (0.7)
• Forward (0.7)
• Edit & Update (0.7) Hard

• Basic Reading and Writing
• HTML rendering (0.7)
• HTML editing
• Alternate layout (ie. detail view on the bottom, separate detail view window)
• Spelling and Grammar checking
• Attachments

• Managing massive amounts of email: Generic features needed for Email)
• Filters (rule builder)
• Email specific search
• Tags (0.7)

• Security SMIME
• Interop with servers
• Interop with other clients (What does this mean?)