Overall Goals and Strategy

A presentation on the 0.6 vision and goals: ZeroPointSixVision.ppt

Our vision for 0.6 Chandler is to have a Usable Calendar. What does a Usable Calendar mean?

Calendar

We want personal, group and small workgroup calendaring for 0.6. It's not social calendaring, nor is it a public events calendar. A calendar may be either an individual's calendar or a group calendar such as a shared office calendar. An individual can share multiple calendars with different sets of sharees.

Sharing is an essential part of having a usable calendar application today. Our vision of sharing for 0.6 is very simple: calendars are published to URLs and anybody who gets the URL can share that calendar. There's no state management or management of people who are sharing the calendar. The person who originally shared the calendar can later delete it, but that's the only state transition.

We may make simplifying choices to achieve these goals early. We need to look for ways to preclude problems.

How does this relate to an ecosystem, or, how is this ecocentric? This approach is naturally interoperable with non-Chandler agents in the ecosystem. We realize that we're giving up some application-centric benefits such as Chandler-specific features, but we think this is more agile and provides interoperability, adoption and spread benefits.

Usable

We have a list of Chandler application-level bugs and tasks already identified ("Cleanup and Polishing") and this is the list of features needed to make the GUI usable. We also have a list of work required in the underlying layers -- from repository performance to handling multiple changes to a single shared item.

The focus on Chandler progress (rather than on a webui) is because the most important part of the ecosystem, for now, is our Chandler client, and it has to work smoothly and feel right to the user. The server is going to need to implement some features (like tickets) that make the client work smoothly.

What else are we doing?

The only other work in progress can be characterized as developer productivity work, developer platform and i18n, with a little bit of email progress -- work we need to do to stay afloat and avoid blocking entirely on our longer term visions.