Cosmo Roadmap

Cosmo 0.4 (tentative release date: early June) is a short release will focus on enabling free/busy reporting for Chandler 0.7 and a few minor bug fixes.

Beyond Cosmo 0.4, we have a number of things we would like to do, but we're in the process of reworking the roadmap and hope to publish it soon.

Here's a partial list of candidates for future releases:

• Deeper support for Chandler ecosystem sharing
• ACL support
• principle namespaces
• CARDDAV support
• JMX extensions for monitoring
• Usability improvements to the Administration Console
• Support for load balancing, clustering, backups

The content below is woefully out of date. We're working on an updated version of the roadmap, but its not ready yet. More information to follow very soon.

Development of the Cosmo server will roughly follow the Chandler milestones, although we anticipate occasionally making releases between milestones. Many but not all of the server's requirements come from specific Chandler milestones. Requirements for the Kibble and Westwood milestones are extremely fuzzy for now, and some of the planned server releases may be further broken up as we get more of an idea how difficult some of these tasks may be.

Over-the-horizon features

These features aren't in a schedule but are roughly within the possible Cosmo goal set.

• Full CalDAV scheduling implementation
• Event publishing features
• Migration of data from other calendar servers/systems

Wishlist projects

These are projects that somebody new could pick up or possible future summer-of-code projects

• Make it possible to do dynamic recurrence expansion to handle time-range requests in the future
  • This may be a research project. There has to be some balance between expanding recurring events pre-emptively (storing instances for 2006-2008) so that queries are fast, and the flexibility of doing dynamic recurrence expansion so that queries can be made in the far future or the past. One can imagine having two ways to expand events: the algorithm for dynamic use would be optimized to return a quick "no" if a recurring event had no instances in the queried time period. Another possible approach is to annotate recurring events with "hints" about which time periods might include instances of this event. (e.g. no time periods ending prior to May 2005)

• Atom in Jackrabbit
  • We've got some Cosmo AtomPub^? support but surely other people using Jackrabbit would be interested in this eventually. Our support could be broken out as a more general-purpose module.

• 3rd-party Identity integration
  • YADIS or some other system could be used so that people wishing to share a calendar on Cosmo wouldn't have to sign up for a new account (identity) and new password. Instead they could provide their identity from a 3rd party identity provider each session. The biggest barrier to this is HTTP-Auth work which is only starting in the IETF, but in the meantime a hack might be that the user could issue themself a write-ticket to be able to use CalDAV.

Out of scope for Cosmo

• Email server (IMAP, POP and SMTP support)

-- BrianMoseley - 22 Feb 2005