From: "Hellekin O. Wolf" <hellekin@cepheide.org>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: AutOrg, and practice of GTD in a group
Date: Thu, 24 Jun 2010 13:00:06 +0000 [thread overview]
Message-ID: <20100624130005.GB920@now.cepheide.org> (raw)
In-Reply-To: <87wrtqqmi5.fsf@gmx.ch>
Wow, thank you Sven...
On Wed, Jun 23, 2010 at 08:41:22AM +0200, Sven Bretfeld wrote:
>
> The third level is for the physical actions of the project. As you see,
> only the first has a todo keyword (NEXT). The others are dependent from
> the first (cannot be done before the first is done) and have only a
> context tag. My context tags include things like HOME, OFFICE, SHOPPING,
> TRAIN etc. When the first NEXT action is done, the next NEXT action in
> the list gains the NEXT todo keyword automatically; this is what the
> TRIGGER property cares for. In that way my Agenda Views (defined as
> NEXT/HOME, NEXT/OFFICE etc.) display only next actions that can be done
> immediately.
>
*** I like the concept of "chained actions" and the TRIGGER property.
Very smart, the auto-assignment to NEXT keeps you busy and focused,
and saves a number of key-strokes.
But I guess that implies multiple NEXT items. Do you maintain several
of those, or one per project? Maybe I'm wrong--I didn't even read the
GTD book thoroughly yet--but I like having *one* NEXT action, so that
I don't get stuck with too many "next" things. I can understand one
NEXT action per project, but several within a single project raises
internal warnings.
> As I'm working in a team, I have long searched for a way to tell Orgmode
> who is with me at a certain moment and display the things that have to
> be done together with the(se) person(s). I have recently discovered
> org-secretary for that purpose. For the above case, if Volkard enters my
> office, I tell Emacs that he is now with me, and a special agenda view
> displays all the things I want to do with him. This is what the "dowith"
> property is for.
>
*** All right, so I'm looking up org-secretary.el. I like this
approach.
> Apart from PROJECTS and contexts I have two more tags defined: BIGROCK
> and MIT. The first is given to projects that I want to concentrate on
> this week (never more than 3 projects contain that tag). MIT means "Most
> Important Thing (of the day)". I use this tag to mark three to four NEXT
> actions every night. These are the first things I care for on the next
> day.
>
*** So you do maintain multiple NEXT actions per project?
Thank you again for your invaluable input.
==
hk
next prev parent reply other threads:[~2010-06-24 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 21:19 AutOrg, and practice of GTD in a group Hellekin O. Wolf
2010-06-22 22:09 ` Bernt Hansen
2010-06-23 17:41 ` Hellekin O. Wolf
2010-06-23 6:41 ` Sven Bretfeld
2010-06-24 13:00 ` Hellekin O. Wolf [this message]
2010-06-24 13:21 ` Jason McBrayer
2010-06-27 20:16 ` Sven Bretfeld
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=20100624130005.GB920@now.cepheide.org \
--to=hellekin@cepheide.org \
--cc=emacs-orgmode@gnu.org \
--cc=sven.bretfeld@gmx.ch \
/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).