Skip to main content

Home/ Chandler Project/ Group items tagged GTD

Rss Feed Group items tagged

Graham Perrin

The Chandler Project Blog » Blog Archive » Chandler and GTD? - 0 views

  • GTD is not our single focus
  • Supporting knowledge work is. (Blog post coming soon.)
  • Chandler will continue to improve for GTD practitioners
  • ...6 more annotations...
  • We also welcome and will actively help volunteers who want to write a GTD plug-in
  • Chandler shouldn’t be construed as an implementation of the GTD methodology or any other methodology
  • how to turn Goals into Next Actions
  • appreciate that there is a difference between the two
  • the GTD label actually scares people away.
  • people who knew about Chandler’s past association with GTD assumed they needed to subscribe to a particular way of doing things in order to succeed with the product
Graham Perrin

The Chandler Project Blog » Blog Archive » Andre Tries Out the New "Indepe... - 0 views

  • Andre keeps two items open all the time in separate windows:
  • The first is something he calls a “Bucket” item
  • The second is a GTD Projects List. Andre consults this list repeatedly throughout the day
  • ...1 more annotation...
  • 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.
Graham Perrin

The Chandler Project Blog » Blog Archive » OSAF's Next Steps - 0 views

  • Chandler succeeds at meeting the needs of users who are tracking ‘knowledge work’
  • 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
  • ...17 more annotations...
  • even more useful as that user pulls in other people to collaborate
  • We want happy users be successful evangelists for Chandler
  • web widgets that might be deployed in different contexts — iGoogle, Facebook, on an iPhone, etc.
  • 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
  • misperception in the press
  • Being a CalDAV reference implementation is not a priority.
  • the Microsoft product with the most overlap with our design objectives is probably OneNote
  • web widgets (in the browser, on mobile devices and on the desktop)
  • not trying to be a GTD specific tool
  • Chandler’s philosophy is different enough from GTD that it would be misleading to call Chandler a GTD tool
  • 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
  • the user problem we are serving is an emerging market
  • there isn’t a shared, public vocabulary to describe what we’re doing
  • Better product messaging so that people understand what ‘user problem’ we’re trying to solve and how we’re trying to solve it.
  • more ways to get data in and out
  • we will not be implementing CalDAV scheduling
    • Graham Perrin
       
      CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
  • 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.
  •  
    February 6th, 2008 at 11:17 pm
Graham Perrin

Brain Breach » Blog Archive » Four Reasons Why Not to Use Chandler 1.0 - 0 views

  • Chandler is supposed to follow the GTD paradigm
    • Graham Perrin
       
      On the subject of GTD (not the single focus of Chandler), see also: http://www.diigo.com/04mh2 http://www.diigo.com/04mh3 http://www.diigo.com/04mh4
  • link a to-do to a contact to a calendar entry
    • Graham Perrin
       
      https://bugzilla.osafoundation.org/show_bug.cgi?id=5235#c12 I foresee Chandler Desktop interoperating with (not duplicating) the OS-managed address book data.
  • Memory Muncher
    • Graham Perrin
    • Graham Perrin
    • Graham Perrin
       
      Concerning a much earlier design decision, to not use ZODB: http://www.diigo.com/04mhd
    • Graham Perrin
    • Graham Perrin
1 - 4 of 4
Showing 20 items per page