We have just moved all the OSAF IRC channels, bots, channel logging and other services from irc.osafoundation.org to irc.freenode.net

The channels available on irc.freenode.net are:

• #chandler - The Chandler project
• #cosmo - The Cosmo project
• #scooby - The Scooby project
• #osaf-notices - This is an informal channel for socializing. It is also the destination for useful output from the soup IRC bot, including realtime notifications of changes to the OSAF wikis.

Please connect to this new server from this point on. Click here for instructions on how to join the OSAF IRC chats and how to access the transcript logs from previous sessions.

We have just moved all the OSAF irc channels, bots, channel logging and other services from irc.osafoundation.org to irc.freenode.net

The channels available on irc.freenode.net are: * #chandler - The Chandler project * #cosmo - The Cosmo project * #scooby - The Scooby project * #osaf-notices - This is an informal channel for socializing. It is also the destination for useful output from the soup IRC bot, including realtime notifications of changes to the OSAF wikis.

Please connect to this new server from this point on. Click here for instructions on how to join the OSAF irc chats and how to access the transcript logs from previous sessions.

The latest status overview, with quick high points from every project and overall highlights, can be found here.

During last week’s sprints I was asked to see how easy it was to import mail into Chandler from a local mailbox. Thanks to Python’s mailbox and email packages, the mailbox parsing was trivial. Similarly, Chandler’s domain model can represent email items and has a number of APIs that make creating such items from a raw email string very easy.

Read the rest of this entry »

It’s been a while since I posted anything on the chandlerdb blog. That is now corrected with a few new posts about repository backup, recent performance improvements and version purging.

Chandler’s repository is versioned. Like a subversion source code repository, changes to items are saved into the repository as coherent versions. This enables to later merge together changes that occurred in different threads or processes instead of serializing changes by locking resources.

Read the rest of this entry »

In the run up to the Chandler 0.6 release, a lot of performance improvements were made to the repository codebase. Many areas of Chandler were also reworked somewhat to make better use of performance critical repository features.

Read the rest of this entry »

Chandler’s repository is intended to store a lot of data that one cannot afford to lose. It should come as no surprise that doing regular backups is strongly recommended. There are a few repository APIs, currently accessible from Chandler’s “Test” menu or from Chandler’s --restore command line option, that make it possible to backup and later restore a repository’s files.

Read the rest of this entry »

Earlier this week I represented OSAF at the 4th CalConnect Interop. This entailed spending a day and half in a room with a bunch of other calendaring vendors, trying to make sure that our software works with theirs.

Most of the work I did involved CalDAV client-server testing. Besides OSAF’s own Cosmo, there were servers from Novell, RPI and Oracle to test against. It turns out that these servers work sufficiently differently from ours that they exposed interesting and useful bugs in our CalDAV client implementation.

Two other CalDAV clients besides Chandler were represented: Mozilla’s Sunbird client, and Evolution (with CalDAV plugin). Brian Moseley had set up a machine at OSAF where he could debug a test server, and was available on IRC to help diagnose problems. Both Evolution and Sunbird use a different method of downloading events from a CalDAV server than Chandler, so Brian (with the help of Bobby Rullo) was able to chase down a couple of good bugs.

In the remaining time, I was able to squeeze in some testing of interoperability of ICalendar (.ics) files with other vendors, including Novell Groupwise, EVDB and Trumba. This, too, turned up a couple of interesting bugs.

All in all, it was very helpful to devote some time to interoperability, especially in an environment where you can discuss issues with other developers, and, in some cases, resolve or work around them. Thanks to CalConnect for organising, and to Novell for hosting us in their lovely Executive Briefing suite.

Since people new to the project may be unaware, I thought I would write up a page describing the current state of Chandler’s embedded webserver, along with how to add your own servlets and set up passwords. Please see the ChandlerWebServer Wiki page for details.