Skip to main content

Home/ Chandler Project/ Group items tagged project

Rss Feed Group items tagged

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

The Chandler Project Blog » Blog Archive » Mobile Chandler? - 0 views

  • sync Chandler data onto any device that can sync with or subscribe to calendars via .iCalendar or CalDAV
  • Specifically, that means you can: Publish your collections to Chandler Hub; Subscribe to them with Apple iCal or Google Calendar; Use either Apple iSync or Google Mobile to get your Chandler data onto your mobile device.
  • https://support.markspace.com/index.php?m=knowledgebase&a=viewarticle&kbarticleid=230
Graham Perrin

The Chandler Project Blog » Blog Archive » Chandler Project: Next Steps - 0 views

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

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 : 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

The Chandler Project Blog » Blog Archive » More Blogging and Fewer Mailing... - 0 views

  • Chandler-dev is now the working list for all things pertaining to the Chandler Project
  • planning, design and bug prioritization
  • Chandler-users will remain the best place for users to ask questions and report issues
Graham Perrin

The Chandler Project Blog » Blog Archive » Next Steps for the Task Stamp - 0 views

  • don’t understand the point of marking some of my Notes as Tasks
  • proposal for extending the range of Item Kinds in Chandler
  • re-instate Tasks
  • ...10 more annotations...
  • extremely basic notion of Contacts
  • Reference Kind
  • don’t propose this instead of the Now/ Later/ Done system, but adjunct to
  • enter deadlines
  • see my tasks organized by those deadlines
  • and not necessarily a “to do” item
  • compilation of reference information
  • a configurable Chandler would be the most scalable solution
  • NOTES or REFERENCE feature would be useful
  • keep track of “reference material” that you want to keep around forever, just in case
Graham Perrin

(15 vs. 16) GetStarted < Projects < OSAF - 0 views

  • Deleting collections from your Chandler Hub account
    • Graham Perrin
       
      I have no problems in iCal or Chander Hub when I use use the Hub to delete a collection from the Hub.
    • Graham Perrin
       
      Is the warning here against using iCal to delete a collection from the Hub?
Graham Perrin

Hosted @ISC | Internet Systems Consortium - 0 views

shared by Graham Perrin on 25 Aug 09 - No Cached
  • ISC's main data centers
  • available to qualified public benefit projects
  •  
    OSAF — Open Source Applications Foundation — appears under Racked Guests. I guess that Chandler Hub and other Chandler Project activities/services fall under that umbrella.
  •  
    OSAF is listed as a racked guest.
Graham Perrin

The Chandler Project Blog » Blog Archive » Chandler User Survey - 0 views

Graham Perrin

Chandler - CIA.vc - 0 views

shared by Graham Perrin on 26 Jan 09 - No Cached
Graham Perrin

Chandler2 - CIA.vc - 0 views

shared by Graham Perrin on 26 Jan 09 - No Cached
Graham Perrin

Chandler Wiki : Browser Design - 0 views

  • computer file systems
  • book stores and supermarket aisles
  • hierarchical org charts
  • ...57 more annotations...
  • Trees abound in
  • trees prevail
  • they clearly limit us
  • Semi-lattices are non-polar, where do you start, where do you end?
  • Reality and the human brain's ability to grok it are far more complex than a tree
  • dumbing down isn't always a bad thing
  • you don't really understand something unless you can explain it in 5 words
  • Let's improve on the software
  • too strict, too dry, too simplistic
  • browse the same data via many different trees
  • visual information mapping hasn't already taken over the world
  • that break the tree
  • brains ARE really really good at seeing relationships
  • linear doublethink
    • Graham Perrin
       
      Graham: review!
  • stop-motion semi-lattice building
    • Graham Perrin
       
      Graham: review!
  • extremely adept at looking at the same data and reorganizing it into different trees in rapid succession
  • in one file cabinet, on one bookshelf, in one way
  • forcing us to look at our data
  • semi-lattii
  • Challenge: Find balance between trees
  • distorts the truth
  • expressive but often not communicative
  • same data in as many different kinds of trees as they want
  • start at any point in the tree
  • same data, different perspectives
  • rotate the tree
  • visual cues that seemed to burst forth with meaning begin to feel meaningless, random, disorienting
  • "watch" in "slow-motion" or user manipulated motion
  • future Chandler may have a richer graphical interface
  • different tree organizations of the same data
  • Overlaying the visualizations
  • composite semi-lattice
  • richness of semi-lattii
  • feed it to users in a way they can easily understand: trees
  • All parameters set in the browser are reflected in the Search bar
  • Saved rules
  • better than limiting users to a single tree
  • better than overwhleming users with a semi-lattice
  • "dumbing down" the data for the user
  • avoid UI shock via information overload
  • present users with the full-force and complexity of their information in a way that is understandable
  • possible, even within the confines of the 2-dimensional
  • easily walk from one tree to another
  • breaking away from hierarchy and how people used to hierarchies of folder are coping
  • http://weblog.edventure.com/blog/_archives/2004/4/19/36468.html
  • the freedom and amorphous-ness of a search-centric navigation paradigm
  • a little built in structure
  • Dashboard view / triage workflow as a point of entry
  • search to get within range
  • navigate using contextual clues to find the exact item
  • fixed hierarchies present a workflow bottlenck
  • we know what topic to file something under, but we don't know where that topic belongs in the hierarchy
  • pilers never bother to file
  • something new comes along to screw up the hierarchy
  • unwieldy taxonomies with duplication and confusion
  • Sometimes we don't know what we're looking for until we see it in context
  • brain's ability to use environmental clues to remember things
Graham Perrin

Inside Mitch Kapor's World | O'Reilly Media - 0 views

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 » How do you use the Chandler Das... - 0 views

  • the Dashboard purely as a place to collect new notes, an “intake” area
  • collections must be initially kept out of the Dashboard
  • everything that could possibly be worked on right now needs to be in one place. I use the Dashboard to answer the question, ‘what should I work on next’. Every Collection is in the Dashboard
  • ...6 more annotations...
  • 30 going at a time
  • a cross-collection view of all their data where the could process items regardless of what collections
  • what’s new across all of your collections without having to click on individual collections one-by-one
  • Dashboard collection in Chandler
  • ground for experimentation
  • no way to view items that are in the Dashboard but not in any other collections
    • Graham Perrin
       
      I did wish for this in the early days, but in practice I don't require this type of view.
  •  
    Interesting use cases.
Graham Perrin

Chandler Wiki : Cosmo Architecture - 0 views

  •  
    A very clear presentation of the architecture.
Graham Perrin

Chandler Wiki : How The Cookie Crumbles Part I - 0 views

  • hierarchies has been the designated one size fits all solution to all our organizational needs
  • we break our semantically pure hierarchies by overstretching their bounds
  • we end up with messy hierarchies that are unusable and unmaintainable
  • ...4 more annotations...
  • Stuff I need access to DOES NOT HAPPEN TO EQUAL the stuff at the top of the tree
  • Case study: Katie's OmniOutliner
  • http://www.shirky.com/writings/ontology_overrated.html
  • The following are images taken from: http://www.shirky.com/writings/ontology_overrated.html
1 - 20 of 60 Next › Last »
Showing 20 items per page