From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: Re: What do you use to identify projects (in the GTD sense) Date: Mon, 10 Oct 2011 13:44:46 -0500 Message-ID: References: <201110101330.44437.DanielBausch@gmx.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0015174789dc5d39a804aef62fb6 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:49055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDKqI-0002Qd-Dm for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 14:44:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDKqG-0003eR-9o for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 14:44:50 -0400 Received: from mail-bw0-f41.google.com ([209.85.214.41]:61728) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDKqF-0003eA-VN for emacs-orgmode@gnu.org; Mon, 10 Oct 2011 14:44:48 -0400 Received: by bkbzs2 with SMTP id zs2so9842809bkb.0 for ; Mon, 10 Oct 2011 11:44:46 -0700 (PDT) In-Reply-To: <201110101330.44437.DanielBausch@gmx.de> 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: Daniel Bausch Cc: emacs-orgmode@gnu.org --0015174789dc5d39a804aef62fb6 Content-Type: text/plain; charset=ISO-8859-1 Hi Daneil, Looks interesting. Could you share a sample tree with projects and actions? Cheers, - Marcelo. On Mon, Oct 10, 2011 at 6:30 AM, Daniel Bausch wrote: > Hello, > > I use a todo keyword "PROJ" and a custom block agenda, that filters > different > interesting groups for review. > > (setq org-agenda-custom-commands > '(("g" "My GTD Agenda" > ((agenda "" ((org-agenda-ndays 1) > (org-agenda-start-on-weekday nil) > (org-agenda-entry-types '(:timestamp :sexp)) > (org-agenda-overriding-header "Appointments"))) > (agenda "" ((org-agenda-ndays 1) > (org-agenda-start-on-weekday nil) > (org-agenda-entry-types '(:deadline)) > (org-agenda-overriding-header "Upcoming Deadlines") > (org-agenda-sorting-strategy '(priority-down > time-down)) > (org-agenda-skip-function '(org-agenda-skip-entry-if > 'todo > 'done)))) > (agenda "" ((org-agenda-ndays 1) > (org-agenda-start-on-weekday nil) > (org-agenda-entry-types '(:scheduled)) > (org-agenda-overriding-header "Scheduled") > (org-agenda-sorting-strategy '(priority-down > time-down)) > (org-agenda-skip-function '(org-agenda-skip-entry-if > 'todo > 'done)))) > (todo "WAIT" ((org-agenda-sorting-strategy '(priority-down)) > (org-agenda-overriding-header "Waiting For"))) > (todo "NEXT" ((org-agenda-sorting-strategy '(priority-down effort- > down)) > (org-agenda-skip-function '(org-agenda-skip-entry-if > 'scheduled 'deadline)) > (org-agenda-overriding-header "Next actions not > being > scheduled nor having a deadline"))) > (todo "TODO" ((org-agenda-sorting-strategy '(priority-down effort- > down)) > (org-agenda-skip-function '(org-agenda-skip-entry-if > 'scheduled 'deadline)) > (org-agenda-overriding-header "Future actions not > being scheduled nor having a deadline"))) > (todo "PROJ" ((org-agenda-overriding-header "Active > Projects"))))))) > > > Along with colors > > '(org-todo-keyword-faces (quote (("PROJ" :foreground "Orange" :weight > bold) > ("MSTN" :foreground "VioletRed" :weight bold) ("WAIT" :foreground "Blue" > :weight bold) ("CNCL" :foreground "MediumSeaGreen" :weight bold)))) > > and > > '(org-enforce-todo-checkbox-dependencies t) > '(org-enforce-todo-dependencies t) > > this works really well for GTD. > > Kind regards, > Daniel > > Am Montag 10 Oktober 2011, 08:21:57 schrieb Marcelo de Moraes Serpa: > > 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. > > > > --0015174789dc5d39a804aef62fb6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Daneil,

Looks interesting. Could you share a sample t= ree with projects and actions?

Cheers,
<= br>
- Marcelo.

On Mon, Oct 10, = 2011 at 6:30 AM, Daniel Bausch <DanielBausch@gmx.de> wrote:
Hello,

I use a todo keyword "PROJ" and a custom block agenda, that filte= rs different
interesting groups for review.

(setq org-agenda-custom-commands
=A0 =A0 =A0'(("g" "My GTD Agenda"
=A0 =A0 =A0 =A0 ((agenda "" ((org-agenda-ndays 1)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-start-on-weekday ni= l)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-entry-types '(:= timestamp :sexp))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-header &= quot;Appointments")))
=A0 =A0 =A0 =A0 =A0(agenda "" ((org-agenda-ndays 1)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-start-on-weekday ni= l)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-entry-types '(:= deadline))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-header &= quot;Upcoming Deadlines")
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-sorting-strategy &#= 39;(priority-down time-down))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-skip-function '= (org-agenda-skip-entry-if 'todo
'done))))
=A0 =A0 =A0 =A0 =A0(agenda "" ((org-agenda-ndays 1)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-start-on-weekday ni= l)
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-entry-types '(:= scheduled))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-header &= quot;Scheduled")
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-sorting-strategy &#= 39;(priority-down time-down))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-skip-function '= (org-agenda-skip-entry-if 'todo
'done))))
=A0 =A0 =A0 =A0 =A0(todo "WAIT" ((org-agenda-sorting-strategy &#= 39;(priority-down))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-head= er "Waiting For")))
=A0 =A0 =A0 =A0 =A0(todo "NEXT" ((org-agenda-sorting-strategy &#= 39;(priority-down effort-
down))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-skip-function &= #39;(org-agenda-skip-entry-if
'scheduled 'deadline))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-head= er "Next actions not being
scheduled nor having a deadline")))
=A0 =A0 =A0 =A0 =A0(todo "TODO" ((org-agenda-sorting-strategy &#= 39;(priority-down effort-
down))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-skip-function &= #39;(org-agenda-skip-entry-if
'scheduled 'deadline))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(org-agenda-overriding-head= er "Future actions not
being scheduled nor having a deadline")))
=A0 =A0 =A0 =A0 =A0(todo "PROJ" ((org-agenda-overriding-header &= quot;Active Projects")))))))


Along with colors

=A0'(org-todo-keyword-faces (quote (("PROJ" :foreground "= ;Orange" :weight bold)
("MSTN" :foreground "VioletRed" :weight bold) ("WA= IT" :foreground "Blue"
:weight bold) ("CNCL" :foreground "MediumSeaGreen" :wei= ght bold))))

and

=A0'(org-enforce-todo-checkbox-dependencies t)
=A0'(org-enforce-todo-dependencies t)

this works really well for GTD.

Kind regards,
Daniel

Am Montag 10 Oktober 2011, 08:21:57 schrieb Marcelo de Moraes Serpa:
> Hey list,
>
> I'm wondering if you make the distinction between projects and act= ionable
> items. If you stop to think about it (specially if you read GTD by Dav= id
> Allen), you see that you can't really "do" a project, bu= t only actions
> related to it. It's a powerful and underestimated concept. Of cour= se, a
> todo list is still a reminder of things, and any list can be useful, b= ut
> the more specific you are, the less you have to think (process) and th= e
> more you can actually execute.
>
> Anyway, I was wondering how you guys differentiate between projects an= d
> 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 t= his:
>
> * 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
> =A0 =A0 SCHEDULED <...>
> ** DONE Buy groceries :project: ...
>
> How do you do it?
>
> Thanks in advance,
>
> - Marcelo.




--0015174789dc5d39a804aef62fb6--