---

---

---

Scooby 0.2

While we’re working on long-term strategic planning for Scooby, the overall goal of 0.2 is to not block the development progress in the short-term. As a result, we've decided to stick with the original 0.1 plan to do whatever next chunk of functionality which makes sense to meet the target user release.

The Scooby project will be released and tightly integrated with Cosmo.

Download

• Download the OSAF Server Bundle and follow the integrated server bundle installation instructions. The instructions will help you install and run an integrated server bundle including Tomcat, Jackrabbit, Cosmo and Scooby.
• The Scooby project will be released and tightly integrated with the release of Cosmo 0.4.
• For Scooby Developers read more about Sever Bundle Development.

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 Scooby-demo (Cosmo server).
• Performance, stability and compatibility improvements over 0.1 (A tenet that is not user-related, but completely technical).

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.

Status

• This will be a time-driven release. Ideally somewhere between four to six weeks of development. Plus a week or two for refactoring code, documentation internal/external, and QA.

Features

• The list of features above was determined by using the Feature Ranking Matrix. You can view the Matrix here: Feature Ranking Matrix.

Issues

Here are some open issues which are not resolved for this release yet.

Editing

• How much editing is really needed for Scooby for meet target users release?
• If the event lives on multiple calendars, should users be able to remove events on other calendars when refreshed? Perhaps for target user release, we not trying to support a fully functional editing on Scooby.
• Only concerned with read scenarios. Write scenarios don't need to work?
• Reconciliation of the “same event” on “multiple calendars”? (Need clarification?)

Viewing your (Chandler) calendar on Scooby

• Is Scooby intended to be a web version of Chandler � for now?
• To view the User's (Chandler) calendar on Cosmo-demo. (Will the idea of OSAF as a 'service' need to be introduced for target user release?)
• Would a user be able to view all the collections once logged on to Scooby or would the user be able to select the collections they want to have published to Scooby?

Timezones

• Should users be able to change the default timezone on Scooby? If this release is only usable for read-only scenarios then this may not be needed as we're mostly focused on display issues?
• Let the users set a default timezone
• Be able to set the timezone on events

Specs and Proposals

In progress

Spec Name	Owner	Dev Owner	Tasks	Notes
Account/View/Creation	Priscilla/Towns	Towns	In Progress
Basic User Preferences	Priscilla/Towns	Bobby	In Progress
Calendar Canvas Interaction	Priscilla/Towns	Mde	In Progress
Navigation	Priscilla/Towns	Mde	In Progress

Meeting Notes

(Weekly meetings are scheduled every Thursdays at 3:00PM PST)

• 060615 Meeting Notes
• 060608 Meeting Notes
• 060531 Meeting Notes
• 060524 Meeting Notes
• 060511 Meeting Notes
• 060504 Meeting Notes
• 060426 Meeting Notes
• 060412 Meeting Notes
• 060405 Meeting Notes
• 060329 Meeting Notes
• 060322 Meeting Notes
• Feature Ranking Matrix
• 060228 0.2 Wishlist
• Server Meeting Notes