The Chandler Project Blog » Blog Archive » OSAF's Next Steps - 0 views
-
Being a CalDAV reference implementation is not a priority.
-
we will not be implementing CalDAV scheduling
-
CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
-
- ...17 more annotations...
-
Chandler’s philosophy is different enough from GTD that it would be misleading to call Chandler a GTD tool
-
Chandler is not oriented around calendaring per se or around a complicated task and project landscape with many dependencies
-
we want Chandler to be more viral. We want Chandler to be easy to explain to others. We want Chandler to be found in contexts where people are already spending time. We want Chandler to be
-
widgets should be compelling to a new user who does not use the desktop, in addition to providing features that complement the desktop. Eventually, the widgets can be building blocks
-
Our best articulation of our core value to date is: Chandler is a way to manage and collaborate on ideas using: A List View built around the idea of the Triage Workflow A Calendar View Chandler Hub Sharing Service
-
Better product messaging so that people understand what ‘user problem’ we’re trying to solve and how we’re trying to solve it.
-
We’re not looking to be a cheaper alternative to Outlook/Exchange. This means we’re not investing in support for free/busy-style scheduling. We’re not looking to be the ‘everyman’s’ version of Microsoft Project or Bug and Ticket-Tracking systems. This means we’re not investing in support for complex task and project management, e.g. task dependencies, tracking percent done, time estimates, robust support for assigning tasks, etc. We’re also not going to be implementing the GTD methodology.