Ops Meeting - May 16th, 2006

Staffing Update

• Interns : see http://wiki.osafoundation.org/bin/view/Projects/IntershipPlan06
• Adam Christian qa contractor helping Mikeal during Aparna's maternity leave, Mikeal to introduce him at the staff meeting
• Katie de facto hiring manager for the business development position
• Cosmo/Scooby job descriptions, John working on this. Description ready for Cosmo, still some work needed on Scooby. Wednesday dead line.

Issue: Could we use Suzette to help with hiring now that Lori is leaving? Could do things like posting, initial screening.

CSG Update

Sheila last week at the meeting.

Gave update to the CSG people on Cosmo, Scooby and Chandler.

We'll continue the relationship but not going to all CSG meetings (may be every other ones). Next one in January 07 then (we'll skip the September 06 one).

Foxmarks operations and "back of the envelope" approach to thinking about Chandler service operations planning

Jared put a short doc together.

Foxmark: We've been maintaining labor cost to a low level. Mitch thinks we should shoot for a 100,000 users, too early to plan for more than that.

Ops challenge: How do we start so we can scale but don't over spend? Our needs are more CPU intensive than bandwidth intensive. We are assuming that we will have needs for an RDB storage (as a persistent layer) and we'll be able to split RDB machines and Scooby machines and handle them as a cluster. That will be the basic unit of scalability. We should be able to have users in different clusters and them continue to share transparently. The basic assumption is that the clusters themselves do not have to share anything (i.e. all the data of every single user can live on 1 single server).

Issues:

• Scaling with the number of apps we support?
• Scaling with the number of versions of Scooby working in the wild?
• Scaling of work force?
• Rate of software change we'll incur?
• QOS (Quality of Service) level we want to provide? (24x7)
• Customer support cost? (escalation)

Next steps:

• have a schedule for the project
• have an idea of the ramp up (hypothesis on the number of people signing up per month)
• get some perspective from other startups with similar need

Target User Feedback

Mimi presenting her persona doc.

Trying to target categories that are likely to:

• switch or adopt Chandler (early adopters)
• pull others in the ecosystem (influencers)

Presented the personas with (priorities):

• Hub (1)
• Busy Body / Coordinator (2)
• Apex (2)
• Assistant (2)
• Individual Contributor (3)
• Passer by

Mimi to present this at the staff meeting.

Staff meeting agenda

• Intro of Adam (Philippe to ask Mikeal)
• Mimi to present the personas
• Ted updating people on governance
• No demo this week

-- PhilippeBossut - 16 May 2006