Design Meeting Notes - Jan 30th, 2005

Agenda

• Status update - how are we doing on goals
• Design discussion Tuesday - goals
• Usability studies, budget - should we be more formal with this?
• Should we have a meeting about where we are at with 0.7 planning and tenets? Staff meeeting?
• Better AV support for design sessions...camera...whiteboard.
• What email/sharing support do we need for our Plausible Dashboard target user?

Notes

Chandler 0.7

• email discussion II scheduled for Tues 01/31
  • sheila will summarize the discussion in an email attached with mimi's notes

• official statement about our email strategy for 1.0
  • mention in presentation to team at staff meeting

• priscilla dogfooding feedback
  • review this and decide what documentation and communications are necessary
  • send out to the list

• next steps:
  • timezone documented in a spec - talk to Grant

• morgen
  • will document synching proposal and send to the list
  • setup followup meeting with him to discuss

• target user next steps
  • thursday calendar user meeting
  • next tues, dashboard target user discussion

• scheduling
  • na: meeting tomorrow
  • put out first draft of proposal

• dashboard
  • na: tackle spec for the dashboard
  • need more design time
  • design session next week- return to dashboard to have target user discussion
  • communications functionality to support plausible dashboard (terminology)
  • flavor of sections

• dogfood calendar
  • schedule a discussion for target user - thurs
  • review all bugzilla items and feedback from users

• specs this week
  • timezones - ready to spec - talk to Grant
  • markup bar - reid review - scheudle this
  • context menus - needs more brainstorming
  • detail view - meeting with bryan on wed @9:30am

• to discuss...
• what should the goal be for CALDAV interop?
• i18n open bugs - how do we triage bugs?
• instrumentation framework - how does this relate to sharing
• accessibility plan - do not triage any bugs - is this a priority - we don't know yet
• schema evolution - driving from development but might need design attention
• domain model - na: conversation between Ted and Mimi
  • ted is to be the owner...needs all the info to drive that
  • support ted - give him the info he needs to be able to do that

• front load synching and free-busy work to understand if we have additional needs for Cosmo
• mimi will send a short proposal for sandbox for experimental ui to the design list

Information Designer

• swat team come up with different responsibilities and job descriptions
• brainstorm scenarios of how people find information
  • ted will sync up with Mimi/Priscilla
  • figure out how to do this...big group, small group etc
  • deb richardson

Cosmo and Scooby

• na priscilla - write up something for cosmo on list re the screen walkthrough
  • goal last week was to walk-through screens

• Scooby in process...working with Matt on design requirements

Other Stuff

*eTech blurb review (done)

• iSummit, CHI paper are done
  • iSummit mar 23-27
  • BAY CHI mar 14

• Usability studies, budget - should we be more formal with this?
  • given a token is not unreasonable - swag
  • FLOSS sprint

• update on 0.7 planning and design
  • sheila will do this at staff meeting

• Need better AV support for design sessions...camera...whiteboard
  • bring in iSight
  • experiment with iBeam to see if this is something that will work for us

• html stickie doc - matt fixed some bugs (ie)
  • sheila will update the 1.0 stickie plan
  • working stickie plan for scooby