Scooby Seven Step Program suggested by BCM:

1. Week and detail views and navigation between weeks.
2. Event create/modify/delete, timezone preference, change password
3. Month view
4. Day view, minical
5. iCalendar import/export
6. Searching local calendars. overlay & bookmarking (consume CalDAV, iCalendar-over WebDAV, RSS/Atom)
7. Ticket and sharing invitations (produce CalDAV, iMIP, RSS/Atom)

Discussion over whether we wanted to call this set of features "1.0" or "0.1". Jared and Lisa felt strongly that we should not call anything 1.0 until we've exceeded initial expectations and this is just a bare minimum. Lisa proposes that the 1-year plan described in ScoobyPlanning should be thought of as 1.0 and that phase 1/2/3 might be releases 0.1, 0.2, 0.3 (or break down even further into four releases over the course of the 1-year). BCM would strongly like to release 1.0 inside of a few months rather than a year.

After thinking about it more, I might be coming around to the 1-year == 1.0 thing. I don't see much value in quarterly dot releases tho. I'd much rather have more frequent ones each with a smaller number of related features. How about we take a look at "re-bucketing" the features from the year-one plan considering monthly releases?

-- BrianMoseley - 19 Aug 2005

Mimi will put up a wiki page with her comps.

Discussion of doing feeds for everything on Scooby

What if Cosmo was a consumer of RSS feeds? Is this more important than importing and exporting iCalendar? Upcoming.org emits these kinds of feeds already

Discussion of how important it is to build up the data available in a new system and viral expansion -- perhaps easier than doing ics import

Proposal not to deal at all with stamping and non-calendar items in first implementation.

Question about whether to support Safari, IE5.0. The question of supported browsers for Scooby is an important initial implementation decision.

Realized that a scooby instance should be running on the Cosmo demo server