Preview Countdown Meeting - May 21, 2007

Agenda

• Cosmo 0.6.1 migration
• 0.7 Schedule
  • Review next actions for getting 0.7 dates updated
• Wiki update
  • Where we are and what we need help with

Notes

Cosmo 0.6.1 migration

• Cosmo 0.6.1 released last week
• Where are we? What are the next actions to launch everything?
• No current migration blockers for Friday's checkpoint
• Still need to do an interactive session to test out migration internally
• Session planned for Tuesday @ 11:00am - move ops meeting to 10:00am
• If we don't run into any issues we can send out all the announcements and declare ourselves done
• Katie: live with some issues we find for now - these people are better targets for actual releases

Schedule and Deliverables Update

• Chandler update
  • Philippe looked an initial look at the numbers
  • Most of the items in 0.7alpha5 are P4 and P5 and will be punted
  • Estimate of 42 days to handle the P1s, P2s, P3s (we have identified now) - developer days to get to code complete (end of July)
  • Another way to look at this is the trend of bug logging - logging about 40 bugs per week
  • Swag is only the apps team and not the platform team
  • Gives us the glide path for everyone
  • Next action: Look at the P3s that are marked Medium and Large swag since eliminating those will have a bigger impact (Sheila will drive this)
  • Next action: Time to create the 0.7.1 bucket in bugzilla and we can put some items ie: interop into that bin (Sheila will talk to Philippe and Heikki)
• Cosmo
  • Ted, Priscilla and Sheila meeting on Tuesday to look at feature list
  • Should be able to have Cosmo swags done by next week
• Service/Hub
  • Production against hub - some EIM related bugs filed against Chandler
  • Figure out who owns them and how they are coordinated
  • Need to have some owner and they can pass along to others
• Other
  • (Wednesday QA session would be the performance review (tentative)
  • Need to update all the other documentation type dates (Sheila will discuss with Mimi, Priss and Jared)
  • Logo
    • Trademark search - should hear back on Wed or Thurs
    • We need to start trying the logo on the desktop - different backgrounds
    • We can go ahead and try the existing image - Mimi usually sends the logos to Bear
    • Next action: Mimi will ping Bear about getting these updated
  • Metrics stuff
    • Still pending because of time spent on migration stuff
    • Next action: Sheila and Jared will talk offline
  • Dogfoodable Chandler
    • Need an estimate for Katie (Wed @ 4:00pm)
    • Aparna and Sheila will look at dump and reload bugs and mark them blockers for 0.7
    • Next action: Sheila and Aparna will review blockers after the Tues bug council

Corrupt Production Data (Katie)

• There was a point where the data on the Hub office calendar has messed up data - duplicate items due to a recurrence bug
• Possible that the data in the dump file that Aparna constructed has a bunch of extra content items - from an earlier bug in dump and reload
• Morgen can help clean that data OR Aparna can create a new file with the latest Chandler
• Check the office calendar on Hub and see if data is still messed up
• Need to figure out how we track that production data is corrupt - in the service or in individual bugs
• Next action: Katie and Jared will discuss this production tracking issue
• Next action: Jared will file a bug against service and will talk to Morgen about the office calendar
• Next action: Aparna will probably generate a new data file with the latest Chandler build

Wiki update

• Mimi sent a summary of wiki issues and status to the general list
• Mimi, Sheila and Priscilla met to talk about structure for Product area - Mimi is working on this
• Product area needs interop section
• Engineering and community areas need some work
• Mimi - working on draft of PPD team page
• Sheila - driving fixing the Get Involved area
• Pieter - working on screen casts and FAQs
• Need a technology and architecture overview owner
• Vision doc - maybe we don't need this with the design overview and product roadmap - still missing server/service issue
• Pieter using Google analytics - most viewed page is the compelling vision page and people are also looking at the mission statement
• Design overview = current philosophy page
• Vision document - off the landing page and accessed frequently
• Do we need a brief document at a high level that talks about compelling vision
  • Mimi was imagining that the combination of the position statement and the expanded nutshell would cover this type of information - abstract of the product
  • We could create one for technical design
  • Do we need something brief that hits target users? Talk about who we are designing for?
  • The important things to talk about at a high level of the picture wrt the target users
  • We would fit this into the design overview
  • Pieter: present this as Vision - use this wording.
  • Ted: take the link on the website and point to the philosophy page
  • Katie: still missing the technical piece how service/server/CALDAV fits in
  • Maybe need something short that hooks into extensive design piece and technical overview
  • Next action: complete list of stuff for the design overview and draft up the technical overview, then look at high-level hook to both of these pages
• Need something that lists the Preview feature set - concise list
  • Understand the requirement - someone outside the project can look in one place (one page) in order to make the decision on whether or not they want to use the product. Also useful to see the feature list in the context of the plan (if it's not there we might have it in 0.7.1).
  • Important to state what we can do right now.
  • Next action: Sheila will own driving this work with the planning pages
• Need owners for technical documents - desktop and server
  • Katie: desktop document
  • Ted & Katie: collaborate on server piece
• Interop
  • Big picture about what we are supporting
  • Separate session - isolate the pieces - Katie and Ted helping with documentation
  • Next action: talk about this with a smaller group
• Ted doing the individual Get Involved stuff
• Sheila, Ted, Mimi and Pieter will talk about the hierarchy - Sheila will drive the discussion
• Position statements
  • Next action: move forward with tagline for the wiki home
  • Mimi took a stab and we can send to the list for feedback
• Wiki now at chandlerproject.org - moved
• Mimi - still pushing out the remainder wiki areas - planning, engineering and notes
  • Engineering - put this off for a couple of weeks
  • Visual design - header redo for top bar - next action: Jared will review and reply to email
  • Planning - Sheila and Mimi will talk about the minimum set of things we need to get this out
  • Notes - wait until other stuff is done

-- SheilaMooney - 21 May 2007