Design Meeting Feb 6th 2006

Agenda

• Chandler project status review
  • Next actions for all the tenets
  • Design sessions this week - agenda and other prep
  • Next steps for target user discussions
  • Review of staging plan for 0.7
  • Performance targets, target user data
  • Schema upgrade (I want to discuss this briefly with you folks before replying to pje's email)
  • Interoperability plan (0.7, beyond)
• Cosmo & Scooby update
  • Update - what's changed about the release plan?
  • Scooby product strategy next steps
• Inviting "PIM/ical/calender" (probably need to define) users, outside the staff of OSAF to become a steering committee for Chandler and other products.

Notes

0.7 Chandler Planning:

• dogfood goals
  • 0.6 calendar target users
    • look into target groups
    • more formal interviews
    • berkeley folks - not ideal for calendar
    • explore katie's suggestion for target user group

• proposal about prioritization of existing feature requests and bugs
  • send to list - how we want to prioritize things - what the priorities are
  • proposal for tagging these - tues meeting

• target users will give us visibility to prioritize the "nice to haves"
• we assume we are moving forward with the "needs for dogfood" list

• send out to the list
• next steps for coordinating interviews

Inviting people to help drive product strategy

• input from outside
• open source and non-profit - identifying our constituency and allowing them to get involved with the product
• osaf as a non-profit is targeting a community that they are trying to serve and giving them a voice
• these people would be part of the community but are not represented today
• seeking out people to fill this role that we don't know about today
• how open to we make the process for selecting these people
• reaching out to the community
• start with one group of people
• keeping discussion on design list

Weekly design session

• Dashboard target user interview - Tues
  • Ted - couple
  • Esther - her and Mitch scenario
  • Task management
  • flush out usage scenarios
  • prep work - send out a list of questions and reminder

Target users and performance targets

• katie's proposal
  • perf tests for 0.7
  • continue with 0.6 tests
  • tests that push on repository

• dogfooding - calendar target - what should this be?
• dashboard - what should this be? mix target size? - 500 tasks and 500 calendar?
• do we count other details...
  • # of recurring events
  • # of a attachments
  • # of tasks

• goal - sample data set with size mix rather than different target for calendar
• pick scenarios for 0.7
• send our informal surveys and first pass at scenarios this week

Schema evolution

• PJE's questions to the dev list
• when will we be committing to keep user's data safe across upgrades?
• what are the different levels of this?
  • exp/imp but you can lose your data at any time
  • offering to upgrade but guaranteeing not corrupted - maybe unstable
  • your data is safe in Chandler
  • boundary - release vs continuous build
• how will be ensure that a previous version will upgrade from an older one? * what do we provide for parcel developers - provide them with a tool to upgrade?
• when an upgrade has to be reverted - what guarantees to we give the user that their data will be safe?
  • automatically create a backup

• user data is important - preferences and ui could get lost
• assume a back up stored
• katie will be replying to list
• talk to Philippe to see if he exports his data daily
• katie will drive this project with input from product/design when needed

Interoperability plan for 0.7 and 1.0

• next action: we need to have a more concrete proposal for 0.7 - spec this in more detail
• longer term alternative - big bucket of options (all the things we can be interoperable with)

Scooby/Cosmo

• Cosmo/Scooby - account creation page bug on Cosmo
• if you go to the server page and log in, you can't sign up for a new account
• Sheila will send an email to the design list

• Scooby/Cosmo can release together - the plan
• if it gets pushed 1 week ok
• 2 weeks fine
• more than that...it seems reasonable to have Scooby released anyhow
• current plan is meeting Tues/Wed - decide what we are going to do
• download and project are not the same thing - cosmo community
• bug review
• release to release data upgrade
• Mimi and Priscilla meeting with BCM about UI and goals for short release

Next actions

• 0.7 dogfood bugs/features email to the list (Sheila)
• setup meeting to discuss strategy for 0.6 target user interviews
• weekly summary to design list (Sheila)
• first pass at dashboard performance scenarios for 0.7
• survey to list about size of calendars
• spec out interoperability proposal for 0.7
• email to the design list about cosmo bug (creating new account when signed in)