Group items tagged

The current release of Chandler builds upon the experimentally usable calendar for individuals and small workgroups. It is a test release for collecting feedback based on real usage. In addition to basic calendaring, advanced features include: recurring events; time-zones; overlayed, multiple calendars; and managing a single event across calendars. Chandler offers innovative capabilities in calendar sharing to support workgroup collaboration. Chandler sharing is server-based, works across platforms and supports multi-author editing. Our goal for our most recent release, 0.7alpha4, is to give a rough sketch of what Chandler will be by our first Preview release (Spring 2007). This release introduces the Dashboard, which gives users a runway view of all of their information. Users can try creating a simple task list, and can share that list with others just as they can share calendars. Users can also experiment with sending notes, tasks and invitations to others via email.

This morning I found an email in my inbox telling me that I am a bad maintainer and that I am making people fork my modules. The mail was not meant to go to me, but the sender hit reply and thought he was moaning about me to someone else. Basically I was asking for my modules to be forked because I was too ### to release a new version. I don’t release a version unless I am confident it is release-worthy: when I have used it myself. Not a big deal, but it gave me food for thought about maintainance and release of Drupal modules, in general. And about how to improve the general issue of not having enough time to dedicate to a contribution In general, I think there are three reasons to maintain a module on Drupal.org You think it is fun or/and like to “give something back” It allows you to have your module improved without having to invest much time and money It works as marketing for you, as a highly visible portfolio: people see you, see your work and therefore might hire your services.