All Hands Meeting; Dec. 18 2003

I. People

A. Siobhan O'Mahoney from Harvard Business School is visiting

B. Chris is our newest employee. IT generalist, desktop support specialist

C. Brian is moving from his data model role to product management, as of Jan. 1

D. Morgen moving from the builds into the app groups, will start with unit tests on parcel loading and go from there. We'll hire someone to pick up Morgens great work in the build world

E. Lots of people away in the next two weeks

F. Next All Hands meeting is on Jan. 6. There will be demos.

II. Summaries from working group coordinators: activities, accomplishments and next steps. This will be a regular feature at All Hands Meetings. We also agreed that each group will demo something at each milestone.

A. Design Working Group (from Chao)

1. Two big groups for deliverables from the Design Group

• a. High-level picture of what Canoga is -- directions, big features. (Butterfly UI is code name for Canoga UI. Hope to have a good idea of this around mid-February.)
• b. concrete deliverables, working with apps group on a milestone and dot release basis. (Caterpillar UI is the code name for the UI in the 0.3 release.)

2. 0.3 deliverables

• Caterpillar and butterfly UI
• Users and groups framework
• Document on sharing framework
• Canoga security design, on a broader level, based on user names and passwords, which is more manageable
• content model (used to be called PIM schema) from the end user perspective
• use patterns

B. Apps Working Group (from Katie)

1. Currently:

• Working out the catepillar UI with the design team and internally.
• Working out ZaoBao^? UI to drive agent and notification issues. Have a good idea of the target and schedule.
• Notification framework is checked in and starting to be used
• Event handling in CPIA and basic blocks are starting to be written
• Content model from design team -- making it live in the code.

2. next milestone

• focused a great deal on unit tests for the frameworks.
• Group hopes to demo CPIA architecture in use, say for repository viewer; some basic blocks working at the next milesonte (Jan 6.)

3. Inter-group issues

• notifications, queries -- need talk with repository group
• catepillar UI, work with design group
• data model issues -- work with repository team.

C. Repository Group (from Heikki)

1. Recent new things available in the repository include XPATH, large text and binary objects, XML tool processing.

2. Ted working on tests; should have a complete test suite for the repository by the end of 0.3.

3. Status Manager and Bugzilla components now match for repository stuff; soon will make other things match.

4. Planning to hire a QA engineer who will start with the repository work.

5. Hoping to migrate Chandler to wxWindows 2.5 in the first milestone of the 0.4 release. We need this to figure out what we actually need in wxWindows. This is Heikki's project.

6. Heikki added two new milestones to the 0.3 planning process, because there is now an extra month before the 0.3 milestone.

D. Community Group (form Mitchell)

1. Not a lot of activity this week. Waiting to let the working groups get going.

2. Working on the Office Hour schedules, Pieter will contact WG coordinators to finalize

3. Investigating the feasibility of a Python sprint at PyCon

4. Upcoming topics:

• StarterProjects pages
• Community Plan -- goals for the 0.4 release.

III. Wiki redesign

1. We have a redesign

2. Ducky has worked out a schema for moving pages and mapping new to old, this was a big chunk of work

3. Jurgen is working on a script to move the pages and the links. It's almost done, some rough edges where a link didn't get translated. We need to decide when it's done and that future problems will be fixed by hand. Then Jurgen needs 3 or 4 hours to take the wiki down and get the new one going. Mitch urged we do this as fast as possible and asked Jurgen to set a date for the switch by the end of the Thursday the 18th.

4. This will also bring the new Project Hierarchy into the wiki, helping rationalize communications structure with the Status Manager and Bugzilla. Then the working groups can work on updating the actual content.

IV Working Groups. Mitch noted that the working group structure seems to be working. Coordinators also track inter-group issues, which can be worked at the Mangement Committee if not solved before. We expect this structure to continue to develop and evolve. We'll be doing more hiring, and we'll need new mechanisms as people start using the code and giving feedback. This leads to some new jobs opening up, job descriptions will happen shortly.

-- MitchellBaker - 18 Dec 2003