---

Feature

• Navigation: Multiple Calendars - Show the display name instead of path name (no calendar overlay, but be able to switch between different calendars)

Tasks

1. Add new Calendar or CalendarMetadata type to model on Server
   • ESTIMATE:Hours
2. Add new Calendar or CalendarMetadata type to model on Client
   • ESTIMATE:Hours
3. Modify ScoobyService^? method to return CalendarMetadata instead of String
   • ESTIMATE:Hours
4. Modify front end code to consume CalendarMetadata's instead of Strings

• • ESTIMATE:Hours

Total Time

• ~1 day

---

Feature

• Infrastructure: CalDAV4j: Figure out the real name of this project (even if its CalDAV4j)

Tasks

1. Bring it up on the mailing list, see what people say
   • ESTIMATE:Trivial
2. If we come to a decision to change it, change all references to caldav4j to XXX
   • ESTIMATE:Hours

Total Time

• <1 day

---

Feature

• Infrastructure: CalDAV4j: Separate CalDAVCalendarCollection^?? API into a DAO and Manager

Tasks

1. Determine which methods go where
   • ESTIMATE:1 Day
2. Move methods
   • ESTIMATE:Hours
3. Document
   • ESTIMATE:1 Day
4. Fix Scooby if necessary
   • ESTIMATE:Hours
5. Fix Unit tests
   • ESTIMATE:1 Day

Total Time

• <2.5 days

---

Feature

• Infrastructure: CalDAV4j: Extend the Slide client WebDAV collection API so that it can return CalDAVCalendarCollections^?? and find calendar collections that are within it.

Tasks

1. Extend the class, overide method which returns directories to return CalDAVCalendarCollections^?
   • ESTIMATE:1 Day
2. Move calendar discovery code from scooby to here
   • ESTIMATE:hours

1. unit tests

Total Time

• ~2 days

---

Feature

• Infrastructure: CalDAV4j: Add caching in various areas (cache Event UID --> Resouce Path, cache iCalendar resources with eTags)

Tasks

1. Research different caching implementations
   • ESTIMATE:day

1. Determine best places to cache (already know a couple of low hanging fruit...)
   • ESTIMATE:.5 days

1. Figure out what parameters should be configurable
   • ESTIMATE:hours

1. implement caching in some places

• • ESTIMATE:2 days

Total Time

• ~1 week

---

Feature

• Infrastructure: CalDAV4j: Add Ticket Support

Tasks

1. add appropriate structures requred for MKTICKET to the caldav4j model
   • ESTIMATE:hours

1. add appropriate structures requred for DELTICKET to the caldav4j model
   • ESTIMATE:hours

1. Implement MKTICKET method
   • ESTIMATE:hours

1. Implement DELTICKET method
   • ESTIMATE:hours

1. Add method at collection level to do support ticket create, deletion
   • ESTIMATE:.5 days

1. Add method in manger for ticket discovrey
   • ESTIMATE:.5 days

1. extend httpclient, or collection or something to allow tix authentication
   • ESTIMATE:hours

1. unit tests
   • ESTIMATE:day

Total Time

• ~1 week

---

Feature

• Infrastructure: CalDAV4j: Free/busy reports

Tasks

1. Extend XML data model * ESTIMATE:.5 days
2. extend REPORT to handle new type of report * ESTIMATE:.5 days
3. Add appropriate manager methods (get free busy) * ESTIMATE:.5 days

Total Time

• ~2 days

---

Feature

• Infrastructure: CalDAV4j: Make sure previous work is caught up to the latest CalDAV spec

Tasks

1. add CALDAV:timezone to queries
   • ESTIMATE:1 days
2. add addded preconditions
   • ESTIMATE:.5 days
3. read about guidelines for finding calendars
   • ESTIMATE:.5 days
4. add property CALDAV:calendar-timezone on calendar collections.
   • ESTIMATE:.5 days

Total Time

• < 1 week