Operations Group Meeting Notes - August 22nd 2006
Staffing/Personnel
- Ted dev manager of Cosmo (congrats!), change will be announced on the list
- Cosmo hiring : moving forward on the 2 recs, great lead on WebUI, still interviewing on Server
- Product strategy : Katie to get back on the description and get that moving again
- New hire at KEI on website design and graphic design, will work on LPFI stuff 50% of his time, could be available for OSAF web site stuff
Sprint update
- Lots of things got addressed, good ground work to build a roadmap, much less tension than expected, went really well altogether
- Sharing meeting was very successful, PJE's proposal the basis of the new data model common to Cosmo and Chandler
- Clarification on the meaning of "beta", i.e. "beta as usable outside of OSAF" not "beta as feature complete". Katie, Ted and Sheila to clarify.
Interop
- Mikeal as interop coordinator
- What is the right forum for interop discussions/planning? May be use everyone? Philippe to decide with Mikeal.
Markku as new committer
- Who's thee keeper of the CLAs? Sheila will take it over. Need a Wiki page to list the CLA signed ons. [We changed this decision after the fact: Pieter will be responsible for collecting CLAs and tracking them on the Wiki, and will hand the physical documents to KEI accounting for safekeeping -- KCP]
- Process : Ted summarized his recent email on the subject
Kiko calendar discussion
- Was mentioned but didn't have any impact on people here
Risk, priorities discussion
If getting people outside of OSAF using Chandler projects by March 2007 is the goal, what are the risks/obstacles to achieving that goal?
- Feature not competitive, miss target user entirely
- Missing mobile strategy
- -> Reactivate mobile strategy (Katie)
- Performance : Desktop, background sync too heavy
- -> Speed up restore
- -> Tackle memory footprint
- -> Goal setting, time allocated (Heikki, Philippe, Sheila)
- Interop w/ existing (email, ical, Google cal)
- -> Set specific goals in roadmap (Ted, Sheila)
- Stability / Reliability
- Failing to nail critical feature set for adoption
- -> Get BK to focus on email, deemphasized i18n (Philippe)
- -> Quick and Dirty feedbacck from users, use survey, take guesswork out of feedback (Sheila)
- Data evolution, Schema migration
- QoS : up and running, not going down too long
- -> Publicly set up goals/target for beta (Jared)
- Data integrity : backup/restore, no corruption/loss
- -> Talkbacck (Heikki)
- -> Backup feature in desktop (Philippe)
- -> Services/Cosmo features (Jared, Ted)
- -> Get the right set of tests and metrics : stress tests, long running tests on desktop, round trip tests
- Dashboard/stamping: getting visual affordances right
- Alpha4 focus on dashboard, alpha5 planning (Sheila)
- Work we don't yet understand for end-end cosmo workflows
- -> Get to dogfood asap. more real dogfooders
- Server plan (lots of things to do, ability to execute the plan)
- -> Nail down hiring plan (Ted)
Staff meeting
- Staff news
- Sprint update
- Lozenge demo (Jeffrey)
- Sharing world demo (Morgen)
--
PhilippeBossut - 22 Aug 2006