What are some architectural issues we'll want to keep in mind up front -- hard issues?

• Support for timezones -- select the view tz
  • If we don't display tz's correctly then there will be interoperability problems with Chandler on a shared data set
• Support for recurrences -- same interop issues.
• Support for different date/time formats selected by user (DD/MM/YY vs MM/DD/YY and others)
• I18n and localizing: language should be a user preference in the long run
• Event status
• reminders

Discussion on floating events (no time scheduled yet) -- difficulties for i18n.

Mimi drew the week view proposed for Scooby:

• minical, eventually with busy bars
• Month label and navigation forward and back
• Sidebar area for switching between calendars

How are devs going to get data into Scooby to test/work with? As soon as Scooby pulls calendar data from Cosmo (using local JCR style interfaces, not CalDAV or WebDAV), then Chandler can be used to populate a calendar.

Discussion of Chandler's approach to hetergeneous collections/shares; filtering by kind...