Agenda:

• Report on Scooby 0.1 release
  • Are there any major issues that came up yesterday, today?

• Testing
  • Encourage everyone to download the latest build: http://builds.osafoundation.org

• Scooby landing/project page (just a quick update on what is going on.)
  • Landing/project page content brainstorm was summarized on the list.
  • Next steps is to organize and assign content to pepl
  • A source repository has been created for Scooby (and requested for Cosmo)

• Proposal for Scooby 0.2 Tenents:
  • First Draft Proposal on Scooby 0.2 Tenents
  • Review the tenents for 0.2 and sending it to the Scooby list for feedback.
  • Will update Scooby section to add 0.2 Planning.

• Propose to do a 'process debrief'
  • Scroll down to Notes on Scheduling and Priorities
  • Help create a better development cycle so it's routine. What worked, what didn't work?
  • Coming up with a release cycle plan that works for everyone

Next Action Items

Report on Scooby 0.1 release

• Code freeze can add documentation and comments
• Recurring events�file bug fix
• Bobby's e-mail on Scooby Process for Code-Freeeze/Testing Cycles (need to add to the Scooby section on the wiki

Scooby landing/project page

• The amount of content for the Scooby landing/project page will depend on the release date for Cosmo.
• Pieter: will send out Scooby list a chart on the wiki^? and assign people for landing/project page
  • Review on the Scooby list about issues such as, "For developers corner": How to build and set up dev environment and how to download 'Snarf' bundle
  • JavaScript libraries (correction from AJAX libraries)
• Priss: Send to list about the naming of Snarf vs. Scooby/Cosmo bundle

Proposal for Scooby 0.2 Tenents:

• Need more discussion for a long term project plan/vision for Scooby
• Bobby: Will send questions to the design list about future framework for Scooby

'Process debrief' for Scooby 0.1 � Topic for discussion discussion

• Development cycle will not be always exact to the example of 30 days. Sometimes a Scooby release may take 20-40 days, but is less then 60 days.
• The tenents will determine the schedule of the release cycle, but the assumtion is that the release cycle will be time based opposed to feature based.
• Include x amount of days in the SWAG for code cleaning, comments, etc. before handing off to QA. Pre-release phase. Then code freeze. See Bobby's e-mail on Scooby Process for Code-Freeeze/Testing Cycles
• Since 0.1 is the first time release, there is still a learing curve about pre-release, code freeze, and to plan landing/project page simotaniously with the release tenents.
• Mile stone release will be defined as releasing big functionality, high level product strategy and will be sent to the Scooby list first
• Need more discussion and provide a clear vision for Scooby, part of project planning (long term) in the begining to help answer some of these questions.
• May revisit 0.1 'debrief' in next week's meeting, but will not schedule a seperate meeting for 0.1. Until the project is more fully developed, ie. Chandler there is no need to make the debrief it's own meeting. In other words, the process is to simulate Chandler's process, but currently much more scaled down.