July 23, 2004
Progress: The .4A Milestone

The team hit the .4A milestone. It took an extra week and we got 90% of the way there, not 100%, but it was an impressive performance. The new planning and scheduling system is working, and we're on track for the rest of 0.4B (August) and 0.4 itself (October).

We've started the 0.5 planning process and there is a first draft from Product Management being reviewed by Engineering. Therefore we haven't yet ratified even the top-level goals or the schedule, but my hope is that the 0.5 calendar is something we at OSAF can use on a day-to-day basis in the first quarter of 2005.

At yesterday's staff meeting, we saw the first demo of email running inside Chandler's GUI. As well, the old calendar code we had has been re-done under CPIA (Chandler's GUI-builder framework), and we could see day, week, and month views, as well as a month-at-at-time thumbnail populated with real event data from the repository. Under the hood, it means we have end-to-end functionality integrating the diverse infrastructure components.

Now that we're starting to add application functionality at a more rapid pace (and this is something which will continue), I've asked the team to think about how it's going to impact out development process. It probably means more time spent stabilizing the code as we go so that the features work reliably. It may mean more attention to the visual appearance sooner rather than later, as it is still really raw, but this is to be determined. We also have to decide about whether to tackle or how long to defer certain engineering issues we have to face. A list is being drawn up.

As an added bonus, Morgen Sagen showed off a weekend hacking project he had built, a photo blog parcel for Chandler. It uses Chandler's repository as the back end, and Twisted's web server, which is now integrated into our code, to serve up the photos. The parcel itself is a Python servlet that manages the photos, their captions and the display. Not much integration into the chandler UI yet, but an impressive display of Chandler extensibility, given Morgen said he spent only a couple of hours on it.

Posted by mitch@osafoundation.org at July 23, 2004 07:54 AM

ok - here are some remarks and a question

faq #12 osaf
"we would be surprised if we finished Canoga before January 2004 or after January 2005 ." So no surprise as to January 2004. As to January 2005 I recommend to write Q1 2006.

Mitch Kapor's Weblog
"...but my hope is that the 0.5 calendar...". Hope is not a plan. I would like to see a plan in Q4 2004. A plan as to Chandler 1.0 to be delivered in Q1 2006.

OSCON 2004/A Developer's Tour of Chandler
"By the time you leave, you'll understand Items, Attributes, Kinds, Large Objects, Queries ..."
The OSAF glossary (http://wiki.osafoundation.org/twiki/bin/view/Glossary/AllGlossaryEntries) needs to be updated. Communication with external volunteers is not possible without a common language.

Mitch and Python
what happened to your endeavour to learn Python?

Posted by: DaniGro at July 26, 2004 01:19 PM

We will have a plan by September.

We'll look at updating the FAQ and glossary.

I learned a little Python and then got so busy I couldn't fdocus on it.

Posted by: Mtch Kapor at July 26, 2004 03:26 PM

Very interesting subject six months is the large term.

Posted by: Leon at August 1, 2004 08:39 AM