Using Chandler 0.5.m4

The project here is to test Chandler for sharing an office calendar and see if it's ready for dogfood usage. (I'm not quite using M4 I'm using head of tree Jul 14, but I'll soon go to M4 officially)

Upgrade

Although import and export works, there are still usability problems with doing sharing and upgrade.

• Sharing accounts need to be recreated after upgrade. We can probably live with this or set users up with a parcel.xml file or use the defaults.

• When you try to share the collection again it shares to a different name. The first time I shared as Office+Calendar, the second time as Office+Calendar-1. So import->export->reshare won't work right now. Instead the calendar owner has to do upgrade->subscribe and then continue editing and synching. New feature to request: prompt the user whether to overwrite the previous share or pick a new non-conflicting name. Not a dogfood blocker.

• All events are exported in one ICS file, not just the ones in the "office calendar". When they're imported, they're imported in one batch. We should eventually have the ability to export a specified collection, unless the person who's going to share the office calendar only uses Chandler for that one purpose. This is actually not a 0.6 dogfood blocker because the upgrade->subscribe workflow works better anyway.

Bug editing collection name

I tried to edit "Imported Calendar" to be called "Office Calendar". I edited and then clicked elsewhere and the change was lost.