[Design] [Sum] June 4 - 10

[Sheila Mooney]

Mimi sent out a Cosmo Proposal to defer Time zone work to Post-Preview
http://lists.osafoundation.org/pipermail/design/2007-June/007352.html
+ We feel that what we have now is consistent with the desktop and  
good enough for Preview. In an effort to get to feature freeze  
faster, and reduce any additional design work to close on the  
details, Mimi proposed we just move all the timezone work to Post- 
Preview.
+ At the time she sent this, we decided to keep them in the task list  
but since then punted all of these bugs.
+ If some issues come up in the course of testing and dogfooding, we  
can move them back into 0.7.

Jeffrey sent out a notice that the Cosmo team (and Jeffrey) will be  
meeting specifically to discuss how we are going to handle Dashboard  
and Recurrence in the Web UI
http://lists.osafoundation.org/pipermail/design/2007-June/007353.html
+ In preparation for this meeting, Bobby had sketched out algorithms  
for how things appear in the NOW, LATER and DONE sections as well as  
a list of open questions to be discussed.  http://chandlerproject.org/ 
Journal/TheAlgorithm

Bobby replied to an earlier thread about the Cosmo - Revised Sign up  
Workflow
http://lists.osafoundation.org/pipermail/design/2007-June/007362.html
+ Bobby added that when users download a server build, they should  
see Chandler Server in the sign-up dialog instead of Chandler Hub.
+ Mimi confirmed this.

There were some responses to Mimi's thread on the Cosmo Update on  
Detail View
http://lists.osafoundation.org/pipermail/design/2007-June/007363.html
+ Matthew had some comments re: the verbiage for stamping items. For  
example "add to task list" doesn't accurately reflect the action  
since there is no task list view in the Web UI and this might be  
confusing for users.
+ As Jeffrey pointed out, the actions as Mimi described them reflect  
the data model more closely.
+ In the end Mimi suggested we use "Mark as a Task" which seemed to  
be the winner.

Bear started a thread on Upgrade notification dialog trigger -  
clarifying
http://lists.osafoundation.org/pipermail/design/2007-June/007372.html
+ He explained that the upgrade notification dialog will be triggered  
in the following use case - Does a repository from a previous  
Chandler version exist and we are creating a new repository?
+ He wanted to confirm that there were no other use cases we wanted  
to support and that in most cases people will be upgrading from  
0.7alpha4.
+ After some further dialog Bear clarified that we are specifically  
looking for the presence of a profile directory from a version that  
isn't the current version (the user is downloading).

Jeffrey sent out a summary of the Cosmo discussions that occurred  
around triage and recurrence in the web ui table view
http://lists.osafoundation.org/pipermail/design/2007-June/007376.html
+ Jeffrey described some of the differences in the way we handling  
triaging recurring events in the web ui vs in the desktop.
+ On the desktop we have a clear idea of when occurrences were  
created or imported and we can easily figure out when to triage stuff  
into the NOW section. We have decided to have the NOW section show  
occurrences only in a few cases.
	+ When a web UI or desktop user triaged the occurrence to NOW already
	+ If the table happens to be shown when an occurrence is in progress
	+ If a future occurrence has non-triage changes like a modification  
ie: title changed
+ This means that in most cases we will show a LATER occurrence but  
not a NOW version.

Mimi sent out an iteration of all the Cosmo Custom Buttons and Icons  
for Matthew
http://lists.osafoundation.org/pipermail/design/2007-June/007378.html

Vera, one of our Google Summer of Code interns sent out a Design  
proposal for progress reporting in chandler for your evaluation
http://lists.osafoundation.org/pipermail/design/2007-June/007381.html
+ Vera's project is to provide Chandler's users with an option to  
overview their tasks in a compressed manner, to track their progress,  
and to be able to report on it with minimal effort.
+ Vera outlined her proposal and wanted some feedback on whether or  
not this was a good set of goals to start with.
+ Some highlights...
	+ The first report would only be for the previous weeks activities
	+ We would create a report using the Quick Item Entry field
	+ We would report on the currently selected collection
	+ We would group items by their triage status
+ Vera also included a bunch of links to wiki pages with more detail  
and background.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070701/9e7d4a03/attachment.html