[Design] Proposal for a nag-reminder feature

[Mimi Yin]

From: Sean Reifschneider <jafo-osafoundation at tummy.com>

(Submitted to bugzilla, moving to design list.)

Not all things that are put on a calendar have a hard date associated  
with them.
  Giving a presentation from 6pm to 7pm at a conference is very  
different from
scheduling having the oil changed in the car, following up with a  
client, or
changing the filter on the furnace.

All these things need to be done, but may have an elastic time when  
you'll be
able to do them.

We currently have a system we call "nag" in which you can specify a  
date/time
and a nag frequency.  On that date/time, you get a reminder, and another
reminder is scheduled for the frequency later.  The nags keep coming  
in until
you mark the event as done.

So, maybe I'd say that in 3 months I want a reminder to schedule an  
oil change,
and that I want a reminder every day after that.  Or maybe I need to  
call a
client next Thursday, but they're hard to get ahold of.  I may want a  
reminder
every 2 or 3 hours throughout the day until I reach them.

This is kind of a "todo" sort of thing, but it also is very much
calendar-centric because it is based on date/time.

This is functionality that we have come to depend on in our  
organization, but
something I haven't seen in many other calendar systems.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060111/1f949193/attachment.html