Chandler 0.6 is a significant milestone for us here at OSAF. We are delivering experimentally usable software into the hands of users for the first time. This will hopefully allow us to start building an active user community as well as collect valuable feedback as people start to use the product on a day-to-day basis.
We defined experimentally usable calendar in terms of what it would take to get everyone at OSAF to start using the Chandler calendar, either for personal calendaring or collaborative group calendaring. This meant, not only making sure we had the right set of features, but also required significant investment in UI polish and performance. We have also made significant inroads into interoperability by supporting read-only and read-write sharing using our open source CALDAV server, Cosmo.
Although our focus in 0.6 was calendaring, we continued to make progress on other important areas of the application: developer platform, i18n, accessibility and expressing Chandler's unique information architecture in the UI to name just a few.
We've built an infrastructure to use localized strings and dates in the UI. We've done significant research into accessibility guidelines and keyboard support. We're addressed key problem areas in the content model and developed a Python schema API. To boost our own productivity, we've also built a testing framework to create and run test scripts against Chandler.
Other feature areas of Chandler, such as email and tasks are still under very early development and do not yet support a number of planned functions and features.
See next sections for further details...
Users should make sure they have the minimum disk space requirements listed below when running Chandler.
[top]
The following are the primary principles by which we prioritized feature work for 0.6.
[top]
This release builds on our current infrastructure to support individual and collaborative calendaring tasks for small workgroups. In 0.6, you should be able to...
[top]
Users should back up their calendar data on a regular basis since the Chandler repository may be deleted if you install new versions of Chandler in the future. You can do this by selecting File->Import/Export->Export Events as iCalendar. If you are managing multiple calendars, you will need to export each calendar individually by selecting it in the sidebar and choosing Export Events as iCalendar.
Likewise, choose File->Import/Export->Import iCalendar Data for importing iCalendar files into Chandler. Likewise, you will need to import multiple files if you are managing multiple calendars. Upon import, the user is given the option to import into an existing calendar or create a new one.
[top]
In 0.6, we have extended sharing so that users can share read-only and read-write calendars using our open source CALDAV server, Cosmo. This is implemented by generating URL tickets, one for read-only sharing and a second for read-write sharing. All sharees will access the share with the same read-write or read-only URL. Once created, these URLs can be passed around to anyone.
Using the menu item under the Collection menu, users can publish and subscribe to calendar URLs. Once a share has been published or subscribed to, we also support the ability to unpublish shares and retrieve both sharing URLs using the menu items or the Manage Share dialog. If upgrading to a new version of Chandler has deleted your current repository, use the Collection->Restore previous shares menu item to re-establish previous shares.
We have optimized the 0.6 workflows to run against Cosmo but in theory, users should be able to share with other WebDAV and CALDAV servers. We also support the ability to share read-only calendars with non-Chandler users via Apple iCal. As a part of our interoperability goals, we encourage users to try sharing with other servers and report any issues/bugs they encounter. Details on how to do this can be found on the Give us feedback page.
OSAF is hosting a calendar sharing test service using Cosmo. This service is available for public calendar sharing at https://osaf.us/cosmo/ cosmo-demo.osafoundation.org:443 (use SSL). This service is being provided to test calendar sharing and is not intended to be a fully-supported production service at this time. At the current early stage of development, the service may be slow, unreliable, or simply not available, and data on this service is likely to be lost or erased. We encourage users to try out this service and report problems in order to help us both scale and stabilize Cosmo going forward.
In order to share, you first need to setup an account on the Cosmo server. In Chandler, go to File->Accounts. From the Accounts dialog, select Sharing account from the list of accounts on the left. A default account has been setup for you which points to our public server, https://osaf.us/cosmo/ Cosmo-Demo. Click on the Sign up for an account button to create a username and password on the server. Then come back to the Accounts dialog to fill in your account information. Make sure to include the path to your account: home/username.
Alternatively, you can go directly to the server signup page at...
http://cosmo-demo.osafoundation.org/chandler06_signup.html [NB: as of Chandler 0.7alpha4 milestone the cosmo server location has changed to http://osaf.us/signup]
If you have your own WebDAV server, you can add this account by clicking on the Create new account drop-down and selecting Sharing WebDAV. You can of course setup your own version of Cosmo as well. To find out more about the Cosmo project, go to the home page...
http://chandlerproject.org/Projects/CosmoHome
[top]
Although we want to see users experimenting with the calendar, it is not without some bugs. I full list of known issues can be found at...
http://chandlerproject.org/Chandler/ZeroPointSixKnownMajorBugs
[top]
We will be maintaining a troubleshooting page that contains work arounds for known bugs. We encourage members of the community to edit this page directly as they encounter issues.
http://chandlerproject.org/Documentation/ChandlerTroubleShooting
[top]