Hard to distinguish between CalDAV testers (external to OSAF) and Chandler users. We may want to sign them differently so that we can distinguish them. Or track the user agent.
How to measure retention? Use some time sample stats.
Use of tickets? Would be nice to measure.
Tradeoffs/realism for Preview
We are committed on some important features (Dashboard, new stamping...)
We should finish/polish those and fix bugs, and, very importantly, improve performance and reliability before adding too many new features
We will need to cut some more fancy features certainly and maintain discipline to the plan
We need to be a little more clear on what we cut for instance early on so that we don't waste anyone's energy on those
We are moving into a different phase of the project where focus will shift to stability/perf rather than features. We need to make that clear to the teams.
2007 conference planning
Let's be very conservative with who we send and when, especially between now and Preview (March 2007)
Next step: Philippe and Ted to create a very tigh plan (it's on the budget spreadsheet).
January sprint planning
Date : January 8th to 12th, 2007
Next step : list of activities to schedule (debug, perf work, sharing testing, other...)