Preview Countdown Meeting - March 5 2007

Agenda

• Deliverables review for last week.
• Deliverables not met (or not scheduled correctly).
  • Metrics infrastructure running regularly to product updates.
  • osaf.us shows new web presence
  • Product site architecture/hierarchy complete.
  • Final decisions on site technologies.
  • osaf.us also available via final domain name.
  • Production hardware up at colo.
• Next actions in progress...
  • Inventory of code related changes due to branding.
  • Inventory of non-code documentation.
  • Draft of trademark policy and trademark usage.
  • Position statements.
  • Logo presentation for ops team.
  • Terms of service.
  • Landing page design.
• Recap decisions made on naming, domain name etc. Naming
• Tracking Preview status and schedule
  • We discussed this in detail last week and during the ops meeting.
  • Based on this I have drafted a proposal for addressing some of the concerns.
  • Review the following - http://wiki.osafoundation.org/Journal/NamingDecisionsRecap20070302

#Notes

Notes

• Big deliverables last week was cosmo launch
• Hosted service stuff. Were they scheduled correctly?
  • Sheila and Jared off-line to come up with a better schedule * Next actions on the list, not done
  • inventory of code –next actions–sheila to go over w/ ppd, get appropriate list to review in this meeting
  • It will be on a wiki page to be tracked
• draft trade mark policy -Pieter added a link to the page, and will follow up w/ e-mail.
• Position statements next actions everyone to write up a blurb. Logo and trademark usage.
• Logo – trouble narrowing down what to present on the list. Next actions to follow up in the PPD meeting.
• Terms of service - hosted service - behind but is working on it, follow up this week.
• Landing page design - several iteration shave been sent to the pr list. Logo is the highest priority.
• Follow up with the lawyer - Pieter
• Domain name. Hyphenated domain names. Naming decision recap, decisions we've made so far. What was closed on what was still open item?
  • Brand name chandler, chandler desktop, server, hub
  • referencing the extensibility of the desktop, extending chandler desktop.
  • weren't sure when we'll used chander and chandler project, not needed to make that decision now, but can be on a case by case basis.
  • closed on chandlerproject.org–how to make this official? It is decided. –next actions w/ jared to take offline w/ Sheila
• Going over decisions made
• Open issues: do we want to go ahead and purchase the hyphnated, .com, .org, .net, .info, for completeness? Just get one, hypnated and info for chandlerproject.info -katie to file the ticket
  • create a page for all the domain names we own
• Should we move the wiki, to wiki.chandlerproject.org? Having the URL is a very strong connection. Could we get close enough that ppl would feel confident. Moving forward w/ closing the decision on moving the URL. -Sheila/Jared to figure out logistic offline. Pick a date and move it. Discuss w/ Dave in the IT group on Friday IT meeting. - Monday we'll have a date.
• Developer tools, svn, bugzilla, proposal to not move them. The build site, may be more public facing. Open to suggestion. Just as a practical. Technically we can only move the build site. Everything else will break.
  • builds and download.osafoundation.org is public facing.
  • mirrors everything from osafoundation and to chandler.org - known under multiple names.
• Move pyicu.osafoundation? Decide to leave it where it is.
• service.info, chandlerproject.info, blog. wiki., not using a path for those. Mirror.
  • Prioritizing mirroring – next actions to follow up in the IT meeting on Friday. Jared/Bear.
• Tracking stuff preview
  • after feature freeze, 3 wk period on performance. - during that time, there may be bug fixes if they block and Cosmo 0.6.1 release and may have interop issues. Interop work cannot start sooner as it will be finished sooner
  • April 16th, estimate end of that 3 wk
  • Final code complete is difficult. How many bugs are we going to have
  • bugs we have today, how long do you think it's going to take to fix it? Approx. 50 days, 8 wks.
  • Not going to be April 20th, push out to June 16th. New bugs will be coming out th same rate.
  • EIM will be spike up the bug list, but it's not for everyone to work on. Understanding all the feature landed and the performance work, we'll be able to have a better estimate on the date.
  • milestone on the exit criteria great, tracking that long the way will help give visibility.
  • not tracking that level detail in the release of Cosmo 0.6.1, end user dogfoodable release

• A small group of users to start testing Chandler Preview –next actions: Katie to send out email about 'when can have have users dogfood'
• Frame a little bit of the soft launch and who the soft loaunch users are–need to have identified milestone for that, but cannot say what it is right now.
• Sheila will send out update gant change for a better way to visual it. - follow up w/ Ted & Priss for Cosmo release.
  • Cosmo 0.7, if we do the dashboard? May need a longer QA cycle. - Sheila to sit down w/ Ted & Priss
  • 0.6.1 is not a visual feature, it's to iron out bugs for the sharing format.
  • how to manage ppl to switching protocols. Dates have been moved out 2 wks - Sheila, Jared, Ted & Priss to take off-line on the schedule status.

• Wiki taxonomy, everyone to look at their area on the wiki. Replacing what we have today.
  • Do we want an explicit goal. Specific next actions for the various wiki owners.
  • Planning area flushed out, Cosmo design, product area. Teams area are solid. QA, builds/ teams and section as well as the planning
  • Planning - Sheila, Cosmo areas - Priss, Bear/Aparna/Jared - hosted service, QA, builds spread apart the areas.–all the owners need to look at it and take a look at it before next weekend. Sheila to capture it and follow up in the PPD meeting.

-- SheilaMooney - 03 Mar 2007