On Jul 14, 2006, at 2:19 PM, Mikeal Rogers wrote:
Remember as Mimi has said, in Chandler we want to think of email as a
verb not a noun. It is just one method of communicating with others.
Sure, we're thinking of email as just another mode of communication
in Chandler. But, in the long term we are going to be asking people
to stop using their current email clients and just use Chandler. If
we do this we either have to provide in Chandler the functionality
they may depend on in most modern email clients, or offer them
alternative features that can replace some of the features they
currently depend on in their mail clients.
Actually, this is an open point of discussion. There are those that
think that users are pretty attached to their existing email clients
and they aren't going to switch to Chandler for reading email. Also,
providing a rich experience for reading/writing/storing email is a
significant amount of work.
One of our key challenges is that since email is a major input into
the user's life, we need to be able to process those inputs. Even if
we did create our own email functionality inside of Chandler, I still
think we have to think about how to solve the problem of the user who
wants to continue to use her own email setup and use Chandler to
triage everything. We need that bridge from their email to the
Chandler ecosystem (and that's what this topic is all about! :-)
I need to spent more time thinking about this before I tackle
Sheila's email, but I wanted to respond to Mikeal's thoughts now :)
--> towns
-Mikeal
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
