Notes

• Tentative 0.6 Community Goals
  • Improved communication
    • more use of e-mail to make decisions
    • improve web site/ wiki information architecture
      • revise compelling vision section of main website
    • public proposals and reviews / feedback
    • group blog
  • Community improvement of the pycon sprint parcels
  • At the end of 0.6 it should be possible
    • For third party developers to create their own parcels without needing an OSAF person to help them
    • To engage people in the various linux distributions to get their help in packaging Chandler according to the rules of their distribution
    • For third party developers to create plugins for the import/export framework
  • Preparation for (and attendance at, depending on schedule) OSCON 2005

• Tentative 0.6 Developer Platform Goals
  • Improve documentation a lot
    • Centralize / organize existing and new specs
    • System architecture document
    • CPIA architecture document
    • Document import/export framework
  • remove parcel.xml
  • flatten parcel hierarchy
  • resolve circular dependencies
  • Improve Content model (since content model is part of the API)
  • Clean up contacts to the point where we can think of linking other items to contacts
  • attribute editors
  • preference panel support
  • web server support

• Notes from my ItemCollection phone call with Morgen
  • We talked about a Spike like evented set model
  • The key requirement for sharing is to share an extent (explicit specification of the elements of the set rather than a query) and the ability to be notifed when items enter/leave (Q: do we need update notifications as well?)
  • What's the essential difference between ItemCollection and Query? Between ItemCollection and Set?
  • Morgen thinks that we ought to decouple sorting from queries/query results
  • Many other ideas being discussed, like spheres, or quarantined items should not be a problem to handle. Most of these end up being tests on attributes.
  • Full compositionality (operations apply to results of other operations, and notifications traverse union/intersect/difference, etc) is important for making ItemCollections work properly.