emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: jmcbray@carcosa.net (Jason F. McBrayer)
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: GTD, Projects, and Next Actions in org-mode
Date: Thu, 03 Aug 2006 16:36:51 -0400	[thread overview]
Message-ID: <m1wt9pr1y4.fsf@bertrand.carcosa.net> (raw)
In-Reply-To: <3dbac09fcc4853019690ee76c8c4a73f@science.uva.nl> (Carsten Dominik's message of "Fri, 7 Jul 2006 08:35:16 +0200")

I thought I'd ask to see how other people who are using org for
Getting Things Done are handling projects and their relationship to
Next Actions.  I've tried out several approaches, and while I can rule
out a few as no good, there are some with enough plusses and minuses
to keep me from being really happy with any of them.

My first go was to have a top-level category for projects, with a
headline for each project under that.  This worked for keeping track
of my list of projects, but it didn't give me any way to tell what
project a Next Action was associated with.

My next attempt was to mix together projects and next actions, with
next actions coming hierarchically under the project they were
associated with.  Projects have a tag unique to that project, but
distinct from the tags I am using for contexts (contexts start with @,
projects with nothing).  This works, but the only way to get a list of
projects is to either look manually through the file, or get the list
of tags and ignore the ones that are contexts.

I've tried two others:  one is to make PROJECT an org-todo-keyword.
This makes it very easy to get a list of projects, with the negative
side effect that projects can show up in context lists if they are
tagged with a context so that their Next Actions can inherit it (e.g.,
home improvements are all tagged @Home).  This would work fine if I
didn't use tag inheritance, or was conscientious about not putting
contexts in projects.  The other thing I've tried is to make "Project"
a tag.  This obviously works only if one is not using tag
inheritance --- if you're not, then it's easy to get a list of
projects, but if you are, you'll get all your next actions, too.

What are other people doing to keep track of their projects?  Is
having projects listable all that important?

| Jason F. McBrayer                    jmcbray@carcosa.net  |
| A flower falls, even though we love it; and a weed grows, |
| even though we do not love it.            -- Dogen        |

  reply	other threads:[~2006-08-03 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  6:35 Org-mode 4.43 Carsten Dominik
2006-08-03 20:36 ` Jason F. McBrayer [this message]
2006-08-04 12:59   ` GTD, Projects, and Next Actions in org-mode Tim O'Callaghan
2006-08-04 13:38   ` Piotr Zielinski
2006-08-10  5:42     ` Carsten Dominik
2006-08-10  9:14       ` Tim O Callaghan
2006-08-10 12:32         ` Carsten Dominik
2006-08-05  0:56   ` Claudine Chionh
2006-08-07 17:32   ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1wt9pr1y4.fsf@bertrand.carcosa.net \
    --to=jmcbray@carcosa.net \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).