Scooby 0.2 Planning

Proposal for 0.2 Tenets

While we're working on long-term strategic planning for Scooby, we want to make sure we will not block the development progress in the short-term. As a result, we've decided to stick with the original 0.1 plan that was originally slated for May.

For more details on original 0.1 release : http://wiki.osafoundation.org/bin/view/Journal/ScoobyMeeting20060111

The overall goal for this original release is to have a 'Target User' be able to 'use' Scooby in a very specific way. There may be a few specific Usage Scenarios. For example, a Chandler User who may want to be able to view their calendar data on the web, Scooby. The target user release date for Scooby is currently TBD. There is no dot number or date pinned to this release.

'Target User' Goal: Scooby release for target user is when all the basic calendar features are available for the users to start using Scooby. Only then would the release be a "useable" release.

Tenet for 'Target User':

• Data availability = "The data you have (in Chandler) is the data you see (in Scooby)"

For more details on Target User Release: http://wiki.osafoundation.org/bin/view/Projects/ScoobyReleaseForTargetUser

Here are the proposed tenets for Scooby 0.2. The 0.2 tenet is mainly to do the next chunk of functionality which makes sense and is doable in the 4-6 week time frame from when the 0.2 tenets are approved. This will be a time-driven release. http://wiki.osafoundation.org/bin/view/Projects/ScoobyZeroDotTwo

Proposal for 0.2 Tenets

• Continue down the original 0.1 plan.
• To show progress from 0.1 in order to raise excitement in the developer community.
• To view the User's (Chandler) calendar on Cosmo-demo. (Open issue.)
• Performance, stability and compatibility improvements over 0.1 (A tenet that is not user-related, but completely technical: Matthew and Bobby to nominate a few tenets, maybe from wishlist?)

High-level Assumptions

• Target audience is potential community contributor/developer, volunteer. No target user will be identified since this is still not intended on being a "usable' release.
  • Not for general use. Still mainly target for a narrow audience. Users interested in web technologies, AJAX and/or calendaring.
• Chandler users may be casual users of Scooby.
  • To make viewing Chandler calendar in Scooby an easier process.
  • Revise layout to more closely resemble Chandler. It should feel like home to a Chandler users.
• We're only concerned with read scenarios. Write scenarios don't need to work.
• Re-factoring and documentation from Scooby 0.1 will be in Scooby 0.2
• Scooby will continue to be bundled with the release for Cosmo. Your Scooby account is your Cosmo account.
• To exhibit the beginnings of a high quality consumer application. ie. Scooby logo, consistent icon set, small aesthetics tweaks.
  • For now, visuals will proceed in the "take it or leave it" design process. A more in-depth review of the Scooby "look and feel" will be addressed at a later release date.