As most of you know, the primary focus of the 0.6 release is a usable calendar. In support of that goal:
+ Ted is working on a design to refactor item collections, queries and notifications. Ted, John and others realized we needed to take a fresh look at this at the end of 0.5, as we were chasing down a series of related bugs.
+ We're continuing to work on improving performance. This will involve continued work on the repository, but will also require some work in other areas of the application. I'm working with Sheila to identify performance goals for 0.6.
We'd also like to spend some time improving the developer platform, in a few targeted areas.
+ Phillip is working on a proposal to define Chandler schemas with Python (instead of parcel xml). We expect this to have immediate benefit for our own productivity, as well as being important for external parcel developers.
+ Brian Kirsch and Ken Krugler have been working on a proposal for I18N support in Chandler. We'd like to start making progress on this in 0.6.
We may also tackle some issues with the content model, flattening of the parcel/package hierarchy, addressing for well known items, and logging improvements.
More details on all of these to come. For each topic we tackle in 0.6, expect to see a written spec/proposal sent to the dev list. I encourage everyone to read these proposals and offer comments. Also, we've been tracking this kind of project in several different places on the wiki -- I'm working on consolidating that for clarity. The idea would be to have one place you could go to find the current proposals, status, etc.
Cheers, Katie _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
