The platform team and the application team now meet as one desktop team. This page mainly contains links to information of historical interest (meeting notes, etc ...
Build and Release Team The Build and Release Team is responsible for the infrastructure and process required to build the source and generate the distributions for ...
Chandler Server Team (Cosmo) Note: The Chandler Server Project and Team used to be known as the Cosmo Project. The Chandler Server team is working on both the Chandler ...
Chandler Presentation and Interaction Architecture Project Project Summary The Chandler Presentation and Interaction Architecture (also known as CPIA) is the framework ...
CPIA Script CPIA Script is a scripting system for Chandler's 0.6 release. CPIA Script allows rudimentary automation of Chandler's functionality. For the 0.6 release ...
Design Team Goals The design team has 3 high level goals: 1 Define the sequence in which we build Chandler by gathering and coordinating input from engineering ...
Motivation This page attempts to clarify the roles of people in the design team We want a process that keeps Mitch and Mimi actively involved and contributing ...
Desktop Release Team Desktop Team leads meet with representatives from QA, Build and PPD every other week Thursdays at 4pm PST/PDT. At different points of the release ...
Intern Bootstrapping All our documentation is publicly available on the Wiki, including documentation for developers and other contributors. That being said, it ...
OSAF Intership Plan 2007 In order to get used to OSAF in general and their project in particular, interns can start taking a look at various documentations and things ...
Operations Team The Operations Team is responsible for OSAF organization as a whole. We monitor project progress and status, guided project and product strategy, and ...
Quality Assurance Team The QA Team is focused on testing features in Chandler Desktop and Chandler Server and defining processes to enhance the overall quality of ...
This is like WebChanges, but gives links to the "Diff" pages for the pages that have changed recently. (Yes, it'd be nice to show the actual diff text in the summaries ...
Motivation and Background In Canoga, sharing collections (e.g. a Calendar) will require a WebDAV server, as a collaboration server. See SharingNetworkArchitectures ...
Web Framework Comparison This document is intended to help us arrive at a decision as to which web framework we are going to use for the Scooby web application. ...
Welcome to the OSAF Projects wiki, a tool for collaborative work on Chandler and our other open source projects. This site is split into three main areas (which you ...
Teams Web Preferences The following settings are web preferences of the Teams web. These preferences overwrite the site level preferences in and , and can ...
WebWork Agility WebWork using JSP as a view is fairly agile when editing pages, but you have to do some configuration when adding new pages and actions though not ...
WebDAV Service Project The goal of this project is to support Chandler sharing over http, mostly by leveraging the high level zanshin protocol library. This page tracks ...