Ops Meeting May 15th, 2007

Present: Sheila, Ted, Aparna, Heikki, Katie, Jared, Philippe

Agenda

• Interns
• PTO Tracking
• Review process checkin
• Release management, and coordinated hub/cosmo releases
• List charter
• Calconnect
• Staff meeting agenda, demos

Interns

• Jacob Robinson (QA) starting today
• Aditya (IT) to show up today for lunch at the office. Will start May 28th.
• Alexandru Dragusin (Cosmo) starting next week
• Ed Bindl (Chandler) to start mid June (June 11th)

PTO tracking

• Accounting would like to change how PTO are handled
• Would like manager accountability, track the quarter by quarter balance
• Will send a spreadsheet to manager per quarter to update
• Need to make sure that people use their PTO, don't accumulate too many days, BTW 1/2 PTO are not legal under California work law

Review process checkin

• We'll have all the formal reviews done over the next 2 weeks
• Most of us already started to give them
• Katie and Suzette making a proposal for the compensation adjustment, will present to Mitch later
• Forms worked well this year, we may add some more structure to the form next year but still keep it really simple (may be 3 or 4 sub sections in the manager's review so we don't forget things like accomplishment for instance)

Release management, and coordinated hub/cosmo releases

• Good that we identified a release manager function for the whole process
• Should we have one single check list for Chandler/Cosmo? Not really but both should make sure they check interop with the other
• Release manager should put together a more detailed plan (on what to be done to release a product) for both products
• Priscilla in that role for Server/Webclient, Heikki for Desktop

List charters

• What goes on general@? Wiki and community, may be too managerial, very low traffic. We should use it for cross product issues more frequently, e.g. wiki gardening. Broadcast that list to say that the charter of that list will change. Release management discussion will happen on the relevant dev list.
• Where should Preview process conversations live? Design@ or relevant dev@.
• Where should conversations go about "release management" for cosmo releases that are deployed to hub.chandlerproject.org? On the relevant dev@.
• Where should conversations about wiki gardening go? On general@.

Calconnect

• Mikeal our representative
• Presence at Calconnect sometimes conflicts will other duties at OSAF
• Should we attend more than the interop sessions? Not necessarily.
• Round table discussions not that useful. Issue is that you need more context to make it useful so sending someone else in lieu of Mikeal is not that productive.
• We can have someone else attending interops if it's too critical for Mikeal to stay. Also, we can participate to interops remotely.
• Aparna to manage this with Mikeal.

Staff meeting

• Use of the lists, especially general@ (Katie)
• Demos
  • Dump and Reload, Migration (Jared)
  • Edit/Update (Philippe to organize)
  • Windmill (Mikeal and Adam)
  • Google Analytics (Pieter)
• Message of the week: The end is nigh! (Sheila) Dogfoodable checkpoint (Katie), picnic (Katie), interns (Philippe)

-- PhilippeBossut - 15 May 2007