Here is a summary write-up of Thursday's Open Design Session on
Communications in Chandler.
http://wiki.osafoundation.org/bin/view/Journal/
EmailAsAVerbAndInvitations
Here are Katie's raw notes:
http://wiki.osafoundation.org/bin/view/Journal/OpenDesign20060127
Thursday was a user scenario exploration exercise to provide the
proper context for modeling invitations in 0.7:
+ How do invitations fit in the larger context of p2p communications
of all Chandler items, regardless of type (ie. tasks, notes, photos,
bookmarks, contacts, etc.)
+ How do invitations work in the context of Chandler sharing?
We accomplish this by briefly sketching out task-completion workflows
for the following types of "information-communications":
+ Scheduling and invitations
+ Wiki pages
+ Bugzilla
+ What do all these scenarios and workflows have in common?
+ What is the simplest model we can come up with so that we have a
unified approach that works for all modes of p2p communications?
We then highlighted how Sharing factors into these workflows.
+ ie. What happens if you receive an iMIP invitation for an event
you're already subscribed to read-write via Cosmo?
We compared 2 approaches to invitations workflows.
Finally, we proposed a phasing for implementation, trying to nail
down the bare minimum we have to do to get to plausible invitations
in 0.7
Next steps:
+ Review proposal at next Open Design Session
+ Plunge into interaction workflows for Scheduling and Invitations (a
la proposal submitted to the list).
Please feel free to comment on the write-up on the list or on the
wiki page directly:
+ Questions
+ Implementation ideas/issues
+ Feedback on workflow scenarios
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
