From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Example of a project for you? Date: Wed, 12 Aug 2009 09:32:56 -0400 Message-ID: <87hbwdjgxj.fsf@gollum.intra.norang.ca> References: <1250082872.31429.1329496389@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbDwy-00015i-29 for emacs-orgmode@gnu.org; Wed, 12 Aug 2009 09:33:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbDwt-00014G-Hs for emacs-orgmode@gnu.org; Wed, 12 Aug 2009 09:33:06 -0400 Received: from [199.232.76.173] (port=51190 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbDwt-00014C-CJ for emacs-orgmode@gnu.org; Wed, 12 Aug 2009 09:33:03 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:55773) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MbDwt-0000nz-2y for emacs-orgmode@gnu.org; Wed, 12 Aug 2009 09:33:03 -0400 In-Reply-To: <1250082872.31429.1329496389@webmail.messagingengine.com> (Xavier Maillard's message of "Wed\, 12 Aug 2009 15\:14\:32 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Xavier Maillard Cc: emacs-orgmode@gnu.org [cced the org-mode mailing list since this might be useful for other people] "Xavier Maillard" 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) Hi Xavier, Everything is a project. A project is just a task. All of my TODO tasks start at level 2 * Miscellaneous ** 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? Regards, Bernt