Preview Countdown Meeting

Agenda

• Review Sheila's first draft of a Preview countdown list (30 min or less)
• General feedback and next actions for updates
• Gather open issues
• Sheila will send this out prior to the meeting
• Positioning statements (5 min)
• Pieter will update us on the next actions for drafting positioning statements.
• Product naming (10 min)
• Discuss next actions to determine product names ( System/Solution, Desktop, Server/Web bundle, Hosted Service)
• Branding Logo update - Mimi and Trevor will give us a summary of where we are and the next steps (5 min)
• Product site issues (10 min)
• Discuss next actions for closing on roles for www.osafoundation.org and www.chandlerproject.org

Preview Countdown List

For the first item on the list, we will be reviewing the "uber" Preview countdown page I have started to put together. A couple of notes.... http://wiki.osafoundation.org/Projects/PreviewReleaseCountdown

• It's not fully complete - this is what I want help with today
• Don't take the dates to seriously. Now that we moved the Chandler feature freeze deadline, I kind of had to make up some of the other dates knowing that they weren't quite right.
• The goal today is to help me identify what "major" deliverables are missing as well as other open issues we should be thinking about and tracking.
• I have a bunch of specific questions about this table and how to make it more useful to this group.
• I am still working on the secondary pages that detail all the specific code changes for branding as well as all the documentation items we need. The plan is to assign owners and bugs to all of those.

Notes

• Preview Countdown
  • Wiki tables or bugzilla? Sheila is trying to take an inventory first, once we have bugs, we won't need to keep track in the table. Use the table to collect the tasks. Use the table for timeline of big deliverables and big dependencies.
  • Sheila: Do we need the level of detail for logistical process? Philippe: yes, we should write down the process. It is better for everyone to know how. Aparna: Not sure we need a formal checklist. Ted: We need to have a good sense of who depends on what. Need to track dependencies.
  • Sheila: Anything missing from the list? Jared: Terms of Service.
  • Aparna: What if we miss a date or a date changes? Sheila: I will keep close contact and keep the dates updated. If anyone knows of something that impacts the deliverables, this meeting is a good forum and Sheila will update the table.
  • Ted: Date for Cosmo 0.6.1 -- 3 days between Chandler feature freeze and 0.6.1 is too short. 1 week for final QA after interop testing is done. Is interop testing done at Feature Freeze? We're looking at 1-2 week loop for interop testing. Sheila: we should be putting QA milestones in individually. What are other QA milestones? (Aparna to note QA milestones)
  • Philippe: Have been using Gantt charts for this kind of tracking, can visualize tasks in parallel, dependencies? Should we use a tool for this, easier to update? (Philippe and Jared to look into tool for visualization).
  • Philippe: What is this week? Sheila: Cosmo release.
  • Ted: Milestone for when sharing lands, interop testing can begin in earnest.
  • Mimi: If we are delayed, can we have more time for logo? Sheila/Pieter: Yes. Ted: Cosmo has to reskin the whole app, so dependencies on having the logo. 3 extra weeks -- would be good for Cosmo to get a bit of that time.
• Positioning Statement Next Steps
  • Pieter sent email to branding committee. Will resend to pr list. Conversation will happen on pr list from here. Post to pr list as we iterate.
  • Pieter will assign people to target users, each person should draft a position statement.
  • Mimi: is this in addition to position statements for SNARF users and platform developers? Do we need a separate position statement for every target user? It might be that we really want to focus on Helen the Hub. She is driving the collaboration, she is our first adopter.
  • People should send draft statements to the list by Thursday.
• Product Naming
  • This week: send ideas as thread on list. On Monday we can collect on wiki and decide if we want to fork into separate brainstorming meetings.
• Branding Logo update
  • Mascot concepts treated with abstract treatment
  • Each will nominate top 5/10 concepts
  • Would like to review ideas on Monday
  • http://wiki.osafoundation.org/Projects/VisualBrainstormWIP
• Product site issues
  • Ted's concern: we don't hide osafoundation identity/affiliation. The foundation is important to the brand, the foundation is important
  • Other concerns: (1) want to avoid split attention across websites (2) want to avoid silo'ing users from group of people developing the product (this includes design and user feedback, not just developers)
  • Will "open source applications foundation" be visible on www.chandlerproject.org?
  • Next action: Katie to post to pr list, Pieter to follow up on pr list.
  • Jared: not worried about technical implications.