---

Feature

• Read/write calendars without an account

Tasks

1. Update scooby to latest CalDAV4j w/ ticket support
   • ESTIMATE:Hours
2. Modify permissions of existing server side methods to be useable by anonymous users
   • ESTIMATE:Hours
3. Create new methods that are necessary for anonymous users/tickets
   • ESTIMATE:2 Days
   1. getEventsForCalendarAtURL(String url)? or "getEventsForCalendar(String userName, String calendarPath, String ticket)
   2. createSharingURL(String calendarPath)
   3. better yet refactor so that you have different calendar types, and you pass the calendar (er CalendarMetaData^?)
   4. modify existing code to use new calendar type
4. Refactor model classes to be in Dojo packages (necessary to get rid weird names caused by lack of namespaces like CalendarMetadata^? when should just be Calendar
   • ESTIMATE:1 Day

Total Time

• ~4 days

---

Feature

• Fine-grain security for RPC calls

Tasks

1. Create new Filter in Acegi
   • ESTIMATE:2 Day
2. Create Proxy of bean which uses filter in calls
   • ESTIMATE:1 Day
3. Configure Proxy, Filter, etc. in Spring
   • ESTIMATE:Hours

Total Time

• ~4 days

---

Feature

• Time Zones on the client-side

Tasks

1. Figure out correct data structures for timezones
   • ESTIMATE:3 Days
2. Create service methods to fetch offsets for timezones
   • ESTIMATE:1 Day
3. Do we have a central repository of timezones? If So
   1. Figure out where to store central repo (possibly in scooby?) and store them
      • ESTIMATE:2-3 Days
   2. create service methods to return them
      • ESTIMATE:Hours
   3. what to do about timezones that are not in the central repo (i.e. custom ones, ones from other vendors)
      • *ESTIMATE:1 Day
      1. basically, I'm trying to avoid writing too much timezone logic on the front-end, so I'd rather not serialize entire timezone objects, but rather just references to them so that the server can do most of the work.

Total Time

• ~8 Days

---

Feature

• Have Default Timezone

Tasks

1. Store Timezone in prefs somewhere
   • ESTIMATE:Hours
2. Modify existing code to use default timezone when creating, viewing events
   • ESTIMATE:2 Days

Total Time

• ~3 Days

---

Feature

• Allow for Editing of Recurring Events

Tasks

1. add new methods to CalDAV4j
   • ESTIMATE:2 Days
   1. updateMasterEvent() ***done I guess 1 udpateRecurrenceRule() ???
2. Add methods to client side for translating "simple" scooby recurrence rules --> iCalendar recurrences
   • ESTIMATE:1 Day

Total Time

• ~3-4 Days

---

Feature

• CalDav^? free-busy events on to other calendars

Tasks

1. Do CalDAV4j work ***MORE INFO, inlight of integration
2. create server, client methods * more info

Total Time

---