From: Bernt Hansen <firstname.lastname@example.org>
To: Xavier Maillard <email@example.com>
Subject: Re: Example of a project for you?
Date: Wed, 12 Aug 2009 09:32:56 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Xavier Maillard's message of "Wed\, 12 Aug 2009 15\:14\:32 +0200")
[cced the org-mode mailing list since this might be useful for other people]
"Xavier Maillard" <firstname.lastname@example.org> writes:
> I read your org-mode tutorial which I found just great.
> Could you explain to me what you really call a project ? (and give an
> example of what it looks like in org-mode)
Everything is a project. A project is just a task. All of my TODO
tasks start at level 2
** TODO Some Project
*** TODO Step 1 :NEXT:
*** TODO Step 2
My stuck projects view complains about any level 2 task (or level 1
refile task) that does not have a :NEXT: task under it and is not
scheduled for a specific day.
i.e. If there was no :NEXT: task then the stuck projects view would say
that 'Some Project' was stuck and needs the next task defined.
If it's a simple task with a known scheduled/deadline date then I just
create the date and it keeps it off the stuck projects list. It will
show up in my agenda with an appropriate lead time.
If it's a simple task without a date I can just give it a :NEXT: task
** TODO Simple Task :NEXT:
and it's no longer stuck. I can work on it anytime when I pick stuff
off my NEXT task agenda view.
I don't want to explicitly say 'this thing is a project'. That's an
extra step I don't need. A project isn't special in any way for me -- I
group tasks into separate org files to keep them logically together. I
normally don't think about projects and tasks separately - everything is
a project and I create NEXT tags on tasks to make them all unstuck.
Does that help?
next parent reply other threads:[~2009-08-12 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2009-08-12 13:32 ` Bernt Hansen [this message]
2009-08-14 13:23 ` Example of a project for you? Xavier Maillard
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 \
* 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).