Preview Meeting March 19th, 2007

Agenda

• Review of updates to the Preview Countdown (3 min)
• Review upcoming deliverables (2 min)
• Logo - next steps (2 min)
• Position statements - next steps (5 min)
• Wiki next actions (5 min)
• End-user documentation - last call Mar 13th ( 2 min)

Notes

• Sheila has updated the gant chart.
• sheila met w/ jared and added items ie. terms of service doc.
• you can track process on the gant chart
• hub/server pushed out dates
• site design close on technology
• final terms in service draft, doesn't need to come in till

• next actions -sheila/ted/priss have met last week to close in on the cosmo dates.
• come up w/ a better confident schedule for cosmo 0.7.
• we're scoping out all the dashboard work and figure out what to cut down.

• next Monday Chandler feature freeze
• engineering meeting, more details

• Philippe: EIML activities going on right now on the list/devlopment ppl are working on it
• EIML on a different milestones
• Katie: problem EIML stuff that's just a delta off the other features from the release
• last mile or half mile; 100 yards wrapping up of all the other features landed, having the two happen on the same day isn't realistic.
• waiting for some details to land
• having that in is most valuable.
• Reid: working on both context menu (lower) for items or EIML stuff. Going to finish EIML stuff first.
• Ted: the sooner EIM stuff done, the more cosmo 0.6.1 to start testing
• Middle of next week. there's really two mile stones in getting the EIM work done, then finishing all the other stuff first.

Milestones

1. Finish EIML interop w/ cosmo
2. Chandler EIML work
3. Finish other tasks work

• end of this week. EIML Chandler (and the 0.6.1 stuff finished?)
• other chandler tasks
• cosmo 0.6.1 EIML stuff --> need to check w/ mogan on schedule

• All the EIML stuff, teams are working close together—both teams is finished for this week.
• Reid and Robin are not working on EIML stuff.

• 0.7 cosmo - team has started dashboard stuff

Questions

• June 11th, non-dev deliverables. Pieter to create bugzilla superbug for documentation deliverables, wiki, blogs, etc. all the dependency stuff.
• Mimi had sent a last call to the design list about non-dev doc.
• Next actions Sheila to send out, need feedback from mostly PPD, pieter, Katie, Philippe. End user documentation. Enough points of view, for rounded out
• right set of content.
• a lot to write, some of the ppl to be owners to be content.
• the good set to target
• all the expectations to be satisfied. Do not want to be the beginning of june and realize we have
• high level if this seems reasonable.

• logo work met w/ the ops team. there area more logos which are being refined and will follow up for review next week.

• Position statements follow up meeting after this.

• wiki next actions: Priscilla & Jared sent out an email about sending
• what other pages should other then the main planning page to migrate
• bear/aparna hosted service qa --> next actions for them to look at it.

• there is an issue that wen we move the sub pages—search engines outside OSAF and email archive will break
• propose to have a wiki automatic redirect, on IE6 it may take a long time to redirect, but it does work. Which ones are important enough to move?
• meeting notes are important
• main teams area
• leaving a stub. the page is active, click here or re-direct. I wouldn't leave the content there.
• jared's concern about some consistency
• if we leave the page, then we double the pages
• wiki area lead will be responsible for making sure there are stub and re-direct on the sub pages.
• Pieter/Priss/Jared to work together and send out a best practices example of a stub page and redirect in 30secs.
• Jared to look into the 30 sec. re-direct.

• Jared's issues, do we want to use www.? Take the discussion on the pr list.
• deprecating alpha 4?
• Date for the count down, milestone for when alpha 4 is no longer usable.
• EIM roll out store, we don't have clear —need to follow up w/ an EIM roll out.
• next action for sheila/katie and philippe after the high level -->next week or monday after to meet.

• Pieter, created superbug, 0.7 release appropriate. To call things 0.7 release vs. calling them preview.
• The word 'preview' was independent. 0.7 release--> chandler. Some items are cosmo items. Some items span both? How are we tracking bugs like the logo, or documentation such as landing pages under both.
• Pieter is using chandler, we will need a seperate component.
• Do we want to have a branding/ marketing component.
• We need a new product. If that product can be used for creative launches.
• We have an osaf products--> for server and web sites.
• That look like appropriate one.
• Pieter to work w/ Philippe on the right list. Work w/ Heikki and Bear.

• Trademark update from Pieter.
• working up the paper work, Mitch to sign and then it will be filed about 90 days file for additional countries.
• Pieter to prepare a shopping list for countries and regions to protect the ™ and logo
• logo search on the ™ data base. If we use some logos ie. starfish, will we conflict w/ other logos in the same.
• subsequent filing for the logo itself.
• should we secure 'cproj.org'? I want to type in something short in the URL. --> pieter to send to the pr list
• I think we need to get a domain taht is short.

• Jared has contacted the lawyer twice about service terms. Sheila has added the service terms on the list.

-- Notes taken by PriscillaChung - 19 Mar 2007

-- SheilaMooney - 19 Mar 2007