[Design] Design Session @ 1PM in Shambhala

[Mimi Yin]

I am hijacking my own agenda. After a number of hallway discussions,  
I'm realizing that before diving into interaction workflows (ie. who  
clicks on what where in the UI), we need to back up a bit and put  
invitations and scheduling in context:

+ How does invitations and scheduling interact with more general  
notions of "communicating" information in and out of Chandler?
+ What are existing models for invitations? Email, Outlook/Exchange...
+ What are existing models for communicating information items?  
Email, Shared public folders...

(When I say models: I'm referring to task-completion workflows as  
opposed to interaction workflows: ie. What are the conceptual steps  
to sending out an invitation regardless of what "technology" I'm  
using: computer, paper, carrier pigeons ;o)

Proposed agenda:

5 minutes: High-level goals of the discussion
5-10 minutes: Sketch out how we do invitations today at OSAF
5-10 minutes: Sketch out how we communicate information items today  
at OSAF
15-20 minutes: Long-term proposal for generic Chandler communication  
of individual information items + specific emphasis on how  
invitations fit into that generic proposal
15 minutes: Next steps in 0.7

If we get through this agenda, next week we will focus on specific  
interaction workflows.

Note: Jeffrey will be facilitating the meeting.

Mimi


On Jan 23, 2006, at 5:11 PM, Mimi Yin wrote:

> Scheduling and Invitation Workflows in 0.7
>
> http://lists.osafoundation.org/pipermail/design/2005-December/ 
> 003697.html
>
> Agenda:
> Sketch out proposals posted to the list.
> Collect input and feedback on proposals.
> Get down a list of open issues.
> The goal is to come up with a solid proposal by the end of next week.
>
> Mimi
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design