[Design] What is the minimum feature set we can put up with in an early release of Chandler?

[Mike Taylor]

On Jul 14, 2006, at 6:37 PM, Ted Leung wrote:

> On Jul 14, 2006, at 3:08 PM, Katie Capps Parlante wrote:
>
>> I think we're all in agreement about the long run -- email is very 
>> important to the full vision of Chandler.
>
> Yes, yes, yes.   And RSS too, but don't get me started on that...

following Ted's lead I'll also defer the majority of my info-viewing 
feature list ...

>> The short run is the harder problem.
>>
>> The question I'm asking: Is there a bare bones feature set that would 
>> allow early adopters to use Chandler as an email client? What is that 
>> feature set?
>
> Ok, so after yesterday's discussion, I started to think about exactly 
> what the feature set would be for me.     When I "came in" this 
> morning, I watched all the operations that I did as I processed all 
> three of my IMAP accounts.
>
> Here are the actions that I actually did:
>
> * view messages by thread
> * delete a message

yes and yes

> * select  messages and use Mail Act-On! to execute an applescript that 
> examines each message and files it correctly by looking at 
> combinations of the mail headers - call this "filing"

I do this by using rules - currently have ~120 rules that move things 
around

> * click on a URL embedded in a browser
> * mark some read messages as unread for later re-processing - give me 
> a triage based workflow for this
> * reply to messages, including editing the to/cc lines because our 
> default list reply to is wrong, i did work on several replies 
> simultaneously.
> * send new e-mail messages (to remembered previous recipients)

all yes

> That's it.
>
> There are a few more actions which I do less frequently, which I 
> didn't do this morning:
> * paste text from the clipboard into a composition/reply window

also done by me frequently

> * verify/decrypt a PGP signed/encrypted message.   Bear and Heikki, I 
> blame you... - consider this one very optional

:) - I would gladly use Mail.app to compose my PGP mail for the testing 
phase

> * search for a particular message

I do this *a lot* - because of the search ability in Mail.app I now 
keep most of my messages in large folders whereas before I would have 
had sub-folders for everyone who has sent me mail from OSAF.

> * look at the raw source of a message - as a way of doing an 
> antiphishing check before deleting

same

> * work offline

I don't do this at all - I tend to view mail as a interrupt-driven 
process when I'm online :)

> * download an attachment

my mail server does this for me.

> * attach a file via a standard file dialog (I don't do drag and drop 
> attachments)

same here

> Well, now you have one person's list...

and one more :)

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/design/attachments/20060717/548a1f95/PGP.pgp