Cosmo UI Stickie Planning

Attending: Sheila, Priscilla, Matt, Mimi, Bobby, Ed, Ted, Jared, Katie, Bear

High Level Feature Workflows, Cosmo

From: List of workflows

• viewing items
• viewing collections
• edit items in a collection
• view in calendar
• view in table (min columns: task, who, subj, triage status, calendar)
• subscribing via Cosmo UI (dispensing other URLs, e.g. iCal)
• subscribing to generic CalDAV, RSS, Atom
• download as an ics file
• edit/update workflows (in band or mailto link)
• ? quick item entry (integrate Darshana's work)
  • bear could help out by making parsing library available in javascript
  • how would we keep it in sync? ted notes we should step back and think about maintaining library in two languages
• search
• preferences (tz, #hours, etc)
• browsing calendar
  • navigation
  • minical
• ? delete/remove (items/collections)
• see other people's stuff on Cosmo (same server)
  • may or may not have account
• viewing other people's Free/Busy
• ticket URL + password for shared collection access
• view/edit attributes...
  • event status (e.g. confirmed/tentative/fyi)
  • notes, title, location, datetime, recurrence, triage status
  • ? task stamp, email stamp (i.e. addressing fields), ticklers/alarms
• ? way to identify yourself (anonymous accounts)
• account signup
• account management
  • password
  • request tech support
  • request service status
• timezones

stickies

• not hardwired to events
  • serialization between cosmo and the browser (2)
  • client side data model (3)
  • stamping support in client side data model (2)
  • changing API on front end (2)
  • changing application to use new API (3)
• single item view (which can display different types of items) (2)
• multiple item view (which can display different types of items) (3)
• read only view (2)
• subscribing to collections (front end) (3)
  • there is a dependency to back end work
  • includes downloading ics file
• edit/update workflows (1)
• quick item entry (2)
• search table view (1)
  • back end dependency
• table work (3)
• pref panel (1)
• delete/remove (1)
• subscribe to other people's collections on cosmo (1)
• viewing other people's freebusy (1)
• url/password for shared collections -- login screen (1)
  • dependency on back end
• round trip email conf for new accounts (1)
• account mgmt (1)
• password change (1)

• work to merge the admin ui to the rest of the web ui

legend

• ? ==> may or may not make it in
• 1 stickie ==> 1 mythical man fortnight (2 weeks)

Desktop

• Dispense new type of URL
  • subscribe
  • publish
• optional password when we generate URL

Notes

• alarms will not go off in Cosmo (current plan)
  • why not? might not make sense in web ui, not critical feature
  • why? alarm moves item to the top of the "now" section -- might be a dependency per the implementation
  • if you can see that the alarm is set in web ui, will this be confusing to the end user? will they expect it to do something? perhaps use visual feedback to make it more clear that it is not an active feature? might feel like it is broken.
• there's another conversation about security big picture
• there's another conversation scoping out ACLs so it doesn't seem like one big overwhelming chunk of work
• delete vs remove might result in some tricky edge cases
  • use case: create an item on web client, delete it right away. If chandler happens to sync, that bogus item may end up in the dashboard
  • generally only supporting remove in web client
  • in the web case, delete vs remove are mutually exclusive. If you created it, its delete.
  • requiring menus would necessitate a bigger chunk of work
  • trash not on the table at the moment
• Jared has a bunch of non functional requirements that will result in many stickies