Re: [Usability] improving alarm productivity

["Matthew Nuzum" <newz bearfruit org>]

On 2/21/07, Andre Klapper <ak-47 gmx net> wrote:
> well, the term "snooze" implies to only postpone it for a short time. if
> you want to postpone something for a day (or something like that), i
> would ask you to edit the appointment data, instead of using the snooze
> function. (at least this was always my feeling about it when using evo.)
>
> > The net result is that I've actually suffered a severe loss of
> > productivity by switching to Evolution from Outlook.
>
> <irony>heh, to me it sounded like you would spend half of the day with
> clicking on snooze buttons to postpone events by an hour. ;-)</irony>

Yeah, I know it sounds odd, but my work day is filled with many short
tasks, so hitting snooze, which takes a single click and half a
thought is actually quite easy. For events that are extremely
critical, I have learned to accommodate evolution and go through the
extra effort to create multiple alarms, just to be safe.

> the problem is, like always, the lack of human ressources. triaging
> evolution bug reports takes more time than a half-time job, trust me.

I've read through the triage manual, I'll try and help out with this when I can.

--
Matthew Nuzum
newz2000 on freenode