Re: Update on Feature List

On Jul 25, 2007, at 9:39 AM, Philippe Bossut wrote:

> On the form first:
> - There are some inconsistencies in the presentation: sometimes the  
> whole first statement is bold, sometimes not, sometimes it  
> introduces an explanatory paragraph starting with semi colon,  
> sometimes it's part of the sentence. The feeling is that it reads  
> more like a marketing pamphlet than a feature list.
> -> Proposal: I can edit and clean that up, I'll keep the active  
> form you use to describe the features, using verbs to introduce the  
> feature and separate the short description from the paragraph with  
> a semi colon.
> - Statements are fuzzy: qualifiers like "smart", "easy" don't carry  
> any useful information since their alternative are not credible.  
> All they do is avoid describing what the feature really does.
> -> Proposal: I can edit that too, suppressing the fluffy qualifiers  
> and adding some meat to the description. You may want to proof read  
> after I'm done though since I'm not an English native speaker.

Hey Philippe. I've taken a pass at unifying the copy style. Please  
take another sweep at it if you have time.

>
> Unclear Titles
> - "Managing Information with the Desktop": This is confusing to new  
> comers I'm afraid. You certainly mean "Chandler the Desktop  
> Application" but, for anyone not familiar with OSAF's jargon, this  
> reads as if Chandler is providing some kind of desktop utilities  
> integrated within the OS desktop.
> -> Proposal: Change this to "Manage Information with the Desktop  
> Application"

Hmmm, We've been referring to the Chandler Desktop Application all  
over our web presences as just Chandler Desktop. I've changed it to:  
Manage Information with Chandler Desktop

> - "Interoperate": Again, this is OSAF's jargon. I'd prefer  
> "Compatible" as "compatibility" is what end users are really  
> looking for.
> -> Proposal: Change to "Compatible with other applications"

Yup. Changed it to: Compatibility

>> *The question of the day is: What's missing?*
>
> - Support for email: Email is only mentioned as a collaborative  
> tool. I think we should mention it as a way to get items into  
> Chandler in the "manage" section. This is a very important feature  
> I think.

I had the IMAP feature as a bullet under collaboration, but you're  
right, it doesn't fit in there. I've added it as a bullet under the  
first section:

Centralize information management in the Triage Table.
    * Create and edit notes, messages, tasks and events.
    * Smart Who and Date columns that display our best guess at the  
data most important to you.
    * Set up special Chandler IMAP folders to download messages into  
Chandler Desktop.

> - Stamping: Hard to explain in one paragraph but important since  
> it's so central to Chandler.

So stamping as a term is never mentioned in the user interface. Nor  
in any of the end-user documentation. I think it might be a good idea  
to think about using stamping officially as an end-user term or  
finding some other single term for describing this functionality.  
Currently, this is what I have for describing Stamping...which is  
consistent with how it's presented in the UI.

Move information seamlessly across application areas.
    * Address an event and send it as an invitation.
    * Take an email and add it to your Task list.
    * Schedule a task on your calendar.

> - Dashboard: The name is not mentioned (instead, we talk about a  
> "Triage Table"). Again, since it's so central to Chandler and right  
> up on the UI, we should mention the term and explain.

Yea, again Dashboard isn't actually in the UI, other than as the name  
of the All Collection. I think for now, we should stick with Triage  
Table to prevent confusion. We've talked a lot about revisiting the  
role of the Dashboard collection post-Preview (as in maybe it's not  
really a Dashboard)...I think that would be a good time for changing  
end-user terminology.

For now, Triage Table is a pretty explicit description of what the  
'Dashboard' does. So I'm okay with having that in the interim.

> -> Proposal: I can take a shot at adding those if you're OK with it.
>
> Cheers,
> - Philippe
>

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general