[chandler-users] [Proposal] Chandler marks items done on its own
meissner.fritz at gmail.com
Fri Sep 19 12:59:57 PDT 2008
Looking at my list of past events, I can't see that any fixed rule (even if
it was a preference) would work for me. Some events cannot be re-scheduled,
others must be re-scheduled. My thinking is that having to manually set an
event to DONE is a minor inconvenience, whereas missing something because it
was set to DONE when it should not have been, could be a major disaster. So
even if there is a preference for auto-DONING, I would suggest that the
safer default should be not to automatically change status.
2008/9/19 Mimi Yin <mimi at osafoundation.org>
> Well it's actually comforting to see disagreement on this issue, as we were
> not at all clear about what the right behavior should be.
> What you're experiencing today is an unfinished implementation of 1 idea of
> how auto-triage to DONE should work, so that makes things doubly confusing
> Some issues that have surfaced from this discussion that we should note:
> 1. Auto-triaging to DONE is jarring to see when Chandler gets it wrong,
> especially for tasks. (Delphine: "I don't want Chandler to do my tasks for
> 2. Auto-triaging to DONE for events is maybe useful, assuming we've
> actually attended them. Otherwise, they should be left NOW so that we know
> to re-schedule them. (William: "All of my "events", with alarms or not, get
> rescheduled if I can't make/miss them.")
> Davor proposed that we only auto-triage events to DONE.
> The problem is, it's essentially impossible for Chandler to tell if an item
> on the calendar is an event or a task, if it's been attended or missed. And
> if it's been missed, whether it's something the user cares to re-schedule,
> because perhaps they are grateful they missed it ;)
> We could add attributes so that users can give Chandler more clues, but
> Chandler's ambiguity is a strength that would be undermined by adding more
> dials for this kind of thing. (Automation is supposed to make things,
> well...more automated!)
> Given that, I think it's fair to say that auto-triaging to DONE probably
> qualifies as something worth providing a user preference for.
> 1. Auto-triage events to DONE when they have passed in time
> 2. Don't auto-triage events to DONE when they have passed in time
> 3. Don't auto-triage Starred Events to DONE when they have passed in time
> Does this sound reasonable? If so, I will amend the auto-triage to DONE bug
> with this proposal.
> chandler-users mailing list
> chandler-users at osafoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chandler-users