emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alex Bochannek <alexb@juniper.net>
To: emacs-orgmode@gnu.org
Subject: Another GTD question.
Date: Tue, 26 Sep 2006 13:03:35 -0700	[thread overview]
Message-ID: <ud59ipf8o.fsf@juniper.net> (raw)

I have been following a lot of the discussions about how people use
Org-mode to implement GTD. I am currently using a system that isn't
that different from it, but I am trying to figure out the "best" way
to use Org-mode for GTD.

Let us say that your primary use for your GTD org file is the lists,
which is what most people have reported they do. For the purpose of
this discussion I am leaving out the whole tickler file concept.

Looking at Charles Cave's example Web page, he uses a mix of grouping
projects and contexts in outlines. I am in a similar situation where
my first instinct would be to group all my work next actions under
specific headlines (e.g., hardware, software, etc.) since I work in
different areas.

In a way, GTD is somewhat fuzzy about how to address this. It's not
really a context since while I am at work, I can work on any number of
tasks in the different areas. The context talks about what it is I
need, where I need to be, or a type of activity. Maybe I overlooked
something, but it seems like another dimension to the problem.

How does this relate to Org-mode? In Org-mode I see different
approaches to how one could structure these lists:

- Outlines
- Tags
- ToDo keywords
- Categories (files)

They all have their pros and cons and I wonder if we could
collectively come up with a good usage model. Let me propose a couple
of items and that could be a starting point for discussion. I am
purposely trying to pick examples that should cover the common
categories listed in the book. I am also "borrowing" from Charles
Cave's page:

o Call the bank about personal statements
o Go to post office to buy stamps
o Wait for SysAdmin to finish server install
o Hang new pictures at home
o Discuss new development process with boss
o Read through vendor proposal
o Server Install project at work
o Install software upgrade on laptop
o Learn more about font-lock in Org-mode

The examples are fictional (well, except the last one), but I think
they are all plausible.

I am really looking forward to hear what people who are already using
GTD with Org-mode suggest and hope that those how are not familiar
with GTD may still find the discussion interesting.

Alex.

             reply	other threads:[~2006-09-26 20:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 20:03 Alex Bochannek [this message]
2006-09-27 12:39 ` Another GTD question Charles Cave
2006-09-29 10:07   ` Christopher Kuettner
2006-09-30  5:25   ` Alex Bochannek
2006-09-30 11:28     ` Carsten Dominik
2006-10-01 14:41       ` Piotr Zielinski
2006-10-02  8:58         ` Chris Lowis
2006-10-14  4:44       ` Alex Bochannek
2006-10-01 23:54     ` Charles Cave
2006-10-14  4:53       ` Alex Bochannek
2006-09-27 14:18 ` Uwe Jochum
2006-10-04 16:11 ` Carsten Dominik
2006-10-04 17:11   ` Piotr Zielinski
2006-10-20  7:54     ` Carsten Dominik
2006-10-21 20:54       ` Christopher Kuettner
     [not found]         ` <b71b18520610211738s297f8f79u227d2ce32e10d2d9@mail.gmail.com>
2006-10-22  0:39           ` Eddward DeVilla
2006-10-23  6:10             ` Carsten Dominik
2006-10-23  7:21               ` Xiao-Yong Jin
2006-10-23  7:36                 ` Carsten Dominik
2006-10-23 20:30                   ` Xiao-Yong Jin
2006-10-23 13:24               ` Eddward DeVilla
2006-10-22 11:28         ` Pete Phillips
2006-10-05 13:01   ` Jason F. McBrayer

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=ud59ipf8o.fsf@juniper.net \
    --to=alexb@juniper.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).