r2 - 13 Jul 2007 - 10:20:05 - MimiYinYou are here: OSAF >  Journal Web  >  OperationsTeam > OperationsGroupMeetingNotes20070522

Ops Meeting May 22nd, 2007

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

Agenda

  • Personnel -review checkin (Katie)
  • intern checkin (Philippe)
  • Service - tracking service bugs
  • tracking data corruption problems
  • Bug 9174 as case study
  • OSCON - who is going?
  • how do current schedule plans fit with OSCON?
  • Preview Schedule(Katie) - tradeoffs and schedule, how to think about this strategically
  • are we all focused on Preview? (reviews have been a distraction--anything we can do from here to limit distractions?)

Review checkin - Katie

  • No new update. The reviews are coming along well.

Intern Update - Philippe

  • Jacob started in the QA team and Alex in the Cosmo team
  • Aditya to start next week with IT
  • Ed Bindl to arrive June 11th
  • Alex will use his own machine and Jacob is using the shared QA laptop

Service bug triage (Jared)

  • Service is currently using bugzilla for tracking service related bugs. There was no conscious effort being made to assign those bugs to product 'Shared Service' purely because no one was aware that such a product existed in bugzilla. If a bug is related to data corruption on service but we don't know whether it was caused from Chandler or Cosmo then it would be best to assign the bug to Service and Jared will get the right people involved to fix the issue.
  • Information on how to file service bugs is available on the IT page.
  • Sheila and Aparna will keep track of bugs assigned to Shared Service.
  • Open issues known on Service will be brought up once a week in the Preview meeting on Monday or a weekly update will be sent to the service-dev list.

OSCON (Katie, Ted)

  • who is going? Mikeal and Adam will be going for the Windmill presentation. Ted and Mimi for the Open Design session and Katie will do the lightening talk about the state of our projects. Others are unknown at this point. At the most 1 or 2 people from Desktop team and 1 or 2 from the Cosmo team.

  • how do current schedule plans fit with OSCON? Oscon is on July 25th. WE should plan to code complete by then. Cosmo has about 250 outstanding bugs half of which are feature tasks.
  • We need to aggressively triage bugs both on Desktop and Server.
  • Sheila is going to meet with Philippe and come up with a tentative code complete date for the Desktop team
  • Priscilla and Sheila to meet come up with tentative code complete date for the Server team
  • One of the options is to look at bugs and their swags and see if we can cut out some large swag items if the return is not that significant.

Preview schedule (Katie) tradeoffs and the schedule, how to think about this strategically

  • identifying right channel for dogfooders to report problems and give feedback
  • demos at OSCON shouldn't take up too much of our time. The focus should remain 'Preview'
  • July time (just before OSCON) is a slow period because people will be traveling here for Picnic and Sprints
  • Maybe we should consider postponing the picnic and sprints to mid-August. We could align it with the Preview celebration.
  • Productivity around sprints is low in terms of code deliverables (high around design discussions)
  • We should make a decision by next week
  • We could conduct 1/2 day test days potentially at the end of the cycle
  • Jared coming to the Desktop team to give updates on the Service.

-- AparnaKadakia - 22 May 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.