Kibble Planning Agenda

1. Review reorganized ZeroPointFivePlanning
2. Discuss methodology to go about planning and scoping out Kibble further (see strawman proposal below)
3. If we are basically in agreement with strawman proposal, discuss high-level goal candidates for 0.6 and 0.7
4. Time permitting, discuss and triage list of smaller-than-sticky size features that Chao would like clarification

• Strawman Kibble planning proposal:
  • Plan 0.6 and 0.7 the same way we are planning 0.5, except at a coarser grain (i.e. more features that are as yet not designed sufficiently). To elaborate:
    • Figure out high-level goals for 0.6 and 0.7 (0.5 was calendar dog food)
    • Come up with features/workflows that support identified high-level goals and categorized by such goals
    • MimiYin: Where applicable, come up with lightweight vs. heavyweight alternative features that can support high-level goals. Discuss pros and cons of alternatives and decide on a path
    • Match these features/workflows back to sticky board. Refactor features & sticky board as necessary
      • Figure out if there are "lightweight" versions of features to fit schedule
    • Identify features/workflows that are ill-designed or need more input from engineering. Prioritize and make time to further design these features
    • Iterate as design, architecture and product matures over the milestones

• Candidates for 0.6 and 0.7 high-level goals:
  • Triage workflow
  • Search
  • Dog food email (can this be divided into two parts?)
    • Processing & Organizing email:
      • Rules & Filters
      • Spam & Junk management
      • clusters (ad-hoc collections) and email threading
    • Composing and Viewing email:
      • Rich text support (rendering & editing)
      • Spell-checking
      • multiple account support
    • Other
      • Polish current features
      • POP mail
      • IMAP folder reconciliation
  • Event Scheduling (whatever doesn't make it to 0.5)
    • Free/busy roll up
    • Sending and updating invitation
    • Invitation state management
  • Interoperability
    • WebDAV and CalDAV interoperability
    • Data import and PDA sync
  • We should also decide which of the above we want to do very well vs. just satisfactorily for any particular release (e.g. for 0.5 we are doing basic calendaring very well, email just incrementally)
  • What about (what are the right next steps?):
    • Developer Dog food?
    • Undo framework?
    • i18n?
  • Questions/Open Issues:
    • What does a CalDAV client entail?

• List of smaller-than sticky-sized features for Triage
  • Suggested process
    • Go through list of features below: Can we easily say it's in vs. deferred?
    • If not, what is the next step/decision on this feature (if any)? e.g.
      • figure out how to breakdown the feature further
      • figure out a lightweight version of this feature
    • List is not comprehensive, just what is on my mind currently
  • List of features:
    • Summary view
      • Fisheye
      • iconic choice widgets
      • inline text editing
    • Sidebar
      • Trays
    • Universal text entry
    • Tabbed views
      • Dnd items between tabs
      • Reorder tabs
    • Visual effects
      • fade in/out
      • animation
    • Dashboard
      • Sections in summary table
      • two phase: mark & purge
      • triage: defer & tickle
    • Email
      • Rich text editing
      • IMAP folder reconciliation
    • Calendaring
      • Invitation state management
    • Archiving
    • mark as needs reply
    • See also section (Labeling workflow)

• What's not on the sticky board that we need to consider:
  • Current Status: just starting to compile
  • Lightweight contact management. e.g.
    • Email addressing and auto-completion
    • Reconciling email address & WebDAV account name

-- ChaoLam - 02 Oct 2004