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 release introduces a new item detail view designed to drastically improve item editing workflows. It integrates a larger, expandable notes field, date pickers for appropriate fields and a cleaner design. Other significant changes in the Web UI include cleaner add/remove affordances, conditional use of WhatWG DOM Storage for login information and numerous minor usability and display tweaks.

On the server side, an upgrade to the 0.4.0 version of Abdera, the library used to build our Atompub service, brings the server up to date with the latest library API changes. Sharing capabilities with Apple’s iCal client have been enhanced by changes in the mapping from the internal server data model to iCalendar records. In addition, enhanced ETag and If-None-Match header support provide significant optimization opportunities for webcal clients.

Chandler Server 0.16.0 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.16.0

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

chandler-users@osafoundation.org

The bugs fixed in this release include:

• [Bug 12181] Make get started message pop more
• [Bug 11540] deleting a subscribed collection raises an error
• [Bug 12146] no error messages on login or signup in safari
• [Bug 12149] Use dom storage when possible for login info
• [Bug 11271] Make Notes field auto-resize depending on available space
• [Bug 9887] prev and next buttons messed up on the calendar UI for small screen browsers
• [Bug 10919] Sort by Starts on doesn’t seem sorted properly
• [Bug 10004] timeout dialog box buttons are confusing.
• [Bug 8917] change event timezone to America Lima event time in lozenge is corrupt
• [Bug 11851] Sort triage status by TriageStatusChangedDate
• [Bug 11853] Explanatory text for account confirmation and account login pages
• [Bug 11854] Various visual improvements and cleanup
• [Bug 11942] signing up for new account in ticket view doesn’t redirect you to new account
• [Bug 12059] New Settings Dialog / New About Hub… text
• [Bug 12063] Make error message on login page pretty
• [Bug 12064] No visual feedback for keyboard focus in Signup dialog in Firefox
• [Bug 12065] Simplify email confirmation message when signing up
• [Bug 12066] Update links for instructions on acct activate page + other improvements
• [Bug 12131] Triage column header won’t reverse sort
• [Bug 12159] unsaved changes dialog appears when no changes occur
• [Bug 12167] Any-time events result in unsaved changes dialog
• [Bug 12174] Setting end date to before start hangs in “Processing…”
• [Bug 12205] 10+ collections creates big gaps in sidebar list on ff2/3
• [Bug 8297] Scroll bar in sign up for a new account is messed up.
• [Bug 9765] Implement selected state that looks different from rollover state
• [Bug 11346] Improve Task icon
• [Bug 11791] Upgrade Abdera
• [Bug 12037] Sync Chandler Notes / Starred Notes as iCalendar Tasks…
• [Bug 12071] webcal requests should return ETag and honor If-None-Match header
• [Bug 12115] Confusing discrepancy between list views on Hub and Desktop
• [Bug 12152] server returns 500 when no master calendar component found
• [Bug 12153] 500 returned when generating Subscription feed that contains invalid subscription
• [Bug 7085] Disable new signups feature
• [Bug 8396] Mini cal for date picker
• [Bug 10430] Chandler Hub logo is squished on ‘Activate’ page
• [Bug 10772] Usernames not being url-escaped before being used in URLs in web ui.
• [Bug 11119] Pull branding graphics out of image grid file
• [Bug 11561] Cannot Delete Recurring Items from Dashboard
• [Bug 11629] Atom subscription edit link returns 404
• [Bug 11739] Ask for email address of users who download the desktop or sign up for an account
• [Bug 11852] Improvements to DV (including Notes field)
• [Bug 11945] Javascript timezone unit tests fail on Safari 3.0
• [Bug 11981] webui creates invalid allday modification
• [Bug 12026] Password Reset not validating password
• [Bug 12053] New sidebar
• [Bug 12054] Implement new Subscribe/Download from the Sidebar design for ticket view
• [Bug 12060] Add “What is Chandler?” link to “logged-out” ticket view
• [Bug 12061] Change all references to “Floating” time zones to “None”
• [Bug 12070] Can’t delete user using Safari
• [Bug 12081] Detail view displays “once” for custom recurrence rules
• [Bug 12121] Collection-Details pulldown isn’t right-aligned when you first log in
• [Bug 12135] focus for new collection dialog should be in text field
• [Bug 12161] Able to select “custom” as a recurrence rule
• [Bug 12163] collection list checkboxes get their own line for many collections
• [Bug 12166] ticket creation ui radio buttons not showing up for account browser
• [Bug 12175] all day change in list view not reflected in canvas view
• [Bug 12177] entering invalid credentials on add subscription to account dialog results in [object Error]
• [Bug 12183] I don’t have Invite button/links for collections I subscribed to
• [Bug 12185] Make subscribe dialogs pop more
• [Bug 12198] Can’t delete recurring events immediately after creation
• [Bug 7098] update wiki CalDAV page
• [Bug 7099] update wiki WebDAV page

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 release introduces a new sharing dialog in the Chandler Server Web UI that greatly simplifies many common sharing and subscription workflows. It also fixes many server and client bugs which improve interoperability and reliability.

Chandler Server 0.15.0 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.15.0

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:

• [Bug 10969] ical doesn’t like multiple dates in single EXDATE property
• [Bug 10985] Incorrect methods reported in Allow header for dav OPTIONS response
• [Bug 11599] Enforce new username policy server side.
• [Bug 11654] Cosmo Doesn’t Seem to build on Java 1.6…
• [Bug 11667] attempt to remove non-existent modification could result in error
• [Bug 11668] npe during time-range index update
• [Bug 11808] iCal not seeing tasks
• [Bug 11864] No story for what happens to modifications when master is no longer stamped as event
• [Bug 11883] Improve error messaging for morse code
• [Bug 11957] login case insesitive, but security check not
• [Bug 12025] ArrayIndexOutOfBounds exceptions in DAV operations on hub
• [Bug 7877] Collection Details - download calendar/tasks not working? And remove text/link
• [Bug 8329] Add hyperlink to feed reader in ‘collection details’ dialog box
• [Bug 10605] “please enter a new name” misleading/confusing
• [Bug 11259] Collection details dialog protocol urls should be links or images.
• [Bug 11535] adding an already subscribed to collection redirects the page to “you do not have access to this resource”
• [Bug 11593] Collection details dialog tweaks for feed URL
• [Bug 11848] Add ticket creation mechanism in the Web UI
• [Bug 11849] Fix collection details dialog
• [Bug 12076] timezone wierdness
• [Bug 10623] specific events stamped as tasks missing from the list view
• [Bug 11418] cosmo allows duplicate name in same collection
• [Bug 11847] Remove OOTB Hub collection
• [Bug 11580] / in username causes hibernate error on signup
• [Bug 11974] ThisAndFuture change to all day event fails
• [Bug 11975] attempt to update un-authorized item through atom returns 500
• [Bug 12074] Unable to save note to All Events when recurrence is custom
• [Bug 12080] check not showing up in list view for tasks

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

The first changes I’m excited about are, like our latest release, less wholesale modifications than improvements and commitments to stable APIs with performance enhancement sugar to sweeten the deal. Dojo’s internationalization (i18n) and event APIs have matured to the point where developers can expect to rely on them without fearing a future change like the one we’ve just experienced. As a result we’ve begun the process of migrating our custom i18n code to Dojo’s API, away from the custom, backend dependent code we’ve used in the past. We’ve also started streamlining our use of Dojo’s topic APIs to make our code easier to read and understand. Both these processes are works in progress, so keep an eye on this space for more detailed information in the future.

Several components have also seen essentially complete overhauls, most prominently the XMLHttpRequest wrappers and Dijit, the full featured HTML/CSS UI toolkit built on Dojo Core. Instead of using dojo.io.bind and passing callback functions, method, and header information dojo.xhrGet, dojo.xhrPost and a handful of other methods accept a variety of arguments, make HTTP requests and return dojo.Deferred objects. This return value, a port of the asynchronous task management API introduced by Python’s Twisted networking library, provides an easy way for developers to manage complex sets of asynchronous actions like server requests. Since our Web UI data APIs already used dojo.Deferred internally, this change led to a very nice code reduction.

Dojo’s user interface building API, Dijit, has been greatly improved since Dojo 0.4. In addition to moving to its own namespace as part of Dojo’s overall API flattening, Dijit is better streamlined, better tested, and easier to use. A number of Chandler Server UI components have been ported to the Dijit APIs, and are, as a result, better tested, more modular, and closer to being embeddable outside of our Web UI.

The Dojo team has also been hard at work putting together the next generation of Javascript tools to support high performance rich applications on top of the Open Web. Two of these tools are already finding their way into heavy use within our code base, and are poised to become critical pieces of our infrastructure over the next year.

The first, dojo.data, is “uniform data access layer” that allows UI components to be built without worrying about backend data formats. Our user administration interface has been essentially completely rewritten, but required almost no new UI code. All we had to do was implement a dojo.data store on top of the Cosmo Management Protocol (CMP) and hook it up to Dojo’s Grid widget to get full in-place user field editing, “infinite scrolling” for handling large numbers of users and a handful of other goodies. While our end-user calendar and item list UIs have not been moved to this API, the ongoing web widget project is being built on a new dojo.data store that we hope to eventually integrate into our current UI.

The second piece of new functionality that I’m excited about is dojo.query. This do-it-all CSS query function is the go-to guy for finding pieces of DOM to manipulate. The beauty of this and other query functions is that they are based on features most web developers eventually expect to be supported natively by all major web browsers. By allowing developers to start using these features now we can build advanced web applications that will get trivially more performant with time, and motivate browser developers to continue implementing this critical functionality.

In addition to improving the tools we use to build our Web UI, Dojo’s 1.0 line has introduced some major infrastructure improvements in the form of a DOH, a new Dojo-independent testing harness, and a from-scratch rewrite of the Dojo build system. We’ve managed to port all of our tests to DOH by writing some wrappers to avoid a completely rewrite, which has allowed us to take advantage of the very nice test harness bundled with Dojo. Nearly as important as this test framework is the build system that plays a key role in transforming over 1MB of Javascript into a much more digestible 138K loaded in several different stages. The Dojo 1.0 line makes this process much cleaner and easy to understand, as well as offering advanced functionality like layering, which allows us to break our Javascript into large chunks appropriate to different pieces of our UI.

Dojo has been an integral part of our project to build a new kind of information and knowledge management ecosystem and we are lucky to be able to rely on a vibrant community of developers producing a first class piece of software. If you’re interested in digging deeper and helping us integrate even more of the exciting new functionality provided in its latest release, Dojo 1.1, please don’t hesitate to ask questions on our development list, or via IRC on irc.freenode.net in the #cosmo channel.

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 release primarily consists of an update to Dojo, the Javascript toolkit used to build the Chandler Server Web UI. Dojo’s 0.9 release was essentially a complete rewrite, and involved a large number of core API changes. Changes to our codebase have been similarly numerous. We are currently using Dojo 1.0.2, and do not anticipate upgrades with as significant consequences in the future.

More information on Dojo, including comphrehensive information about changes introduced in its 0.9 release, can be found at:

http://dojotoolkit.org

Chandler Server 0.14.0 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.0

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:

• #11607 Upgrade to Dojo 1.0
• #8499 Subscribe/unsubscribe to a collection on web UI
• #11351 Move client collection addition/deletion to atom api

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 release includes a major security fix as well as a small amount of minor bug fixes. The focus for this release was to fix the security hole present in prior versions that allowed users to gain write access to items without a read-write ticket. Part of this fix required changes to the desktop client, so upgrading the server to 0.13.0 will require upgrading Chandler Desktop to 0.7.5 in order to support certain features (sharing items in multiple collections). It is strongly recommended that the desktop client be upgraded to 0.7.5 when upgrading the server to 0.13.0. Chandler Desktop can be downloaded here: http://chandlerproject.org/Projects/DownloadChandlerDesktop

Chandler Server 0.13.0 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.13.0

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:

• #11867 fix items in multiple collections security hole
• #11794 support for PostgreSQL in migration tool
• #10814 Can’t update an item that isn’t owned by user from webui
• #11779 changing calendar selection while looking at future weeks resets view to this week without grabbing this week’s elements
• #11797 Chandler requires JVM properties to be set
• #11641 HCalendarParser broken when ical4j.relaxed.parsing is set
• #11863 updating item using DAV results in owner always being set
• #11931 Can’t access account browser for any of my collections
• #11909 hibernate session not getting flushed after optimistic locking failures

There was a minor change to the database schema for Chandler Server in version 0.13.0. Instructions for upgrading from previous versions of Chandler Server can be found at: <http://chandlerproject.org/Developers/ServerBundleInstallation#Upgrading%20from%20previous%20versions> Please remember to backup your database before attempting migration!

As we have in the past, OSAF will be participating in SoC as a mentoring organization this year. A full list of projects we believe will be both useful to the project in the long term and stand a high chance of being included in our code base in the short run can be found here, but as in past years outside proposals are more than welcome.

Comprehensive information about this year’s program, including important bits like eligibility and application instructions can be found on the the official FAQ. Student applications will be accepted from March 24 - March 31, so now is the time to find a project and put together a solid proposal!

As always, feel free to ask on one of the Chandler Project mailing lists or in #cosmo or #chandler on irc.freenode.net for more information.

Chandler is about trying to match the way people really work. And everyone uses lots of tools to get their job done. One of the first things people want to know when considering trying out Chandler software is “Will it work with what I already use? Can I switch back if I don’t like it? Will it work with the tools that friends of mine use?”

We believe the answer to all these questions is “YES”! You can safely and productively start using one or more of the Chandler Project components on top of your existing toolset. Go ahead, try it out! Read more below to learn the details.

For a bullet-list summary of our best-available notes on specific applications and which features are supported with each, see our interop overview.

Import/export

The gold standard of calendar transfer is the “ICS” file (in iCalendar format). Most calendar and task list applications support both import and export of ICS files.

You can try out Chandler Desktop without switching from your current setup. Just export one or more ICS files from your current application, then import those files into Chandler Desktop (continuing to use your current app). To switch over permanently, just export+import again a final time!

If you later decide you’d like to change again, you can export ICS files from Chandler Desktop or Chandler Hub, using those files for import into a wide variety of applications.

We’ve seen import and export work for Outlook 2003/2007, Mozilla Lightning/Sunbird, Apple iCal, and others; it should work with a great many apps, probably yours included.

Note that Outlook doesn’t export full information by default; we’ve found this $10 application from littlemachines produces high-quality exports from Outlook that work well with Chandler Desktop.

In practice, doing ICS import/export can have gotachas. Not all application combinations/roundtrips are 100% perfect. We urge you to keep backups and try out import/export before committing your important data to any application. In Chandler Desktop, we’ve spent a lot of time tuning our import/export routines to handle as many variants and details as we can. Chandler Desktop properly handles events, tasks, timezones, recurrence, and other details. Please report any import/export problems you encounter.

We’ve put together some additional information about import/export with Chandler Desktop specifically, so check that for additional hints and notes.

Synchronization

ICS import/export is great for transferring your data between apps, but it’s a manual process not suited to keeping multiple applications in sync. Usually when you import a data set, your app will overwrite changes you may have in your local copies of those events. It’s hard to make changes in two separate apps.

Chandler Desktop and Chandler Hub both support multiple network sync protocols. Where other applications (Outlook, iCal, etc) overlap at least one of these protocols, interoperability is possible on at least some level.

One main idea to keep in mind when thinking about these various systems is whether a scheme is “read-only” or “read-write” (ie, bidirectional). It seems like read-only (or 1-way) interoperability works more reliably today, but protocols like CalDAV promise a new era of real-time, 2-way synchronization of calendar data between lots of free and for-pay applications and web services.

The big news is that you can do 2-way/read-write calendar and task synchronization today, both privately and shared with other people. Here’s a list of the main ways to do that, based on Chandler Project software.

Webcal, 1-way sync

The most simple network protocol is to take an ICS file (see above in import/export) and post it to the web, so various apps can download it (redownloading to check for changes periodically). This system is called webcal.

Chandler Desktop works great for subscribing to a number of public webcal URLs and overlaying them all on one canvas. This is a great way to keep track of lots of calendars.

If you store any events/tasks on Chandler Hub, then you can login to get a URL that you can enter into the right spot in Outlook, Apple iCal, Google Calendar, Lightning/Sunbird, Evolution, Zimbra, and many other apps to synchronize that Hub calendar with your app. This is always a read-only/1-way procedure.

Using webcal, in Outlook 2007, you can overlay say personal or family Hub calendars on top of your Exchange/Outlook calendars you use at work. (Look for “Internet Calendar” features in Outlook’s help.) If you make a change on the Hub or Chandler Desktop and then synchronize, you’ll see that change in your work Outlook’s display.

You can also subscribe to Hub calendars in Outlook 2003, but only view the calendars side-by-side. Other apps like iCal, Lightning/Sunbird, Google Calendar, and Evolution all support overlaying the Hub calendar with other calendars.

Many applications, Outlook included, can also publish a webcal calendar to a web server. You can use Chandler Hub as a destination server for most of these webcal-publishing apps. This works, but please note this does not provide a web UI for that calendar, and it’s again a 1-way publication. The original application will very likely not detect any changes made to this webcal file on the server.

Webcal, 2-way sync

Chandler Desktop can also do 2-way synchronization via webcal. Most applications treat a webcal file as read-only or write-only, but Chandler Desktop will check for changes in a webcal file it is monitoring and integrate those changes. If used with another application that also checks for changes, you get 2-way synchronization. We know Lightning/Sunbird does this (though you might chose to use CalDAV to synchronize instead).

CalDAV, 2-way sync

CalDAV is an emerging standard protocol for open calendar exchange. It’s not a protocol that’s used directly between two clients (like ICS files are), but rather defines a calendar server to which multiple clients can subscribe and synchronize. Chandler Hub also provides a read-write web UI to any calendar you store or use in your account.

The Open Source Applications Foundation via the Chandler Project was an early supporter of CalDAV. Together, our Chandler Desktop application and Chandler Server server product are some of the oldest and most mature implementations of the CalDAV standard and we plan to continue that support.

Chandler Hub is, as far as we know, essentially the leading free CalDAV service offered to the public. Given a fully-cooperating CalDAV client (Lightning/Sunbird, iCal 3.x, and Evolution all cooperate to various degrees), you can use these other clients regularly or occassionally and even use Chandler Desktop for advanced work (like sharing a single item between multiple calendars).

Chandler Desktop can subscribe to and publish a collection (calendar+events) to any CalDAV server (Apple Calendar Server, RSCDS, Bedework), or actually any WebDAV server (Apache mod_dav, .Mac, etc). Both of these mechanisms support bidirectional (read-write) synchronization, so multiple applications or people can all create, edit, and delete events and tasks any time they want, using the application of their choice.

iCal 3 (in Apple 10.5 “Leopard”) is a great new CalDAV-using PIM client. You can use it to make changes to your Hub collection, and still be able to use the Hub web UI to make changes from anywhere. Note that iCal 3 supports read-write calendars only to calendars in your account. Chandler Desktop and Chandler Hub let you subscribe to shared collections owned by other users with full read-write access.

Email integration

Chandler Desktop is not a complete email client; it is rather intended to complement your existing email client. The mechanism we use is to create dedicated Chandler folders on your IMAP server. Using your regular email client (Outlook, Thunderbird, Mail.app, Evolution, etc), you just drag an email from your inbox into a Chandler folder, where the message will be parsed for event, task, and other information.

You should also be able to send email update of items from Chandler Desktop using just about any outgoing mail server available. Events emailed this way appear as ICS attachments. We’ve tested Exchange, Postfix, Gmail, Yahoo mail, and Hotmail/MSN among others.

Mimi described the goals nicely in a post to the chandler-dev list…

1. Get Chandler in front of more users, aka: Make it more viral.

Product changes:

• Item sharing: a new workflow to use the web to collaborate on just one item. We’ll “widgetize” this functionality, making it available in other contexts like iGoogle or on an iPhone.
• Improve web UI “ticket views” so subscribers can more easily subscribe to collections in applications they already use
• Improve existing use cases for iCal and Lightning users (sharing with Chandler users, using Chandler Hub)

Marketing and Evangelism:

• Improve our pitch, improve our web presence
• Better demos, user testimonials
• Reach out and talk to people about Chandler in other spaces

2. Make Chandler more appealing to new users, aka: Reduce barriers to getting started.

Reduce the number of new concepts users need to understand in order to get started:

• Pare down UI, de-emphasizing email UI
• De-emphasize notion of “Item” and replace with “Note”
• Remove explicit “Task” and introduce “Star”

Improve the web UI experience for people not using Chandler desktop (iCal/Lightning or Hub only users):

• smooth out sharing workflows
• auto-triaging CalDAV events
• make Notes field in detail view more usable

3. Make it easier for new users to ramp up to using Chandler every day.

Add two additional “widgets” with features that allow people to use Chandler in other contexts:

• Notifications: Users can send themselves or others notifications about changes to shared collections. This also counts towards the first goal, as it allows current users to share some Chandler functionality with other people. Notifications will be available first as an iGoogle widget (and potentially other similar contexts), and eventually also as email, SMS, or IM messages.
• Quick Entry: this widget will allow users to enter items into Chandler Hub from other contexts: iGoogle, iPhone, OSX and Vista widgets. Eventually we’d like to allow similar functionality through forwarding email to a particular address.

Work Queues and Releases

The work described above has been broken down into tasks and bugs and is prioritized into two work queues, one for the desktop and one for all of the web related work. Grant is marching down the desktop queue while everyone else tackles the web queue. We meet daily to cover progress, adjusting the work queues if priorities change. (Mockups and specs for the new widgets and web UI changes are also linked from the web queue.)

• Web Work Queue
• Desktop Work Queue

The plan is to do a desktop release and a server release once a month. Usually these won’t need to be coordinated — though in this next round we have a security bug that involves both.

Phillip’s work on the desktop rearchitecture is the exception. He’s posting about his work over on the PEAK list. We may move Chandler desktop over to this architecture after the 1.0 — we’re waiting to see how this plays out to make the call on that.

Milestones

We plan on hitting a few major milestones by early summer — these are the big goals we are shooting for:

• Web Widgets: Quick Entry, Notifications, Item Sharing — we’d like to have these deployed in a few contexts.
• Desktop 1.0: We’re pretty close to releasing a 1.0 desktop. Prior to launching this we want to make sure some web UI improvements go up on the Hub, and make some changes to the website.
• Server 1.0: With some security fixes, authentication work, and a few other items (e.g. the ability to disable account signups), we should be able to release a 1.0 for people who want to run their own server.

We don’t need to coordinate all of these milestones — we may hit some more quickly than others.

Changes to the Plan

We were thinking we’d put minimal investment into the existing web ui, figuring that we’d do a better job on the web use cases we want to hit with the web widgets. Once started thinking through both the web and desktop use cases, we realized we really do need to make some investment in the existing web ui. We’ve added web ui bugs to the web queue.

We decided to put off working on a Thunderbird plugin, for two reasons: (1) after doing a bit of research it was starting to look like a more sizable investment than we initially thought and (2) we worried about having too many projects.