Skip to main content

Home/ Groups/ Chandler Project
Graham Perrin

Chandler Get Started Guide - Chapter 2: Setting Up Accounts - Email Accounts - 0 views

  • drag and drop the email messages that you want to import into Chandler into one of the folders
  • file incoming email into one of those folders
  • Depending on which Chandler folder the email is in, when it gets retrieved and imported as a Chandler item, it will be stamped as a calendar event, email message, or task
  • ...3 more annotations...
  • Every time Chandler syncs with the email server
  • it checks for any new messages in one of the Chandler folders
  • even though it remains in the folder it is only imported once into Chandler
    • Graham Perrin
       
      So: does Chandler Desktop use IMAP message IDs to determine whether a message has been previously copied?
Graham Perrin

Chandler Wiki : Using Other Apps With Chandler Hub - 0 views

  • Sign up for a Chandler Hub Account
    • Graham Perrin
       
      Placement of the list of clients beneath this heading will confuse readers; they may imagine that what's presented below are means of signing up for Chandler Hub.
  • Step One
    • Graham Perrin
       
      The page is missing named steps beyond 'One'.
  • Publish from Apple iCal 3.x
    • Graham Perrin
       
      The description that follows relates to CalDAV which is not limited to (one-way) publication.
  • ...3 more annotations...
  • Collections you've subscribed to
    • Graham Perrin
       
      We should be more explicit about subscriptions. I guess that this statement refers to your Chandler Desktop subscriptions to the Chandler collections of other users of Chandler.
    • Graham Perrin
       
      Consider: some users of Apple iCal perceived collections long before Chandler introduced the expression.
    • Graham Perrin
       
      Consider: users of Apple iCal were familiar with subscriptions long before Chandler Desktop introduced the expression.
  • Sunbird Version 0.3
    • Graham Perrin
       
      Mozilla Sunbird has reached version 0.9.
  • view-only subscribing to other people's shared calendars
Graham Perrin

John's Blog » Chandler Changes - 0 views

  • the chronicling of the project in Dreaming in Code, was not, it seemed to me, quite fair or accurate, and I feel that there were significant missed conclusions in it
Graham Perrin

Chandler Wiki : Vision - 0 views

  • Custom Attribute
  • Custom Attribute
  • The Chandler Knowledge Worker
  • ...42 more annotations...
  • Information is the substance of their work and more information is the output of their work: Research, proposals, priorities, direction and decisions?
  • knowledge is gained and shared
  • how people actually work
  • (too) many interesting things
  • There's something wrong with the way data
  • doesn't flow between the tools we use to manage, process, organize our information
  • software should be modeled around information
  • technological barriers
  • too much copying and pasting
  • false assumption that information management tasks are binary
  • false assumption underlying most productivity software that information and the organizational structures needed to manage that information are essentially static
  • A lone email languishes for a long time in your Inbox and then all of a sudden, blooms into an unending thread which dies down
  • the thread is revived and mushrooms into a full scale project
  • Three weeks later
  • you barely give it a thought
    • Graham Perrin
       
      I tend to find myself involved in: at one extreme, very many varied small tasks, which are recorded/archived then intentionally forgotten; and at the other extreme: projects about which thought extends months or even years later. Between the two extremes: for me, things are hazy.
  • the same workflow hiccups show up again and again
  • an information management environment with built-in workflows that mirror what people hack together
  • three basic workflows everybody seems to construct for themselves, regardless of what tools they use
  • varying degrees of complexity and automation
  • These three workflows however, need to exist independently of each other
  • no complicated rule-builder
  • push-button interface
  • always assume a need for iteration and change over time
  • Peeling the Onion
  • Allow Organization to Change and Flow
  • the entire gamut of organizational affordances
  • Tagging
  • Filing, Rules, et cetera
  • won't ever be asked to decide between them
  • turn it into a Custom Attribute
  • Add semantics to a Tag
  • Custom Attribute
  • Drag a Tag or a Cluster to the sidebar
  • a Cluster: a way to thread items together, a way to reflect dependencies
  • Group collaboration systems exist in parallel with personal communication tools
  • does not scale down to work for small groups
  • the majority of the significant emails we send are sent while still in a draft-state
    • Graham Perrin
       
      This is very thought-provoking.
  • Future
  • a well-defined end-user information model
  • by modeling the user experience around how people work today and the substance of that work, we can be more than just another software tool and instead aspire to be a system for information management: A smarter way to work. A better environment for collaboration
  • We want Chandler to be able to talk to other applications
  • As we make Chandler's end-user information model richer, the number of interesting applications to talk to will increase. This is one of the many areas where we hope that people in the community will help increase Chandler's ability to talk to other applications
Graham Perrin

Vista - End of the Dream? * The Register - 0 views

  • I downloaded a copy of Chandler the other day, just to see how things were shaping up. As soon as I launched version
    • Graham Perrin
       
      Reading the April 2007 date of this story alongside http://blog.chandlerproject.org/2007/04/18/preview-update/ and http://blog.chandlerproject.org/2007/09/11/preview/ it's clear that the version (probably a checkpoint) tested by Dave Jewell predated the 'preview' by around five months.
  • Chandler is still an awful long way off from that magic 1.0 release
    • Graham Perrin
       
      The OSAF vision of Chandler originated around 2001. In 2007: the preview milestone version was certainly (but not disappointingly) some way away from the release. Chandler 1.0 was released in August 2008.
  •  
    Some discussion of the Chandler Project.
Graham Perrin

Chandler Wiki : OSAFHistory - 0 views

  • OSAF started in 2001
  • accumulated a major backlog of innovative ideas for new software products
  • has become quite difficult
  • ...3 more annotations...
  • adoption of innovative solutions
  • very happy for others to make money
  • a licensing scheme which would permit both non-commercial and commercial development on the code base
Graham Perrin

Chandler Wiki : Is Search The Panacea - 0 views

  • In our euphoria over the success and surprising usefulness and usable-ness of search and tagging, are we passing by a chance to not only make information accessible and useful but fundamentally alter the way we use information to make decisions.
  • we did not come all this way to end in Search, the biggest leap in information technology is yet to come
  • Search doesn't solve many of the biggest problems we face in our still nascent yet rapidly growing information-centric, information overloaded age
  • ...2 more annotations...
  • how do we grok, wrap our heads around all this data? (NOT just succeed in finding stuff in it.)
  • Search is not a solution to information management. It's one piece of the puzzle.
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

Chandler Wiki : Chandler Interop - 0 views

  • Chandler Server does not support CalDAV scheduling
Graham Perrin

Checkvist: collaborative online outliner and checklist - 0 views

shared by Graham Perrin on 04 Jan 09 - Cached
  • Extensive use of keyboard navigation and shortcuts
Graham Perrin

Chandler Wiki : Get Started - 0 views

  • Collaborate on Notes and Events over Email
    • Graham Perrin
       
      IMHO the e-mail capabilities of Chandler 1.0.2 require special explanation. Some explanations are offered within the FAQ, http://www.diigo.com/annotated/faf93764c6f6f5eb9a29268ad4b472de
    • Graham Perrin
       
      The number and nature of the special explanations, criteria and limitations of e-mail in Chandler Desktop make me think that 'Email' its sub-headings, as currently presented in 'Get Started', should not appear in Get Started.
    • Graham Perrin
       
      I suggest leaving references, from the Get Started page, to pages that are dedicated to: (1) an overview of e-mail in Chandler Hub and Chandler Desktop, and of limited communications with IMAP and POP servers; (2) using Chandler Desktop to configure an IMAP server, and understanding the workflows (in particular, the aspects that are one-way, periodic (Chandler Desktop sync) and incremental (the effect of adding messages to a Chandler-specific mailbox that was previously synced)); (3) e-mail in Chandler Hub; (4) e-mail in Chandler Deskop.
    • Graham Perrin
       
      Critically: the overview should contain no instructions on use; it should present, in pictures and in few words as possible, the current workflow and vision, plus maybe no more than one vision of the future.
Graham Perrin

Chandler Getting Started Guide - Chapter 6: Triage Workflow and Stamping - 0 views

  • Today, many people do this by flagging emails or maintaining a task list. The problem is
    • Graham Perrin
       
      This is a 'Getting Started Guide'. Keep it positive :) Talk of problems, behavioural patterns and visions should be elsewhere (the wiki is fine); simply refer from the Guide to the wiki.
  • have been added to the User Interface
    • Graham Perrin
       
      Comments such as this belong in 'What's new' flyers, or in release notes. People who are truly using this Guide to get started are unlikely to have an interest in project history or design changes.
  • has been improved: better native
    • Graham Perrin
       
      Whilst I'm getting started, I don't want to read that things were worse.
Graham Perrin

Chandler Wiki : Web Home - 0 views

  •  
    Includes a nice loose graphical representation of server and of extensible desktop.
Graham Perrin

Chandler Project - Welcome - 0 views

  • confluence
  • simple items which can interact and be managed with one other
Graham Perrin

Mailing list archives - 0 views

  • 2. Mailing list systems... All the comment on whether to have user group mailing lists on Gname or Nibble or MyLittleMailingListServer sometimes seems a bit beside the point of the forum for users for chandler. <commence flame>
Graham Perrin

Chandler Wiki : Why Not Zodb - 0 views

  • data model to be independant of any language in particular
  • queries, interactions with RDF, bi-directional referential integrity, access control, garbage collection, etc.
  • replication, remote access, shared access, threaded transaction model, etc.
  • ...3 more annotations...
  • started a data model implementation from scratch and persisted it using Sleepycat's Berkeley dbxml and Berkeley db
  • Chandler repository is not really so much an object database as an item database combined with large collections of references directly stored in Berkeley DB
  • a somewhat steeper learning curve for programmers expecting a real object database like ZODB. My hope is that this trade-off is well worth the gains
Graham Perrin

[Chandler-dev] What's our Web Strategy? Web Widgets, The Server and The Current Web UI - 0 views

  • Less important behaviors to 'get right' across Chandler access points
  • items living in multiple collections
Graham Perrin

Chandler Wiki : FAQ - 0 views

  • Q Can I use Chandler for Email?
  • For Preview
    • Graham Perrin
       
      This paragraph, at least these words, should be updated with respect to 1.0.2.
    • Graham Perrin
       
      Re http://www.diigo.com/annotated/d62b6b8ed21cf763e92d3b3b6a88f86a the expression 'Preview' was in use around April 2007.
  • Chandler Preview
    • Graham Perrin
       
      Update to reflect the 1.0.2 situation.
  • ...11 more annotations...
  • sends and receives email
    • Graham Perrin
       
      … and uses IMAP, but does not place sent messages in the Sent mailbox of the IMAP server.
  • sent from other Chandler users
    • Graham Perrin
       
      This fundamental point should be HIGHLIGHTED (not diminished in parentheses).
  • downloads messages via 3 IMAP folders
    • Graham Perrin
       
      I see evidence of Chandler 1.0.2 working with POP, though I don't use it in that way.
  • Add messages from your email client into special Chandler IMAP folders
    • Graham Perrin
       
      Messages moved by your IMAP client to Chandler Desktop-specific mailboxes
  • to download them into Chandler where you can manage them as Chandler notes and events
    • Graham Perrin
       
      … will be copied by Chandler Desktop whenever you sync Chandler Desktop.
    • Graham Perrin
       
      Subsequent management within Chandler Desktop will not be communicated back to the IMAP server.
    • Graham Perrin
       
      After a message has been copied by Chandler Desktop, then in your IMAP client you may wish to archive (or set aside) the earlier copy, to avoid confusion.
  • What still needs to be done
  • Sync IMAP Flags and Read/Unread status
  • Unlike "regular" email, you can edit and re-send Chandler emails
  • current target screen size - 1024x768 pixels
  • should still be usable at 800x600 pixels
  • the application
    • Graham Perrin
       
      the Hub
Graham Perrin

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Tra... - 0 views

  •  
    A most remarkable omission from the reviews on Amazon (and presumably, from the book) is: discussion of standards, such as those relating to CalDAV. OSAF/Chandler Project members made significant contributions to the drafting and setting of standards. Happily, we don't hear companies such as Apple or Google criticising Chandler Project history whilst embracing/enjoying CalDAV. I suspect that - however well written the book may be - a *focus* on a space in time (however short or long) has overlooked the broader value of the Project.
  •  
    I'll rate and review this book, probably some time around Christmas.
  •  
    "Our civilization runs on software. Yet the art of creating it continues to be a dark mystery, even to the experts, and the greater our ambitions, the more spectacularly we seem to fail. … [this book] sets out to understand why, through the story of one software project -- Mitch Kapor's Chandler, an ambitious, open-source effort…
Graham Perrin

2003 - The Andrew W. Mellon Foundation - 0 views

  • Research in Information Technology
  • unusual projects supported through the Foundation’s program in Research in Information Technology, Chandler
  • developed by the Open Source Applications Foundation (OSAF), led by Mitch Kapor, and over the next two years OSAF will receive a total of $2.75 million to develop
  • ...2 more annotations...
  • the 25 members of the Common Solutions Group (CSG), a group of information technology specialists from major universities
  • CSG schools have formed a formal advisory group to help OSAF during the development
« First ‹ Previous 41 - 60 Next › Last »
Showing 20 items per page