[Design] [Cosmo] Design Session: Review Preview Dashboard Proposal

[Mimi Yin]

We reviewed the wiki spec for Dashboard at: http:// 
wiki.osafoundation.org/Journal/ 
StrawpersonProposalForSimplifiedCosmoDashboard

The biggest areas of concern are around the complex behaviors we have  
in Chandler for auto-triaging of items and displaying recurring  
events  in the Dashboard.

The $852 question is: How closely does the Cosmo Dashboard need to  
follow the behaviors in the Chandler Dashboard?

The $2432 question is: Do we need to have a Dashboard in Cosmo for  
Preview? In other words, what are the tenets for Cosmo Preview?

    * Ted expressed concern over schedule, but was also worried about  
coming out with 'just another web calendar.'
    * Bobby wondered if answering this question would actually have  
any impact on the work that was done.
    * Mimi responded that there weren't really any big 'feature'  
additions for Calendar scheduled for Preview (Timezones and  
Styleguides are the only 2). So as long as we make sure that we keep  
the Calendar usable for the Casual Collaborator, any Dashboard work  
we get done is gravy and can be presented as Experimentally Usable or  
as a Plausible Promise for a usable Dashboard, post-Preview

NEXT ACTIONS

Bobby and Travis start a conversation on the Cosmo list about  
infrastructure work that's needed to support Stamping, Triage and the  
Dashboard.

PPD
Find a time with the Cosmo team to discuss Cosmo tenets. Perhaps at  
the next weekly Cosmo meeting?

Mimi
Flesh out phasing scenarios for Auto-triaging behavior in Cosmo
    * No auto-triaging in Cosmo, but provide a ways to ignore Cosmo  
TS settings in Chandler and have Chandler shoulder the burden of auto- 
triaging.
    * Auto-triaging items based on alarm and event date/time  
information being added to an item
    * Auto-triaging items as time passes

Alert Chandler developers re: Cosmo workflow issues that may require  
cooperation on the Chandler end.

Do another pass at the styleguide, incorporating new UI elements  
introduced by the Dashboard and Matthew's CSS tricks for lightening  
the number of images we need to download.

OPEN ISSUES
    * What to do about auto-triaging in Cosmo
    * How do we display Recurring events in the Dashboard? Just  
display a separate instance in some arbitrary range of time?
    * Do we want separate branding for Hosted Service versus SNARF?


On Feb 5, 2007, at 11:01 AM, Mimi Yin wrote:

> Tuesday Feb 6, 2007 2:30-4PM PST, Whoville.
>
> We will be reviewing the Preview Cosmo Dashboard proposal put forth  
> last month by PPD (modulo Cosmo 0.6 getting done beforehand).
>
> http://wiki.osafoundation.org/Journal/ 
> StrawpersonProposalForSimplifiedCosmoDashboard
>
> The goal of the session is to:
> 1. Review the proposal
> 2. Capture issues and questions
> 3. Get feedback to help PPD refine the proposal
>
> Thx!
>
> Mimi
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070206/38ce7407/attachment.html