This is a summary of the tenets, features and assumptions for the Scooby 0.1 release.

Tenets

Proposed tenet for 0.1...

• 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
  • an individual can view their calendars in Scooby
  • talk to Cosmo via CALDAV
  • some level of editing

Assumptions

• Target audience is potential community contributor/developer, volunteer
• Will not run against Cosmo Demo ( Cosmo 0.2.6 )
• Your Scooby account is your Cosmo account (the instance of Cosmo you have setup or the snapshot of Cosmo 0.3 we are setting up)
• ?? expectations around version of Cosmo we are providing.

"In" List

• Editing
• Basic event creation (in-place creation and editing) - DONE
  • simple events with start and end time - DONE
  • all-day events - no stacking - DONE
  • multi-day events - (IN PROGRESS)
• Dragging events and resizing them in the calendar (IN PROGRESS)
• Remove events (DONE)
  • It doesn't delete the event from other calendars it may be on
  • we need to flag this as and issue with Chandler interop - talk to Morgen about what Chandler users see

• Display, but not Edit
• @ time events (start time = end time), but no special display lozenge (DONE)
• Recurring events will be displayed correctly - edits will not work
  • issue: need to figure out what the actual behavior will be (errors)
• Anytime events display as all day events (DONE)
• Overlapping events will not stagger, they will just overlap (DONE)
  • Open Issue: there may not be a way to get at events obscured by other events

• Navigation
• Week view and navigating back and forth between weeks (DONE)
• All day area (DONE)
• Event detail view (DONE)

• Managing calendars
• View a single calendar at a time (DONE)
• 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. (IN PROGRESS)
• Events created in scooby can exist on only one calendar (DONE)
  • 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)
• Allow a "public" publish (NOT IN 0.1)
  • Open issue: this came up in the use cases meeting but I am not sure where we netted out
  • MimiYin: We would need UI for this and it wouldn't be totally straightforward
  • This has been ditched for 0.1 at this point --Bobby

• Login, Logout, Manage account
  • Managing accounts will be done through Cosmo UI for 0.1 --Bobby

• Timezones
• 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) (NOT DONE)
  • have a separate discussion to figure out how it will look in Scooby
  • how do we figure out the local time?
    • the JavaScript runtime "knows" your locale --Bobby
• Events created in Scooby are in floating time.

• Talking to Cosmo -> CALDAV support (NOT DONE)

"Out" List

• Navigation
• No day view
• No month view
• No sidebar
• No calendar overlays (colors etc)
• No mini-calendar
• No jump-to-date

• Editing and creating @ times

• Managing calendars
• No publish/subscribe workflows - no dialogs to type in urls
• No import/export features
• No affordances for setting timezone of calendar
• No "public calendar"

• Calendar canvas interactions
• No staggered event overlays like chandler.
• No dragging and droppings events to add them to a different calendar
• No reconciliation of the "same event" on "multiple calendars"

• Managing events
• No creation of editing of recurring events
• No creation or special display of anytime events (date but no start and end time)
• No creation or display of alarms
• No creation or display of event status (confirmed, tentative, fyi)
• No assigning timezones to specific events

Open Issues/Questions

• At what level should we publicize this?
• Should we have any community goals? (non-code release items)
  • landing page?
  • how to help?
  • known bugs?
  • need to discuss what's reasonable with Ted
• What kind of error handling to we need, and user feedback?
• What kind of documentation do we need?
• Any specific release goals we need to have?
  • ie: package Scooby for download and install
• What kind of test plan do we need?
  • manual, automated tests?
  • what browsers do we support?
• Release process....what's the timeline ie: milestones, code complete, qa?
• What is the qa/bug triage process?