Summary

Mimi and Sheila met to brainstorm subset of recurrence features to support in 0.6. We need to get some input from Engineering before putting together a formal proposal. A summary of our discussion and musings is as follows.

Notes

What workflows do we need to support?

1. Import a calendar with recurring events and have them displayed accordingly.

1. Will there be a visual indicator in the calendar view or summary table view that this is a recurring event? Mimi does not think this is necessary for 0.6. b. How is the recurrence indicated for imported events? Could we potentially map these items to our Chandler recurrence? What do we do if the imported item recurrence is more sophisticated that want we support in the UI?

2. Export a Chandler calendar with recurring events.

1. What happens to events with recurrence that we don't support when we export those.

3. Publish and subscribe to a calendar with recurring events.

4. A user can create a new event or modify an existing event and use the detail view to specify the recurrence parameters. We are thinking about very simple options.

1. None b. Daily c. Weekly (on this day of the week) d. Monthly (on this date - if that month doesn't have this date ie: 31st, then there would be nothing for that month) e. Yearly (on this date - if we pick Feb 29th, it would only appear every 4 years)

5. Delete an event that is recurring.

1. Do we delete all of them or just a single one. Would probably like to minimized the UI required to do this for 0.6 if possible.

6. Modify a recurring event to be non-recurring.