Here's a by no means definitive list of things to work on in Scooby.

Some of these things are actual "features" - stuff that the end user can see. Some stuff only an administrator would care about, and some stuff is architectural and only other devs would care about directly.

CalDAV4j

• Figure out the real name of this project (even if it's CalDAV4j)
• Separate CalDAVCalendarCollection^? API into a DAO and a manager
• Extend the Slide Client WebDAV collection API so that it can return CalDAVCalendarCollections^? and find calendar collections that are within it
• Add caching in various areas
  • cache Event UID --> Resource Path
  • cache icalendar resources w/ etags
• Add Ticket Support
• Free busy reports
• make sure previous work is caught up to the latest CalDAV spec

Timezones

• let the users set a default timezone
• be able to set the timezone on events

Multiple Calendars

• Show the "display name" instead of the user-unfriendly path.

Configuration

• Specify a URL for cosmo, as opposed to seperate properties for hostname, port, etc.

Public Calendars

• Be able to display Read-Only calendars, e.g. a public calendar for play rehearsals via a simple URL without the user having to have an account -- PieterHartsook - 28 Feb 2006

Account Creation

• Make it simple process for an end-user to create an account and login to a Scooby session -- PieterHartsook - 28 Feb 2006

Testing

• Integrate JS unit tests into Maven build process
• Write lots more unit tests - especially for CalDAV4j and scooby <==> icalendar conversion utils

Code Standards

• Have some sort of Coding standards for Java and JavaScript
• Orgaznize JS files into folders to resemble "pacakages" in Java

Internationalization

• Allow user to choose other languages from those installed.

Security

• Implement finer grained security for RPC calls - right now only auth'd users can get in, but maybe we want anonymous users to be able to do SOME webservices, like AUTH

CMP

• How about a CMP client library for talking to cosmo?