r1 - 10 Apr 2005 - 16:03:04 - SheilaMooneyYou are here: OSAF >  Journal Web  >  ContributorNotes > SheilaMooneyNotes > RecurrenceNotes20050408

Summary

Phone meeting to discuss recurrence and calendar import/export plan and goals for 0.6 and find out the status of the current discussions.

Attendees

Sheila and Jeffrey

Notes and Decisions

1. Sheila and Jeffrey discussed current bugs with Calendar import/export that would be addressed during 0.6 cleanup phase.

  • There is a bug importing some large calendars. Mimi was having a problem with this. Jeffrey has fixed this bug and it's currently awaiting a new build.
  • Jeffrey will work on a fix so that importing a calendar creates a new collection on the sidebar. Jeffrey indicated this should be fixed in the next couple of days.

2. We discussed specs for 0.6 and what would be required. We identified that we would need 2 specs, one for Import/Export and one for Recurrence. It was decided that Sheila will own creating these 2 specs and getting contributions from Alec and Jeffrey. The Import/Export spec would deal the current behavior in the app as well as the modifications to deal with other types of events ie: multi-day, anytime that we use in Chandler. The recurrence spec will detail the modelling and architecture for the 0.6 recurrence goals including what UI workflows will be supported.

3. First initial draft of both specs will be targetted for Monday May 18th.

4. Jeffrey and Sheila discussed recurrence goals for 0.6 in more detail. We decided that we wanted to focus on the following scenarios and simplifying assumptions.

  • Recurring events on imported calendars will show up in Chandler.
  • We will not try to map imported recurrence algorithms to any UI in Chandler. We will indicate that the recurrence algorithm is "custom" or "imported".
  • We will preserve the recurrence rule so that when we re-export the calendar, it is maintained.
  • To simplify 0.6, If you delete a recurring event, it deletes the entire series. We can implement more complicated scenarios later.
  • To simplify 0.6, if you change a recurring event, it changes the entire series. We can implement more complicated scenarios later.
  • You will be able to create recurring events in Chandler with a very simply selection of rules, Daily, Weekly, Monthly, Yearly. We can add more custom and complicated scenarios for 0.7. This will keep the required work for the detail view very minimal for 0.6.

5. Jeffrey and Sheila decided to setup a regular weekly meeting to touch base on process and review the spec.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.