From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: What do you use to identify projects (in the GTD sense) Date: Mon, 10 Oct 2011 01:21:57 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0015174c18b8d9ae6804aeebcec1 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:46194) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RD9FQ-0007Z8-Rh for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 02:22:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RD9FQ-0002d5-17 for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 02:22:00 -0400 Received: from mail-bw0-f41.google.com ([209.85.214.41]:61459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RD9FP-0002d1-Hu for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 02:21:59 -0400 Received: by bkbzs2 with SMTP id zs2so9025001bkb.0 for ; Sun, 09 Oct 2011 23:21:58 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode --0015174c18b8d9ae6804aeebcec1 Content-Type: text/plain; charset=ISO-8859-1 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. --0015174c18b8d9ae6804aeebcec1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey list,

I'm wondering if you make the distinction = between projects and actionable items. If you stop to think about it (speci= ally if you read GTD by David Allen), you see that you can't really &qu= ot;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 t= hings, 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.=A0

Anyway, I was wondering how you guys differentiate betw= een 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. Proj= ects never have a todo keyword, except when DONE. I used to use a PROJECT k= eyword before, but I felt that a tag seems to work better (and allows you t= o actually filter todos without mixing projects). So, a typical list looks = like this:

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

How do you do it= ?=A0

Thanks in advance,

-= Marcelo.
--0015174c18b8d9ae6804aeebcec1--