r9 - 30 Oct 2006 - 17:13:43 - PieterHartsookYou are here: OSAF >  Projects Web  >  ScoobyHome > ScoobyZeroDotOne
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.1

The overall goal of Scooby 0.1 is to put in place the major application architecture pieces in order to provide enough of a basis to generate interest and have serious volunteers start contributing to the project. The Scooby project will be released and tightly integrated with the release of Cosmo 0.3.

Download

0.1 Tenet

  • "Initial" web based access to calendar data for Chandler users
    • get a first release of Scooby out the door to validate the project and start to build a community
    • don't worry about completeness of functionality or polished UI.
    • an individual can view their calendars in Scooby - talk to Cosmo via CALDAV
    • some level of creating and editing events

High-level Assumptions

  • Target audience is potential community contributor/developer, volunteer. No target user will be identified since this is not intended on being a "usable' release.
  • Will not run against Cosmo Demo ( Cosmo 0.2.6 )
    • Scooby depends on work currently being done for Cosmo 0.3.
    • Scooby will be bundled with the release for Cosmo 0.3.
  • Your Scooby account is your Cosmo account (the instance of Cosmo 0.3 you have setup)

Status

Features

Feature selection is extracted on the one-year Scooby plan -- this release is probably less than a quarter of that plan, and only part of Phase 1, because we want to show people something early.

  • Editing
  • Basic event creation (in-place creation and editing in event detail area)
    • simple events with start and end time
    • all-day events - no stacking
    • multi-day events

  • Dragging events and resizing them in the calendar
  • Remove events
    • It doesn't delete the event from other calendars it may be on

  • Display - no editing
  • @ time events. You can create these events in the detail view by setting start time = end time but there is no special display lozenge as in Chandler.
  • Anytime events display as all day events
  • Recurring events will be displayed correctly - edits will not work correctly
  • Timezones will display correctly in the detail view, but user cannot change the timezone
  • Overlapping events will stagger Overlapping events are currently on top of each other.

  • Navigation
  • Week view and navigating back and forth between weeks
  • All day area Not currently available on 0.1
  • Event detail view
  • Jump to date field Not currently available on 0.1

  • Managing calendars
  • Published calendars and Subscriptions as well
  • View a single calendar at a time
  • Pull-down to switch calendars
  • When you run Scooby there is a default calendar created on your behalf. You cannot create new addtional calendars in Scooby. View multiple calendars created using Chandler but only one at a time.
  • Events created in Scooby can exist on only one calendar (This issue has not been resolved for 0.1, open issue)
    • this one is confusing because I can have 2 chandler calendar that has the same event on more than one calendar
    • assume there will be no affordance to indicate this (what calendar is on)
    • what happens when I modify this event in scooby (on one of the calendars)
  • Login, Logout, Manage account
    • Managing accounts will be done through Cosmo UI for 0.1

  • Timezones (Timezone issues not settled on 0.1, open issue)
  • All events are translated into local time and original timezone information is preserved (ie: if system TZ=PST, if my event is 10:00am EST, it displays as 7:00am PST)
    • Events created in Scooby are in floating time.

  • Talking to Cosmo -> CALDAV support
    • view calendars published on cosmo

Issues

  • What happens to update events that are on more than one calendar?
    • Use Case: I am viewing my Chandler work calendar in Scobby and I modify an event that is on more than one calendar. What happens when I sync? We need to flag this as an issue with Chandler interop and talk to Morgen about what behavior Chandler users will see.
  • If we don't handle overlapping events there may not be a way to get at events obscured by other events.
  • Recurring events: We don't know how recurring events will behave in Scooby and what will happen when the user makes changes. Need to figure out what the actual behavior will be and log all those use cases. We anticipate errors if users try to edit recurring events in Scooby...this is probably ok for 0.1.
  • Timezones: We still need to work out all the detailed timezone workflows in Scooby. They may not be displayed quite the same way as in Chandler.

Specs and Proposals

Spec Name Owner Status Tasks Server Time Estimate Client Time Estimate
Basic Calendar Matt Implementation In Progress bugzilla 14 days
Confidence : Fair
28 days
Confidence : Fair
Recurrence Bobby Implementation In Progress bugzilla 3 Days
Confidence : Fair
 
Java CalDAV? Library Bobby Planning bugzilla 5 days
Confidence : Fair
 
Authorization and Authentication Bobby Implementation in Progress bugzilla 5 Days
Confidence : Fair
 
TimeZones Bobby Implementation in Progress bugzilla 1 day : Confidence High  

See week view wireframes

Features Tabled for Future Release

Spec Name Owner Status Tasks Server Time Estimate Client Time Estimate
Overlay (mulitiple calendars) Matt Planning bugzilla N/A (Pending more design info)
Confidence : Nil
Searching Events Matt Planning bugzilla 2 days
Confidence : High
2 days
Confidence : High
Tickets/Sharing Bobby Planning bugzilla 3 Days
Confidence : Fair
 
Public Calendars Bobby Planning bugzilla 3 days : Confidence High  

Meeting Notes

(Weekly meetings are now scheduled every Wednesday at 1:30PM PST)

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | 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.