Calendar
Introduction
Westwood is the code name for a version of Chandler that is designed for use in higher education. This site is meant to collect requirements and architectural details needed to determine the appropriate scope of Westwood and answer important questions that CSG might have about Westwood.
Canoga is the code name for the first release of Chandler. OSAF still has some questions about the scope and architecture of Canoga, but generally has a plan for "serverless" group calendaring in Canoga. We do not literally mean that there will be no server, but that Canoga will be designed for individuals and small workgroups who do not want to administer a full server. In practice, a group of users may designate one Canoga instance to be a relay server, for availability of repository information. For calendars in particular, Canoga users might want to publish/replicate their calendar free-busy time to such a relay server.
For Westwood, we need to determine what is needed beyond Canoga for universities to be interested in deploying Chandler. It may be that folks are interested in deploying Westwood for calendaring in departmental groups, as long as we can support some number of users. (500? 2000?) It may be that folks are interested in trying out an "experimental" version of a Chandler server, with plans to grow it into truly scalable, highly available solution for a large university deployment. It may be that Chandler as a CAP client and/or server would be an exciting step to help making CAP a widely used standard. We would like CSG folks' help in determining what elements of this mix would make an interesting proposal. We also need to know what "showstopper" requirements would need to be met, what would prevent Westwood from being deployable. We understand that the answers will not be the same for all universities, but would like to come up with a proposal that is interesting to many.
Status
Proposal
Requirements
Architecture
Resources
Existing CSG related calendaring requirements
OSAF calendar requirements
IMAP interoperability
--
KatieCappsParlante - 27 Mar 2003
--
PieterHartsook - 24 May 2004