r6 - 01 Aug 2007 - 13:05:20 - PhilippeBossutYou are here: OSAF >  Journal Web  >  MeetingNotes > ManagementCommitteeMeetingNotes > OperationsGroupMeetingNotes20070220

Operations Group Meeting 20 Feb 2007

Attending: Mitch, Sheila, Jared, Ted, Aparna, Heikki. Agenda prepared by Philippe

Branding/Pr

  • Domain name and Wiki: Katie summarized the discussion in an email to the Pr list before leaving. The next step is to get agreement on the design of the landing page (so that we alleviate worries about OSAF being buried or hidden) and the URL for the Wiki.
    • Next actions: Waiting on Ted to look at mock-up for integrated landing page. He can give us feedback on whether or not it conveys the relationship to OSAF. Sheila will forward Ted the email with the latest mock-up proposal.
  • Product naming: Lots of discussion on this last week. Looks like we have convergence on what needs to be named but there's no agreement on how to name the "service" and the "Snarf" parts. PPD driving the discussion so far. What is the next step?
    • Next actions: Sheila and Mimi will frame the responses and send a proposal to the list.
  • Logo: Got Mimi's email on the Pr list. Feedback starting to get in. Next step is short selection before presenting to Mitch.
    • Next actions: Mimi is giving people until the end of today to respond then she will summarize the feedback and frame the next steps.
  • Calconnect quote: Mikeal, Jared and Pieter wordsmithed something. Did that get to the Calconnect folks?
    • Next actions: Mikeal just sent out a last call on the quote and wants to wrap this up by the end of the day.

QA

  • QA mentioned that we need more hands on deck in testing Chandler and Cosmo. Hiring now (contractor) would be very difficult. We can still hope getting an intern in short order (hmmm...).
  • One thing that has been suggested is that the managers (people in that meeting minus Mitch...) do dedicate some of their time running real test cases (beyond dogfood as we all already do). Thoughts? (Philippe "+1"'s this proposal)
  • Aparna gave us some context * She talked to Katie and Philippe - concerned about testing converage of Chandler. * Past 3 weeks we have spent testing Cosmo - only Dan is testing Chandler. QA is pretty understaffed right now. * Aparna is worried about quality standards for Preview - we need the bar to be very high. * Having an additional contractor is probably not enough. * Bring this up to the ops team for ideas.
  • Options that came up.
    • Have more than one collaborative QA session a week - focused on specific features. Try 2 a week - Wed/Friday.
    • Ted: We could have everyone spending 1 day a week testing. Concerns - the developers are really busy and if we do this the schedule will get pushed way out. The apps team will be very busy as well as other developers who are working on performance.
    • We could do something brute force - get rid of iCal calendar - make people use Chandler. Likely not everyone will participate even with that.
    • Next actions: Bring this up at staff meeting - give some options to people. Talk about how to encourage people to dogfood. Get others suggestions - ideas.

Preview

  • Sheila maintaining the Preview Countdown and the group is reviewing it every week. So far, this new process works well.
  • Things worth mentioning this week (from Chandler's side):
    • EIM: Morgen landed his changes before leaving. API mature enough so Chandler (Edit/Update) not blocked. Cosmo working out compatibility issues this week.
    • Dump and Reload: Lots of discussion on this, resulted on a list of new tasks added to Bugzilla. Work spread among 6 or so devs.
    • Plug ins in Preview: decided to keep those in finally though disable them by default (see Katie's synthetic proposal)
    • Officially Cut: Print, Free-busy
  • Printing - we already cut this officially. We are also going to remove the option entirely since it's so broken. http://wiki.osafoundation.org/Projects/ItemsNotInPreview
  • Free-busy - we haven't talked about this but what we have now is apparently really buggy. Discussion should happen on the list. Sheila will send out an email framing the discussions.
  • Cosmo - done with 0.6 - should we have a celebration. Thorough UI testing, we have something dogfoodable.
    • Sheila will send out an email re: hitting a significant milestone.
    • Sheila will look into the logistics of a celebration - cake etc.

Interns and GSoc

  • Interns: Philippe and Suzette met this week to review the plan. Offers will be posted this week in various colleges across the US. Philippe received a couple of resumes already (people picking stuff up from OSAF's wiki directly)
  • GSoc: We received the start from Google. Ted will be driving the process like last year.

Last week actions follow up

  • Privacy/Terms of Service: follow up with Jared if anything new
    • Next actions: tenets to the PR list.
  • CalDAV and Preview: Chandler started to mark bugs with the "interop" keyword. Need to keep an eye on those.
    • Make sure iCal bugs are prioritized accordingly.
    • Do we have these to test against? Follow-up with Mikeal.
    • Next actions: Sheila still needs to do a write-up on import/export - this also feeds into interop stuff.
  • Build support for Cosmo and Service: follow up with Heikki and Ted.
    • Jared is not stalled on this right now.
    • Bear is starting to look at 0.6.1 bugs. Heikki is in the Cosmo IRC channel now and will be attending the Cosmo engineering.
    • Next actions: Wait to see how above changes improve things.

Staff meeting message and demo

  • Items to discuss
    • QA resources issues - getting everyone at OSAF helping to test (Aparna).
    • Resizable sidebar - talk to Philippe about any apps demos.
    • Countdown - what items got done - what is on the horizon for upcoming week. Make this a regular part of staff meeting (Sheila)
    • Acknowledge Cosmo release - mention cake/celebration.

-- PhilippeBossut - 20 Feb 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r6 < r5 < r4 < r3 < r2 | 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.