0.3 Planning

This area is for documenting the purpose and planned features of the 0.3 release.

The purpose of the 0.3 release is to get Chandler's base architecture and riskier innovative features in a reasonably stable state. 0.3 should be stable enough for us to then work at full speed on end-user features for the 0.4 release.

A rough outline of the path to 0.3 is in the ZeroPointThreeDevelopment page.

High-level Deliverables

• Base architecture framework in place:
  • Chandler Presentation and Interaction Architecture
  • Parcel loading
  • Repository enhancements including transactions and multi-threading support
  • Agent and Notification Framework
  • Content Model
  • Unit Tests Framework and real tests(!)
• Our initial �Caterpillar� UI
• Design docs for 0.4

Also see WhatIsZeroPointThree?

---

Categorized in more detail by work groups:

• Design Team Deliverables -- This list is referenced here
  • [Mimi] Caterpillar UI
  • [Brian] A set of proposals for design doc templates and organization, including:
    • what design artifacts to keep track of -- Filing Proposal
    • how to organize the documents -- Project Overview Table
    • a prototypical example of a design doc -- Canoga Sharing Design^?
  • [Brian -- map UI to content model] Caterpillar UI (including "enhancements") design and documentation (Bug:1111)
  • [Mitch] ItemCollection design
  • [Mimi] "Butterfly" UI Design including:
    • overall philosophy and motivation
    • sidebar design
    • View types (e.g. Today View)
    • Command-line text entry box specification
    • How are ItemCollection utilized?
    • View filtering/searching, navigation & other interactions
    • How UI Design relates and applies to Content Model
    • Marking up items
    • CPIA-reconciliation [extra-heavy apps team involvement]
  • [Brian] UsersAndGroupsDesign2004 (Bug:1112)
  • [Chao] Canoga Sharing Design^?
  • [Chao] Canoga Security Design [working w/repository team]
  • [Chao] Canoga Usage Patterns and how they relate to above
  • [Brian] End-user level Content-Model ChandlerSchemaGeneratedDocumentation (Bug:841)
  • [Chao] Tentative feature set of mail, calendar, contacts, tasks and notes
  • [Chao] First set of specific 0.4 deliverables to apps team [TBD]

• Apps Team Deliverables
  • Application functionality
    • Repository Viewer on CPIA
    • ZaoBao on CPIA, with an agent
      • Agent to update feeds
      • Dialog for agent edits [no]
    • Caterpillar UI, NavBar on CPIA
    • Content model
      • parcels checked in to cvs
      • xsl generated documentation
      • [first pass, more work needed e.g. in sync with query proposal]
  • Framework
    • Clean directory structure
      • all dead code will be removed
    • Logging infrastructure
    • Agent framework
    • Notification framework
    • CPIA
    • Parcel loading
  • Documentation
    • CPIA [high-level description, examples, code commented]
    • Notification framework
    • Agent framework
    • Parcel loading

• Repository Team Deliverables
  • Transactions
  • Thread-safety
  • Limited query for 0.3 CPIA
  • Storage of large text and binary objects
  • Notification for 0.3
  • New parcel support
  • Limited sharing
  • Tests
    • Performance
    • Item (parent/child, literal attribute)
    • Alias
    • Kind
    • Type
    • Bi-directional references
    • Persistent collections
  • Documentation
    • Data model and repository documentation
    • Tests documentation
  • Full-text indexing and querying (Lucene)

-- ChaoLam - 12 Aug 2003
-- DuckySherwood - 22 Sep 2003