> "Adam" == Adam Spiers <[EMAIL PROTECTED]> writes:
Adam> Thanks a lot for the feedback. I have read the book several
Adam> times but it was great to be reminded of his views on
Adam> priorities. Having said that, I think I would really struggle
Adam> to review on a regularly
On Dec 31, 2007 10:45 PM, Adam Spiers <[EMAIL PROTECTED]> wrote:
> Adam Spiers ([EMAIL PROTECTED]) wrote:
> > OK. My setup is similar except that I allow for sub-projects -
> > projects within projects. As a result, projects are not uniquely
> > identified by their star level, so I explicitly mar
Adam Spiers ([EMAIL PROTECTED]) wrote:
> OK. My setup is similar except that I allow for sub-projects -
> projects within projects. As a result, projects are not uniquely
> identified by their star level, so I explicitly mark them with PROJECT
> which means I retain the ability to do keyword sear
(More Structured Procrastination... ;-)
Adam Spiers ([EMAIL PROTECTED]) wrote:
> And on top of that, I need a way of marking a "someday" or "maybe"
> task/project as already STARTED or WAITING etc., which is why I
> wrote:
>
> > - Priorities become truly orthogonal to workflow, e.g. if your
> >
Pete Phillips ([EMAIL PROTECTED]) wrote:
> > "Adam" == Adam Spiers <[EMAIL PROTECTED]> writes:
>
> Adam> GTD methodology suggests having "someday" and "maybe" task
> Adam> buckets for things which you want to remember to do at some
> Adam> undetermined point in the future.
>
>
> "Adam" == Adam Spiers <[EMAIL PROTECTED]> writes:
Adam> GTD methodology suggests having "someday" and "maybe" task
Adam> buckets for things which you want to remember to do at some
Adam> undetermined point in the future.
Adam> So far I have implemented this in org-mode by us
On Dec 30, 2007 12:11 PM, Adam Spiers <[EMAIL PROTECTED]> wrote:
> Pros:
>
> - Priorities become truly orthogonal to workflow, e.g. if your
> workflow keywords are PROJECT, PROJDONE, NEXT, STARTED, WAITING,
> DONE etc. then you can mark any of these as someday/maybe
> priority. This
GTD methodology suggests having "someday" and "maybe" task buckets for
things which you want to remember to do at some undetermined point in
the future.
So far I have implemented this in org-mode by using SOMEDAY and MAYBE
keywords. However I have been deliberating whether in fact these
states ar
