For 0.6, we should create individual .ics files (per event) on the webdav server.

I asked about how we will support interop with Apple iCal and it seems the consensus was that Chandler should just publish the individual .ics files and Cosmo will bundle those up into a monolithic file. Since Chandler can already produce a monolithic .ics file today, I will continue to support that (via the Test menu).

Unpublishing:

There was talk about leaving tombstones around on the webdav server, perhaps in a .directory so as not to pollute your webdav directory, and potentially those tombstones could be expired after a period of time.

Synching:

We will have manually-triggered syncs (not on a 'cron job') but the goal is to have them operate asynchronously for 0.6.

Sheila, Mimi, and I will talk about specific menus/dialogs on Monday.

Account creation:

I think I heard that Cosmo will support creation of new webdav accounts via a web interface. If we have time, Chandler could access this directly so the user wouldn't even need to use the web to do it. Otherwise, we could just have a button that opens a browser to that page from the accounts dialog (and also when you share for the first time and haven't set up a webdav account).

Other comments:

Don't use UUIDs for webdav collection names, and instead allow the user to name them -- "They're heinous" was what I think I heard.

Users need to be able to specify shared collection names independently from other participants in the share.

Unified "subscribe" menu/dialog: same for chandler share and .ics file, and under the hood do the right thing.