Chandler 0.7.6 features the ability to keep multiple items open in separate windows. You can access this feature by clicking on the icon in the upper right hand corner of the item details pane or by going to View>>Separate Item Details. (You can also select an item and hit Ctrl-I on Windows/Linux or Apple-I on Mac.)

User Andre Mueninghoff has already been making use of this new feature for a few weeks now, helping us track down bugs and providing feedback. Here are 2 uses he’s found so far:

Andre keeps two items open all the time in separate windows:

The first is something he calls a “Bucket” item:

…to capture those random thoughts and bits of information that appear during the day.

The second is a GTD Projects List. Andre consults this list repeatedly throughout the day. In his words:

This saves me the trouble of having to leave the Chandler item I’m working with, find the GTD Projects List item, and then find my way back to the original item.

Laszlo Systems announced that they have chosen Chandler Server as the back end for a new calendar application they are deploying by as part of their Webtop suite.

In their recent blog post, Chandler Server came up in the open source credits.

“We liked the fact that we could use the CalDAV standard, and that Cosmo supports publishing a CalDAV collection as a single .ics file that can users can subscribe to via external calendar clients. Also, in evaluating scalability, we found that Cosmo performance outpaced other solutions.”

It’s great to see other people using Chandler Server and getting value out of it. We are happy to have them as an open source partner!

The Chandler Project is pleased to announce the 0.14.2 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This is a bugfix release to update the visual treatment on the login page and add a new widget specific Javascript build.

Chandler Server 0.14.2 is available for download as a ready-to-run bundle at:

http://chandlerproject.org/serverdownload

and the source code is available from subversion at:

http://svn.osafoundation.org/server/cosmo/tags/rel_0.14.2

Send us feedback at the open mailing list (no subscription required):

chandler-users@osafoundation.org

We look forward to hearing from you!

In the early days of free e-mail accounts, I lived in a close-knit rural community. My close friends and I thought e-mail was the best thing ever invented, and we’d make all sorts of plans entirely by e-mail. What could be more simple and effective? It turned out almost anything.

While my closest friends all checked their e-mail hourly, many of my other friends had work that wasn’t sitting in front of a computer. Many of them got e-mail accounts only grudgingly, and checked them maybe weekly. I was constantly wasting time expecting people to have read my email proposals. Eventually, I learned that I had to kill trees if I wanted people to hear what I had to say.

Applications, even paradigm shifting applications, are only useful if you use them. Obvious though this may be, it’s critical in determining whether a tool is valuable in practice.

In my day to day use of Chandler, I often close the application down and forget to open it up again. When I want to go check whether I can schedule an event, or find some other specific piece of information, I go and load Chandler, no sweat. But when I have an idea or something I need to remember to do, I often just create an (electronic) sticky or emacs file or send an email to myself to track it.

This is a hassle! I love Chandler’s organization of my calendar, random thoughts, and tasks, especially the ability to set something to come back to my attention later. But I’m not getting us much advantage from this as I’d like, because I still have so many tasks not in Chandler. The truth is, I don’t need all that organizational power most of the time. Often, I’d just like to quickly jot down a task.

To make it easier for everyone in my position to add tasks to their Chandler collections, today we’re announcing Chandler Quick Entry for iGoogle. OK, maybe this doesn’t make anything easier for Nepalese babies. But hopefully it’ll be helpful for people who use Chandler Hub and iGoogle.

If your homepage is set to Google and you’ve never used iGoogle before, it’s worth a look. You can quickly add a few gadgets with blog feeds, news, or whatever else you’re into. And, now, you can create notes and quickly send them to Chandler Hub. If you use Chandler Desktop to sync your hub collections, your new note will appear in Chandler the next time it’s open and syncs.

Give it a try and let us know what you think!

 [Note: at the moment, you can’t use Google’s Directory to add the gadget, the directory contains an old, non-functional version of the gadget.  You need to click on the image above to successfully add.]

While Chandler was originally conceived as a general purpose personal information management tool, we realized early on that sharing and collaboration, particularly small-group collaboration needed to be integral to any effective personal information manager.

It’s an exciting time to be in this area of software development. Software companies are finally turning their attention to small organizations, businesses and households; groups that are less structured than traditional corporate environments.

Chandler falls into this new category of personal and collaboration tools for small, loosely structured workgroups. There are 2 significant ways in which Chandler departs from enterprise-scale collaboration tools:

One. Traditionally, many collaboration tools have been structured around “clients” and projects, which were presumed to have start and end dates and concrete deliverables, that once delivered meant the project was complete. Delivering for each client was assumed to be a relatively “straightforward, process-oriented” affair that could be mapped out in “workflows” that remained constant from one project to the next.

By contrast, Chandler assumes that new projects (or tasks) will continuously emerge from existing projects. Old projects change or become irrelevant before they’re even begun. As a result, “work” becomes a never-ending, ever-changing procession directed towards a higher-level goal. To be sure, deadlines and milestones exist along the way. But they are markers in a continuous progression as opposed to tidy endings to bounded projects.

In short, Chandler is designed for groups that are constantly re-inventing what it is they do and how they do it.

As a result, building and maintaining project and workflow structures for managing and organizing such a constantly changing morass of tasks, dates and unresolved issues just doesn’t seem worth it.

Instead, Chandler is intended for users who are actively looking for something that lets you stay “organized” at their own pace. They specifically don’t want to feel like they’re being pressured to set deadlines they’re not ready to set. They don’t want to be harassed about tasks you entered but no longer need to do. In other words, Chandler users want a “Don’t call me, I’ll call you.” kind of tool.

Two. Traditionally, collaboration tools have focused on coordinating hand-off of information and shared resources (documents, media, etc) so that each member of the team has access to what they need in order to focus on their work.

By contrast, Chandler assumes that ownership of responsibilities is shared and passed from one member of the team to another with relative fluidity.

As a result, Chandler sharing isn’t modeled as a fileshare that gives everyone access to everyone else’s work. Instead, Chandler collaboration assumes that people need help working on the same thing together.

Sharing in Chandler is less about “watching” other people’s task lists and calendars and more about sharing a group collection and calendar where individual tasks are passed around or simply worked on in parallel by multiple people.

This doesn’t mean that “personal” collections can’t and shouldn’t be shared with others. It’s more a matter of “What is Chandler’s special sauce?” when it comes to collaboration.

This fluidy in collaboration also explains why Chandler is first and foremost a personal tool with built-in collaboration as opposed to straight-on groupware.

Our belief is that the line between “my work” and “your work” and “our work” is now sufficiently blurred such that tools that draw a hard line between personal and group task management simply erect unecessary hindrances that break common workflows.

Note: This is yet another way in which Chandler aspires to mimic email. People see email first and foremost as a personal tool. But fundamentally, email is about communicating and working with others. Nevertheless, the collaboration aspect of email is framed as an extension of the personal.)

It’s time to come out with another in our series of monthly-ish Chandler Desktop releases. Chandler Desktop 0.7.6 will contain the following two major features:

1. Separate detail view windows: This has been requested fairly often in the past. We’re nailing down the final UI for opening a new top-level window for a given item, but otherwise the code is done and has been checked into trunk. There will probably be a more detailed post at some point about using this feature: I personally have found it handy to use separate windows for items I update regularly but sporadically, like my grocery list.
2. Automatically checking for updates: I’ve added some data on our website to enable Chandler Desktop to check periodically (weekly is the default) for new releases. The app will pop up a dialog that tells you what the new release is, and allows you to click a button to download it in your web browser.

Besides this, there are quite a few bugs addressed in 0.7.6. You can find the full list here.

[May 16, 2008] Updated to Add: It’s out now … Download it here.

[May 16, 2008] Also Added: For more on separate detail views, see this post.

I was mucking around on wikipedia last night and ended up on the Open Source Applications Foundation entry page. It’s been a while since I looked at this and I was surprised how out of date the information was, particularly since the restructuring in January. Although I love the charming picture of Mitch Kapor, Katie Capps Parlante is now our acting President.

I also looked at the Chandler entry and found it a bit more current. It does show the new logo although the latest version is listed as 0.7.4.1 and not 0.7.5.1. The screenshot could also be updated to show the new simplified UI.

I hesitate to update these myself, as I know that Wikipedia has a NPOV (neutral point of view) policy and I fear being biased. If anyone wants to help us out, updating the entries to reflect the current state of the organization and the project would be much appreciated!

From a recent post by Lisa Hoover on “Open Source Apps for Homeschoolers”:

Juggling my schedule and that of three young learners — plus all their extra-cirricular activities — isn’t easy. I need to be able to look at a calendar and tell who needs to do what (and who needs to be where) at a glance. To stay organized I use Chandler, an app so feature-rich that I don’t even use it to it’s fullest capability. I love the way it color codes whatever I throw at for easy sorting and retrieval. It also keeps a running to-do list for me, and it’s a snap to create new events, messages, and tasks.

The idea of a “running to-do” list is interesting. To me, it sounds like a task list that is unpredictable, always changing.

When building a task manager, it’s tempting to go down the path of developing features to map out projects with complex task landscapes: dependencies, time estimates, urgency and priority rankings, start times and end times, intermediate milestone dates, etc. There are certainly projects that require this kind of project / task manager (and as an open source project, Chandler can be extended to support such functionality).

However, the kinds of task lists Chandler serves best are precisely “running to-do lists” (or at least my understanding of what a “running to-do list” is.) Task lists that change so quickly, it’s not worthwhile to invest a lot of time inputting and maintaining a lot of meta-data about your tasks. Instead what’s important is a snappy way to get stuff out of your head and onto the task list, plus some basic affordances for tracking (Triage Status + Tickler Alarms) and organizing (Collections + Calendar) your tasks, so they don’t just pile up into one big, insurmountable mountain of to-dos.

The Chandler Project is pleased to announce the 0.14.1 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This is a bugfix release to patch a bug in which users with non-url-safe characters in their usernames or passwords could not log in to the Web UI.

Chandler Server 0.14.1 is available for download as a ready-to-run bundle at:

http://chandlerproject.org/serverdownload

and the source code is available from subversion at:

http://svn.osafoundation.org/server/cosmo/tags/rel_0.14.1

Send us feedback at the open mailing list (no subscription required):

chandler-users@osafoundation.org

We look forward to hearing from you!

The bugs fixed in this release include:

• #11956: Calendar ui double-escaping authentication request

As promised, here is a specific scenario illustrating how Chandler can help to reduce and simplify the information in your life.

Use Case: Setting up and Following-thru on a Meeting.

Edit, Evolve, Send and Re-Send the same item of information as your task to schedule a meeting turns into an invitation turns into a scheduled meeting on your calendar turns into an agenda list turns into meeting notes.

A simple meeting can often generate a dozen or more separate bits of information for everyone involved; bits of information that each person then needs to manage independently.

• You create a task item to schedule a meeting;
• Send out a separate email message to invite others to the meeting;
• Follow-up with a whole thread to work out the meeting agenda;
• And add the meeting to your calendar.

• As the meeting shifts around and the agenda changes (all information that arrives via more email messages), you update the event on your calendar.

• During the meeting, you write up notes and send them out in yet another email; which in turn
• Prompts responses as others amend your meeting notes in follow-up emails

When you go back to look for the definitive record of what was discussed and decided at that meeting, where do you start? There are so many bits to collate and reconcile into a “single source of truth”.

By contrast, in Chandler you have 1 item that you edit and amend over time with changes and new information.

Your task to schedule a meeting can be sent out as an invitation email and then put on your calendar once everyone has agreed to a suitable time. In parallel, you can pull together a meeting agenda on that same meeting event item. During the meeting, you can take meetings notes, again in the same meeting event item. All the while, you can send and resend the same task/event item to notify people who aren’t sharing through Chandler.

1. Collecting Agenda Items for a Meeting in a “Task List” View

2. Reviewing Meeting Notes from the Calendar

3. Sending an Update to the Event with Notes from the Meeting

More importantly, all of this use and re-use is plausible because you can access the same information item from different contexts (the calendar and the list view, multiple collections) and there is built-in support for “losing” and “finding” information. Otherwise, recycling and evolving notes and events would quickly turn into an onerous workflow you would not bother with.

In Chandler:

• Meetings on your calendar can be managed like tasks in a list view; and vice versa,
• Tasks can be tracked from the list view *and* put on the calendar to mark important deadlines and milestone dates;

• The LATER “Triage Status” allows you to “disappear” stuff you can’t deal with right now without losing it forever;
• Tickler alarms and event dates automatically re-focus your attention on things you need to follow-up on

This Recycling Workflow works for maintaining lists (shopping lists, lists of questions, thank you notes, etc) and working on drafts as well. Really, it applies to anything that evolves and changes over time.