Agenda

• Mimi - overview of process
• Discuss users for Scooby - 0.1 specifically and beyond
• Discuss feature list for 0.1 (what's in/what's out)

Notes

User & Scenario Brainstorm

• Who is going to use Scooby 0.1?
• What are they going to use it for?

• Timeframe for Scooby? Not sure maybe 3-4 mos?

• Who is going to use Scooby 0.1?
  • someone that uses Chandler and wants to access data on the web.
  • someone that doesn't use Chandler and wants to create, share and manage calendars.
  • someone that uses iCal or Sunbird and wants web access with it.
  • Chandler users that want to publish a calendar and have other users viewing using Scooby.
  • types of users
    • people living inside scooby
    • people using scooby as a suplement to another client ie: chandler
    • people who just want a simple read for a web calendar
    • plausible promise people who want to check it out but won't use it now
    • early adopters vs developers

• use cases
  • office calendar - if we are managing office cal - people can update office cal
  • public events calendar
  • resource management, holiday schedule, pto
  • you don't have a pc with you but you want to have web access to check schedule
  • sharing with your spouse
  • mitch and esther
  • access calendar on web enabled pda and mobile phone
  • not using it to manage my life

• Given current options on web that exist today, who would use Scooby as opposed to some other calendar?
  • people who want to own their data - setup own cosmo server - based on open protocol
  • people who are using Chandler 0.6 may be interesting in suplementing - early adopters
  • people who want to extend it
  • create a simple calendar and have others read...maybe read write
  • we are not trying to compete with other web calendars
  • people who want to use scooby if it's the only option if you want to control your own data

Users for 0.1

• we are leaning towards - target user for 0.1 is someone who uses Chandler to publish calendars and wants to supplement with Scooby.
• is it likely someone will use Scooby independently - probably not 0.1.

Feature List

With the above target user in mind what are the feature we need (will have) for 0.1.

• Basic Events
• basic events with start and end time
• all day events
• multi-day (?)- orginally not on 0.1 plan but calendars published using Chandler will have multi-day events. Will be a problem and perhaps this needs to be in 0.1.
• in-place creation/editing event titles
• dragging events and resizing them in the calendar
• staggering events that overlay - likely just side by side (not staggered like Chandler)
• week and day view (could do week only)
• navigation - back and forth for weeks
• jump to date - since we are not having a mini calendar

• anytime - (not in 0.1) probably not supported but need to decide what we display for calendars published using Chandler
• @time - same as above (not in 0.1)
• overlays (not in 0.1)

• Timezones
  • events translated to local time
  • no setting timezones - preserve timezone info
  • how are we going to figure out the default timezone? calendar canvas inherits the timezone of the browser

• Recurrence
  • recurrence - display only but not edit
  • cannot create recurring events
  • view recurring events - no creation, editing, deletion (read only events)
  • 0.1 stretch goal - creation but not editing - you can create the series initially but not make changes

• no sidebar
• publish and subscribe shares - consider subscribe only if our target users are chandler users only
• no displaying status icon for sharing
• probably need something for error handling
• you create a calendar and you want people to see it
• you publish a calendar with iCal - you can get a .mac url to look at the calendar

• you can create multiple calendars
• dragging onto other calendars not possible
• events can't exist on more than one calendar
• no attribute that displays what calendar it's on. (talk to Morgen/Lisa about this) - flag as issue.

• subscribing workflows
  • 1. someone who is adding a calendar to their scooby account
  • 2. someone who wants to view a cal and doesn't have an account (public)
  • 3. person who wants to export data cosmo and put it into some other tool

• publishing workflows - no supporting in 0.1
• another alternative - allow publish - option to specify public or not
• people who are unauthenticated have access to it

Issues Summarized

• multi-day events
• is "subscribe only" reasonable for 0.1
• know issue - events on more than one calendar - synching how will that work
• alarms - didn't talk about this
• event status - confirmed, tentitive, fyi - didn't talk about this

Next Steps

• type up notes - post to scooby list (sheila)
• bobby will update the specs based on these notes - use cases
• link off scooby page that has a writeup for the target user and scenarios (bobby?)
• schedule a follow-up meeting to go through remaining features
  • pub sub and login/logout
  • schedule next meeting after holidays
• schedule a cosmo 0.3 - ui discussion