All Hands Meeting of April 15 2004

I. Discussion of Working Group organization

We've split the apps group into two. John, Jed, Morgen and David remain in the Apps Group, which Katie continues to coordinate. The Design Group, QA and Release Group and Community Group continue as before. We have a new "Services Group" with Lisa as the coordinator. Ted and Morgen and Stuart and Brian K work with this group. One can think of it as the "Middleware" layer, between the Repository and the Apps Group. Working groups are related to a management structure, and some people participate in 2 working groups, and there are lots of fuzzy edges to the working groups, which reflects the way we work.

II. Discussion of Services Group plans can be found at: http://wiki.osafoundation.org/twiki/bin/view/Chandler/ServicesWorkingGroup

Services are utilities above the repository level that don't have a "visual" or user interface level, including protocols and non-visual utilities. Current focus is:

• content model, email object schema
• Sharing -- still working on the desing
• Parcel loading -- getting its data model into the repository
• schedule manager and notification manager.

III. Sharing will proceed on parallel paths -- some Andi will do, some the Services Group will do. Mitch didn't want to hold up implementation and things Andi is ready to do because we don't have the protocol and entire big picture of a Repository Access Protocol figured out. So we'll do both, coordinate, look for commonalities.

IV. Andi

Trying to get access control for a user now. For 1.0, we're not going to try to do the full spectrum of multi-user access control. "Sharing" assumes distinct repositories with some overlap of data that needs to be synchronized. "Replication" means the whole repository is a functional duplicate of another repository. Andi working on the nitty-gritty of two repositories talking to each other; not the protocol, or security, etc. Not so much questions related to two Chandlers discovering each other, connecting to each other, etc.

V. Future discussions. QA/Release Group and Community Group. We'll also start doing demos about what's in the milestones again. This may start with a discussion of the new build system, which is a major effort.

VI. 0.4 Schedule

Currently, we've scheduled milestones for a number of tasks. Now we need to learn more about how hard these tasks are, then we can do some more scheduling. We know that we don't want to go beyond the end of September. If things can't be done by then we'll need to figure out what needs to be cut. We may also do some milestones before then with a more rigorous QA and so on.

As to the timing, 0.4 will take longer than originally planned because we've added new requirements:

• All major systems for the repository should be in place at the end of 0.4; after that it will be stability, polishing and productizing work for the repository
• Added authentication and crypto to 0.4

-- EstherSun - 15 Apr 2004