emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Hellekin O. Wolf" <hellekin@cepheide.org>
To: emacs-orgmode@gnu.org
Subject: AutOrg, and practice of GTD in a group
Date: Tue, 22 Jun 2010 21:19:41 +0000	[thread overview]
Message-ID: <20100622211941.GF520@now.cepheide.org> (raw)

Hello list,

I'm quite impressed posting on this list of genious coders who brought
such a powerful tool as org-mode.  Not honey-licking your shoes.
Being allergic to linear time and its implementation (calendars,
clocks...), I found org-mode of great help when dealing with normal
people.

Using the ! flag to Orgmode TODO states, I can track time without
having to look at it.  Wew!

But let's get to the point.  Jaromil, Yaakov and I started AutOrg, as
a way to combine different goals, the main drive being Yaakov wanting
us to use GTD in org-mode.  Thus we started thinking about AutOrg, an
autonomous, distributed information system based on Orgmode and Git.

One of the obvious issue that came up concerns the ways to "share
GTD", i.e. to apply it to groups.  GTD is a methodology for the
individual, and each individual tends to tailor it to her own
world-view.  I explain the kind of issues more in depth in the AutOrg
documentation[1], but I want to keep this reasonably short.

How do you guys use CATEGORIES, PROPERTIES and TAGS in combination
with TODO states and Org-Agenda to optimize your GTD workflow?

What strategy do you take when you have a personal SEQ_TODO and need
to work with other people, using a different SEQ_TODO?

Cheers,

==
hk

[1] http://code.dyne.org/index.cgi?url=autorg/tree/doc/TODO.org
section "GTD for groups"

             reply	other threads:[~2010-06-22 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:19 Hellekin O. Wolf [this message]
2010-06-22 22:09 ` AutOrg, and practice of GTD in a group 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
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=20100622211941.GF520@now.cepheide.org \
    --to=hellekin@cepheide.org \
    --cc=emacs-orgmode@gnu.org \
    /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).