emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: What do you use to identify projects (in the GTD sense)
Date: Mon, 10 Oct 2011 01:21:57 -0500	[thread overview]
Message-ID: <CACHMzOHa8=ehOA3y+0kmJHVcfi0oN-RbC1_BObGXRaJoCG_sWg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Hey list,

I'm wondering if you make the distinction between projects and actionable
items. If you stop to think about it (specially if you read GTD by David
Allen), you see that you can't really "do" a project, but only actions
related to it. It's a powerful and underestimated concept. Of course, a todo
list is still a reminder of things, and any list can be useful, but the more
specific you are, the less you have to think (process) and the more you can
actually execute.

Anyway, I was wondering how you guys differentiate between projects and next
actions (todo's) in your org lists. I myself use a :project: tag for
projects and todos have todo keywords before them. Projects never have a
todo keyword, except when DONE. I used to use a PROJECT keyword before, but
I felt that a tag seems to work better (and allows you to actually filter
todos without mixing projects). So, a typical list looks like this:

* New feature :project:
** TODO Create a mockup for the index page
** TODO Convert the mockup to html
* Renew passport :project:
** DONE Call for appointment
** TODO Interveiw
    SCHEDULED <...>
** DONE Buy groceries :project: ...

How do you do it?

Thanks in advance,

- Marcelo.

[-- Attachment #2: Type: text/html, Size: 1454 bytes --]

             reply	other threads:[~2011-10-10  6:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10  6:21 Marcelo de Moraes Serpa [this message]
2011-10-10 11:30 ` What do you use to identify projects (in the GTD sense) Daniel Bausch
2011-10-10 18:44   ` Marcelo de Moraes Serpa
2011-10-11  6:20     ` Daniel Bausch
2011-10-11  1:28 ` Bernt Hansen
2011-10-11  8:16   ` Sven Bretfeld
2011-12-11 16:49   ` Viktor Rosenfeld
2011-12-11 22:18     ` Bernt Hansen
2011-12-12 18:29       ` Viktor Rosenfeld
2011-12-12 19:58         ` Bernt Hansen
2011-12-15 14:41         ` Defining dependencies (was: What do you use to identify projects (in the GTD sense)) Karl Voit

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='CACHMzOHa8=ehOA3y+0kmJHVcfi0oN-RbC1_BObGXRaJoCG_sWg@mail.gmail.com' \
    --to=celoserpa@gmail.com \
    --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).