|
This page has been moved into the Cosmo Wiki project...
|
|
The contents of this page are no longer relevant since Scooby has been incorporated into Cosmo
|
Scooby 0.3
There are currently two target users we are focused on for the release of Scooby 1.0. They are:
- Casual Collaborator - Non-Chandler users viewing calendars published from Chandler.
- Chandler users reading calendars on the web using Scooby. This implies casual use.
For 0.3, our top priority is a specific usage scenario for the Casual Collaborator. We basically want to detail out what we need to satisfy our main target usage scenario first since that's the highest priority. We will also be making progress for the Chandler user, though this would be specific to calendar.
The Scooby project will be released and tightly integrated with Cosmo.
Download
- The download is not available at this time. Scooby 0.3 is currently in the planning phase.
0.3 Tenets
- This will be a dogfoodable release for a very specific task. An example of this task is an OSAF employee being able to use Scooby to put in their paid time off (PTO) on the office calendar.
- To keep raising excitement in the developer community.
- Performance, stability and compatibility improvements over 0.2 (Technical improvements in the architecture).
High-level Assumptions
- This is to be a dogfoodable release, though the target user is very specific and is not intended for a general audience. Calendaring is still the main focus for 0.3. Task lists and other features will be addressed in a later release.
- Potential community contributor/developer, volunteer are still considered the primary target audience. In addition to 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.
- Re-factoring and documentation from Scooby 0.2 will be in Scooby 0.3
- Scooby will continue to be bundled with the release for Cosmo. Your Scooby account is your Cosmo account.
- Revise layout to more closely resemble Chandler where it makes sense.
- To continue exhibiting 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 is a time driven release that may take up to 4-6 weeks. The criteria for success for this release is being able to view the office calendar without an account and to edit it on Scooby.
Specs and Proposals
In Progress
Features
Casual Collaborator
- View calendars without an account
- Jump to date
- Link to mail client to send "Notifications" of newly created events/edited events, for example, PTO announcements)– this is the beginnings of “stamping” but not fully featured as in Chandler.
- Editing and recurring events
- Read/editing calendar
Chandler User reading their Calendars on Scooby
- Viewing all of my Chandler calendars on Scooby (regardless of whether or not they're shared, published, subscriptions) – This feature has a dependancy on the release of Chandler Alpha4.
- Account creation in Scooby
- Time-zones
- Store default time-zone
- Change timezone of calendar canvas
- Edit timezone on specific events
- Subscribe and Publish workflows
- Continue visual tweaks
Things to consider working on because it meets consistency with Chandler, but not as high priority because it does not meet 0.3 target user’s needs:
- Basic user preferences
- View @time and anytime events
- View alarms
Things to consider working on, but will not be fully functional for Scooby 0.3. These features will be scheduled for a future release:
- "Remember me on this computer" to help users populate their accounts with shares they've accessed with Scooby in the past
- List view
- Fine-grain RPC calls
- Overlays
- CalDAV free-busy reports (MimiYin? Question: to view free-busy in Scooby?)
- Drag and drop events onto other calendars
- Mini-calendar
- Month view/Day view and print
Things we're not doing in the near-term, but necessary to meet workflow needs
- Casual Collaborator uses their email client to add to shared collections
- Unified URL for accessing share via Scooby and Chandler client – This feature has a dependancy on the development of Chandler/Cosmo.
- What elements of stamping need to be exposed in Scooby?