Notes from the Management Committee Meeting of Feb. 3, 2004

1. Hiring. Long discussion of openings and resumes.

2. Management Committee Meetings being extended to 90 minutes, from 10:45 to 12:15, and ultimately to 2 hours once we figure out train schedules and such.

3. The 0.3 release.

Today is the feature freeze date. The repository group has hit feature freeze. May have work to do to support the apps group, of course.

The apps team is in good shape with respect to the high order goals -- CPIA is coming along, old code removed, started implementing design in line with the design team. At the next level of detail, we're probably not where we want to be for 0.3 quite yet. Close, but not quite there. And we want to get there; to have clean code with a coherent set of features that work. Not aiming at a great UI in 0.3, we're aiming for the basic UI.

Today the apps team will make a list of things it would like to get done to feel good about the 0.3 release. This requires making the Bugzilla data good as to the set of tasks we want to do for the 0.3 release. Important that we use Bugzilla to manage the rest of the 0.3 release. Heikki and maybe Katie will do some basic clean-up of the old bugs so we don't have to keep wading through them.

After we have a good list of things we might want to do before the 0.3 release we'll develop a process for deciding which are important enough to hold the release for. We'll have a Bug Council. Katie will chair it; Chao, Heikki and Andi will also be members. We'll also implement a "code buddy" system. Buddies may be involved with code review. But it's also an awareness issue, so if a problem develops we'll know where to look for issues.

Bug Council starts at 4pm or 4:15 today. The Bug Council will also decide about scheduling future meetings as well as the actual release date for 0.3.

Parameters for deciding on which bugs might make sense to include in the 0.3 release include:

• It should be a release we can be proud of
• Some extra credit stuff would be nice, except for the caterpiller UI. We probably won't hold the release to work on the caterpiller UI things, since we know that will change.

4. Non-code deliverables

We have some spedific technical documenation in mind sucyh as the "Busy Developer's Guide to the Repository", various design doc, and so on. In addition, Mitchell will make a proposal regarding non-code deliverables for the release as a whole. That is, our view of the goals of the release, what it accomplishes, what's intereating about it, etc. Chao has it the 0.3 planning document; we can turn this into what we are actually releasing, and then we can add the "what you can do with this piece."

-- MitchellBaker - 04 Feb 2004