[Design] [Sum] Open Design Issues

[Mimi Yin]

Below is an attempt at a comprehensive list of all open design issues  
(issues that are already on the list or about to be on the list).

Please review to check if there are any issues that are waiting for a  
response from you. Also, please reply if you think of something we've  
missed.

SHARING / ECOSYSTEM WORKFLOWS
Reconciling Edit and Update workflows with Read-only sharing: http:// 
lists.osafoundation.org/pipermail/design/2006-July/004974.html
- Waiting for: response from Morgen

Supporting Casual Collaborators in collaborating on a single item via  
Scooby
- Next action for PPD: Send a proposal for use cases and workflows  
for the list
- Depends on 1.0 Ecosystem plan

Restoring shares by saving account information across instances of  
Chandler: http://lists.osafoundation.org/pipermail/design/2006-July/ 
005003.html
- Waiting for: Morgen to respond

Sharing with .Mac in Chandler and syncing Chandler to Scooby
- Next action for PPD: Sheila is going to put forward a proposal to  
not support 3rd party sharing in Scooby

Sharing account  field in the Manage share dialog: http:// 
lists.osafoundation.org/pipermail/design/2006-July/004968.html
- Next action for PPD: Propose short-term fix. Change the name of the  
Sharing account OOTB to Chandler Sharing Service: https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=6235
- Need to have a long-term discussion about: Ideal sharing workflows  
in the context of having unified workflows for getting data in and  
out of the Ecosystem.

Anonymous login: http://lists.osafoundation.org/pipermail/design/2006- 
July/004958.html
- Waiting for: More responses
- Next action for PPD: Summarize issues, concerns and proposals.
- I will wait for a bit more dialog then Sheila will send out a  
summary of the thread since we seem to be converging on a proposal.

Sharing URLs
- Waiting for: John to summarize issues to seed discussion on the list

'Remember me' feature for anonymous Scooby users
- Deferred from Scooby 0.3
- Depends on outcome of Anonymous login discussion

Mail-to link workflow: http://lists.osafoundation.org/pipermail/ 
design/2006-July/004966.html
- Waiting on: response for Engineering
- Next action for PPD: Turn it into a 0.3 spec with mockups


SCOOBY
Scooby UI layout
- Not expecting very many changes for 0.3
- Next action for PPD: Mimi and Priss will send out a context-setting  
email to explain current usability issues relating to layout and seed  
a discussion about possible solutions.

0.3 Specs
- http://lists.osafoundation.org/pipermail/design/2006-July/005070.html
- Waiting for dev feedback

COMMUNICATIONS / EMAIL
Stamping and Clusters: http://lists.osafoundation.org/pipermail/ 
design/2006-July/004936.html
- In holding pattern until Alpha 4 specs have been finalized
- Clusters and Threads are deferred until after Alpha 4

Email plan: How are we bridging the gap?  This is a continuation of  
the discussion we've been having on the list about the 1.0 Email  
Plan: http://lists.osafoundation.org/pipermail/design/2006-July/ 
004920.html and the proposed 1.0 Email Workflows: http:// 
lists.osafoundation.org/pipermail/design/2006-July/004923.html
- Next action for PPD: Sheila will send out a summary of the  
proposals we've discussed thus far to seed an engineering discussion.
- I think we should wait for a few more responses then send a summary  
later this week.

Chandler as an IMAP server, workflow issues: http:// 
lists.osafoundation.org/pipermail/design/2006-July/004935.html
- Waiting for: Travis looking into how to complete the workflow of  
getting email items into Chandler from your email client.

SIDEBAR
Should the Dashboard = All (mine AND not-mine)?
- In holding pattern until we solve the Dashboard and Overlays issues  
below
- Next action for PPD: Mimi to set context for workflow problems that  
arise as a result of limiting the Dashboard to just contain only  
'mine' items.

Dashboard and overlays: http://lists.osafoundation.org/pipermail/ 
design/2006-June/004818.html
- Next action for PPD: Prioritize and work into overall plan /  
development schedule

Mini-calendar - Preview pane interaction design: http:// 
wiki.osafoundation.org/bin/view/Journal/MiniCalPreviewReview20060621
- Next actions for PPD:
-- Ask Jeffrey about icon in the preview pane
-- Review spec with Jeffrey

CALENDAR
Calendar canvas improvements (new and improved event lozenges):  
http://lists.osafoundation.org/pipermail/design/2006-May/004737.html
- Scheduled for Alpha 4

DASHBOARD SPEC
Auto-triaging events added directly to the calendar canvas & Tweaking  
the Reminder/Calendar and Date columns: http:// 
lists.osafoundation.org/pipermail/design/2006-July/004926.html
- Next action for PPD: Mimi to update spec

GENERAL UI
Multiple window support: http://lists.osafoundation.org/pipermail/ 
design/2006-June/004837.html
- Next action for PPD: Prioritize and fit into plan / development  
schedule. Most likely being moved to post 1.0 timeframe.

Remove / Delete key: http://lists.osafoundation.org/pipermail/design/ 
2006-June/004854.html
- Next action for PPD: Sheila to summarize discussion and log  
proposal to make the DELETE key = Remove in user-defined collections  
as a part of dogfood feedback bug

Date/time picker in the Detail view: http://lists.osafoundation.org/ 
pipermail/design/2006-June/004901.html
- Waiting for: Responses from the list re: workflow questions.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060717/cfd337d8/attachment.htm