[General] Draft of Vision Document is Live

[Mimi Yin]

Ted, Sheila and Katie: Here is the latest draft of the Vision  
Document: http://chandlerproject.org/Product/Vision for you to review.
Davor and Andre: It would be great to get feedback from you. In  
particular, what's confusing? Does the document feel balanced?  Are  
there areas we should emphasize more / less.

(Grammar and spelling feedback is always appreciated.)

Context:
Ted, Katie, Sheila and I have re-taken up work on the Vision Document  
for the past couple of months. The 4th draft is now available on the  
wiki. Some background on what we've been doing:

What are we trying to communicate with the Vision Document?
1. Explain our Design Approach and walk people through it at a high  
level from Target Users through Usage Scenario and Workflow Analysis  
to specific Design Solutions.

2. Define our Target Users

3. Define the problem we're trying to solve.

4. Explain how we're going about solving it.

4a. What are our Core Chandler Information Management Workflows:
1. Triage and Tickling
2. Stamping
3. Organizing with Collections
4. Post-Preview plans for Tagging and Clusters

4b. What are our Core Chandler Collaboration Workflows:
1. Edit/Update
2. Collaborating with Casual Collaborators via Chandler Hub
3. Sharing

5. Post-Preview commitment to extending Chandler.

Why do we need a Vision Document?
1. To explain OSAF's mission. Why are building Chandler? What do we  
think is it's value proposition.

2. To provide context for the Preview Release. What are we trying to  
accomplish? How should we be evaluated? (Our success should not be  
measured in terms of whether companies can replace their enterprise  
calendaring systems with Chandler.)

3. To explain how Chandler is unique as an open source project. Our  
approach to design. How we're innovating. Our commitment to  
interoperability and standards.

Still to come:
Linking descriptions of proposed workflow solutions to specific areas  
of the Get Started Guide so readers can see how our high level design  
approach manifests itself in the UI.

Katie is working on two more sections:
1. Project and community goals.
2. Interoperability.

Mimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/general/attachments/20070717/83ea628f/attachment.html