Management Committee March 29 2004

I. Hiring. Brian Kirsh and David have started in the last two weeks. Discussion about future hiring.

2. "Services" Project planning for 0.4. Katie and Lisa have split up the thinking into areas that reflect their strengths. So Lisa is focusing on Notifications framework, agents, protocols, parcel loading. Katie is focusing on the interactions between CPIA UI specs, wxWidgets.

III. PyCon and related thinking.

A. Last week's Python Convention was the first time Chandler has gone out both in person and with a substantial body of code. It was a highly valuable experience. It was also very useful for Ted, Mitch and Jeffrey Harris to be together at PyCon and share their slightly different perspectives.

B. We also learned a lot about how Chandler appears to others, what's frustrating about it and so on. Ted put together a summary of what we've learned. Then we'll want to figure out what we should do, what investment to make in it, who owns the issue, and who might do the bulk of the implementation.

C. In 0.4 and 0.5 it will be time to do a little less coordination, and be a bit more open-source like and let people run with it. OSAF is doing well on the critical core pieces, but it doesn't scale. It's an organizational imperitive that we learn how to incorporate other participants with less central coordinators. Having a very smart technical person roaming over the code and seeing the opportunities is important for Chandler. The question is when it's time for this. We might also have a more explicit conversation regarding organizational goals. For example, how to balance a focus on community now with a focus on shipping Canoga asap to enable the community. We need to have a "there" there before developers can get involved.

D. Developing community is a highly strategic long term goal for sustainability. And a short term goal for shipping. There are some tradeoffs there, and what are they. For example, breaking out the repository isn't something we've thought about. Breaking out everything that isn't the PIM (repository, content model, notification manager, etc.) is something we have thought about. It's suitable for a narrower range of apps than one could otherwise use the repository for, but has a deeper set of capabilities. We'll want to give a lot of thought to this at the right time.

IV. 0.4 Planning

We will discuss at the All Hands a week from thursday . Mitch will work with each group throught the rest of the week to make a more final form. We will review at the next management committee meeting, and discuss at the All Hands a week from Thursday.

V. OSAF orientation for other KKIE folks in the building. Product, why we do it, community elements, etc. Mitchell to talk about what is open source and why people do it.

-- MitchellBaker - 02 Apr 2004