Overview

The Cosmo project aims to provide an innovative web application and a content/calendar sharing server to support collaboration with Chandler users. Chandler users will be able to share calendar collections with friends who do not use Chandler, iCal or any other desktop clients by providing them with Cosmo URLs for the collections.

Cosmo is a Java-based content/calendar sharing server with a built-in rich web application client. Cosmo is built on top of Tomcat, Jackrabbit, the Spring Framework, and Acegi Security for Spring. Cosmo is available under the terms of the Apache Software License, Version 2.0. The Cosmo JavaScript libraries are available under the same license.

Please note: The Scooby project has merged with the Cosmo project. Please refer to the discussion on the list in regards to the merge. Note older wiki pages may still refer to the Scooby name.

Download

Cosmo Sharing Server

• The current release of Cosmo is 0.4.0, released on June 8, 2006. Download it here.
• More information is available in the release notes.

Cosmo Web Application

• Download the OSAF Server Bundle and follow the integrated server bundle installation instructions. The instructions will help you install and run an integrated server bundle including Tomcat, Jackrabbit, and Cosmo.

• To install the Cosmo web application into your pre-existing Tomcat installation download Cosmo and follow the Cosmo Web-app Installation Instructions

• Read more about the OSAF Server Bundle Administrator.
• Read more about Sever Bundle Development.

Current Development

For a glimpse at our current “work in progress”:

• Cosmo 0.5

Documentation

• Developers - source code access, build instructions, specifications, client development
• Server Administrators - server installation and configuration
• Build Notes - Build environment information and release steps

• End Users - account signup, client configuration, JavaScript Libraries
• CalDAV4j Home - CalDAV4j is a protocol library. Cosmo web application needs a CalDAV library to communicate with Cosmo server side.

• Cosmo FAQ - Frequently Asked Questions about Cosmo.

Future Planning

We recently had a Cosmo Sprint Week to help us collaborate more effectively and plan for the Cosmo roadmap:

• Sprint Week Notes: Cosmo Sprint Week August 2006

Here are some current documentation on planning. There are details of the product planning which are currently being addressed.

• Long range plan
• Release for target user^? aka. A Dog Food-able release

Help Us Please!

Currently in progress

This section lists projects which are on the Cosmo roadmap. We’d like to invite you to help us please! If you are interesting in developing any of the features listed, please contact us first!

Contact

Join the cosmo-dev@osafoundation.org mailing list for discussion and answers to your questions.

You can also find us on IRC at irc.freenode.net in #cosmo. You can view the current activity by visiting the Cosmo IRC Chat log.

Before reporting a bug, please read How to report bugs in Cosmo.

Cosmo Team

• Adam Christian: Test implementation
• Priscilla Chung: Program Management/UI Design
• Matthew Eernisse: Client side development/Web UI
• Ted Leung: Project Management
• Sheila Mooney: Product Management
• Brian Moseley: Server side development architecture, all components
• Mikeal Rogers: Test implementation
• Bobby Rullo: Server side development all components
• Mike Taylor: Build, test and release engineering
• Heikki Toivonen Test implementation
• Mimi Yin: UI Design

Contributors

These are people we’d like to recognize for their help and hard work on the Cosmo project.

• Todd Agulnick: Hammer load testing tool
• Cyrus Daboo: Initial CalDAV report implementation
• Jeremy Epstien: Web UI enhancements
• Randy Letness: Hibernate storage layer (Committer)

Summer Interns 2006

• Ed Bindl
• Vinubalaji Gopal

Resources/Archive

• Server meeting notes
• Resources - List of AJAX libraries and web calendar information.
• Archives - Previous release planning.

-- PriscillaChung - 10 Sep 2006