r8 - 14 Jun 2007 - 10:48:24 - MimiYinYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > DraftProposalZeroDotThree

Scooby 0.3

Draft

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 in 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 make progress on things for the Chandler user, 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 raise excitement in the developer community.
  • Performance, stability and compatibility improvements over 0.2 (Technical improvements in the architecture).

Planning and Design goals

In progress

  • What elements of stamping need to be exposed in Scooby?

High-level Assumptions

  • This is to be a dogfoodable release, though the target user is very specific and not wide general use. 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

  • The criteria for success for this release is being able to view the office calendar without an account and to edit it. This may take up to 4-6 weeks to meet goal.

Features

This list stil needs to be reviewed with the Scooby development team. Since we are in the planning phase, we are currently revising this list.

Casual Collaborator

  • View calendars without an account
  • Jump to date
  • NEW: Send "N"otifications of newly created events/edited events (aka PTO announcements) - does not have to be implemented via Stamping
  • List view of event data
  • Email events to the calendar on Cosmo

Chandler User reading their Calendars on Scooby

  • NEW Viewing all of my Chandler calendars on Scooby (regardless of whether or not they're shared, published, subscriptions)

  • Account creation in Scooby

  • Sidebar navigation and overlays
  • View @time and anytime events
  • View alarms

  • Basic user preferences
  • Timezones
    • Store default timezone
    • Change timezone of calendar canvas
    • Edit timezone on specific events

  • Subscribe and Publish workflows
  • Import/Export .ics files

  • Continue visual tweaks

Stretch goals

  • CalDAV free-busy reports (Question: viewing them in Scooby?)
  • Fine-grain RPC calls

  • Overlays
  • Drag and drop events onto other calendars
  • Mini-calendar

-- PriscillaChung - 05 Jun 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r8 < r7 < r6 < r5 < r4 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.