Ops Meeting, Tuesday May 2nd 2006

Staffing Update

• interns: We're set with a list of interns. Philippe driving. One offer to go to Vinu (Cosmo). May be move Ed to Scooby (Philippe to follow up with John).
• chandler staffing changes: Need contingency plan for the people leaving. Philippe and Katie working on this.
• cosmo/scooby position: Looking for someone more Cosmo side than Scooby. John building a job description.
• business dev position: May be not a permanent position (requirement may change, we need a generalist now, more of a specialist later). Work on both Foxmarks and Chandler? Mitch and John Lilly working on this.

CSG Update

Mitch sent a draft report and integrated the feedback. Consensus on this.

Ecosystem Value Hypothesis

Still getting feedback on the Vision and Prioritization of elements. Wait till Thursday (last call on prioritization from Mimi).

Using "Chandler" for all projects

• Proposal: use "Chandler Desktop", "Chandler Webapp", "Chandler Sharing Server"
• Should we go ahead and do this now? Helps use to set the right tone, different from the branding discussion though.
• What will it take to implement this now? Issues with the mailing lists, Wiki, etc... May be we don't want to do all that now, wait till the branding is done.

Consensus: use the new naming scheme, talk about it to the staff meeting but not change everything in Wiki, making list, etc... right now.

Foxmarks and Cosmo

• Cosmo priority: make the Chandler ecosystem successful. Will move into being a sharing service/server beyond just CalDAV.
• Foxmarks may move away from Cosmo for its own good. Anyway, Foxmarks may need to have its own resource for this (Cosmo or not).
• Cosmo development shouldn't be driven by Foxmarks requirements. So far, this allowed Cosmo to do work on scalability, perf, account management (all good). In the future, the directions will diverge.
• Currently we are changing the order of things we need to do anyway. The bigger issue is that Foxmarks may need to pony up resources to cover some of its need. We may want to exchange some Java services for QA services to make things easier.

Dogfood scenario

Issue with Esther syncing on Cosmo-demo (memory leak then crash). Lack of stability of the whole dogfooding system. Our process to deal with issues is too ad-hoc. What should we do?

Have an email address for escalation of this kind of issues, on the model we have for support at kei.

License issue

Some people can't use GPL licensed code. Switch to Apache licensing or LGPL? May be we should switch to one single licensing scheme for all. General consensus on this but we need to take the time of reflection about this.

Sprint Week

Next week. All regular meetings cancelled so that we can focus on people in town.

Staff Meeting Agenda

• Demos: markup bar and wxColumnHeader
• Markku intro
• Naming scheme

-- PhilippeBossut - 02 May 2006