All Hands Feb. 14 2004

I. Bug Council. We've set up a Bug Council, which is our name for a common best practice in many places. Representatives from different groups meet on a regular basis at the end of a release process to make good decisions about the release. The group looks at the task list, triages and makes decisions about the release. It also is a mechanism for controlling change at the end of a release cycle and for load-balencing. There's often a policy of restricted changes to the source tree to reduce new bugs. Right now you should only change things that have a bug and for which you have obtained a review.

We'll do a post-mortem after the release to see how the Bug Council did and what changes might be helpful. Katie is chairing the Bug Council, Heikki is working his Bugzilla magic.

II. 0.3 Release. Code freeze milestone is coming on Tuesday. If things go well, Tuesday will mark the end of changes except needed bug fixes.

III. Standards. It's becoming clear that in some places we would adopt standards if they existed, but they don't. Calendar is an example the repository is another. With some effort OSAF could help the right things happen to increase interoperability. We might look into this.

Mitch also noted that Canoga release has a strong internal focus on the product design. Less focus on migrating from Outlook and Exchange, that comes afterwards. We need to have the product right first. But for adoption in the long term there are a lot of additional activities, including working with existing infrastructural organizations and migration issues.

IV.Andy Hertzfeld. Andy is writing a book about the early days of the Macintosh. There's a public website -- forlklore.org. When Andy's done with the book we'll see what it makes sense for Andy to do wrt Chandler. Hopefully we'll be at a point where we're ready to make good use of Andy's great skills.

-- MitchellBaker - 13 Feb 2004