Hi Mimi,

This is a pretty good first shot. Here's some comments and proposals for improvements. I'm ready to do it if you're OK with them.

Mimi Yin wrote:
I have done a pass at the Feature List: http://chandlerproject.org/Planning/Features
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.

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" - "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"


*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. - Stamping: Hard to explain in one paragraph but important since it's so central to Chandler. - 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.
-> 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

Reply via email to