Platform Team Meeting 23 Jan 2007

Agenda

• Question: What would you like to ask Grant now before he's away for two weeks?
• Follow up on technical questions:
  • Tuning views to use pruning?
  • Strategy for using commit() in the app?
  • initialValue/defaultValue next steps? (aka 49 values on welcome note)
  • Further repository changes to support recurrence work?
  • Edit/Update/ConflictManagement/recurrence in EIM follow up?

Notes

Status

Katie

• Progress
  • Dev list summary: Dec 25 - Jan 7
  • Users list
  • Branding: domain quest
  • menu work (not yet committed)
  • wiki work (not yet completed)
• Plans
  • Performance targets
  • Dump and reload spec
  • Positioning statement, BrandingDeliverables^?
  • PreviewDomainModelOverview
  • test egg, commit menu fixes

Andi

• http://kumu.osafoundation.org/~vajda/logs.cgi

Bear

• Progress
  • Worked on do_test.sh rewrite (almost done) (Bug:7472)
  • Implemented Heikki's research into a simple debian package creation - need to finish verifying it (Bug:6159)
  • Bug:7247 (setuptools/configobj require download after clean)
  • Bug:4644 (move compilers from downloads to builds)
  • Bug:7503 (add docutils to package list)
• Plans
  • Finish 7472 and 6159 (my remaining P1's)
  • Implement script to stop/load/config/startup Cosmo Checkpoint on QASharing so tboxes are always testing latest instance
  • Finish script work to move last of hardhat distribution to standalone scripts (Bug:5578)

Morgen

• Progress
  • Tweaked new merge algorithm and checked it in
  • Wrote lots of test cases around new algorithm
  • Meetings:
    • Edit/Update
    • Conflict Resolution
    • Recurrence
    • Event-related EIM Record Types
    • Merge algorithm
  • Investigated bug 7712, restored collections becoming read-only
• Plan
  • Discuss deletions with pje, and how they affect the merge algoritm
  • Likewise, figure out how events get added to collections
  • Work with Jeffrey on event-related translation callbacks
  • Figure out APIs for Mail layer to access EIM-based sharing
  • Figure out APIs for UI to retrieve pending changes, apply them, or discard them