Org-mode mailing list
 help / color / mirror / Atom feed
From: (Thomas S. Dye)
To: M <>
Cc: emacs orgmode-mailinglist <>
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 11:39:13 -1000
Message-ID: <> (raw)
In-Reply-To: <> (M.'s message of "Tue, 22 Jan 2013 21:19:44 +0100")

Aloha M,

M <> writes:

> Hi,
> I'm working with org-mode to document my work and to keep track of tasks and
> projects.
> At the moment there are many little projects where I
> * get a text from someone (or write it myself)
> * have to read and edit it
> * send it oer email to 1 or 2 other colleagues which have to read / edit it
> * get it back and check the changes
> * maybe send the text again to the original author
> * then finally release the text for publication
> ... and you imagine, there is not only 1 such text at once but several of
> them.

A terrific source of ideas about how to organize projects with Org mode
is Bernt Hansen's web page,

See especially his section 6 about adding tasks quickly with Capture.

I organize projects something like this, where the first level heading
names the project and sub-headings are tasks or task groups for the

* Topic XYZ

** DONE Create text

** WAITING Revisions by Colleague ABC

** TODO Finalize text

** TODO Submit text

When something comes in via email, I quickly file it to, read
other emails, etc. Then, when convenient, I go through and
put things where they should go. Bernt's setup using ido makes it
possible to get to Topic XYZ quickly, where the choices can be narrowed
and the appropriate file location easily found.

I try to discipline myself so a DEADLINE or SCHEDULE is always attached
to a TODO item.  It is easy for me to skip the weekly project review
that the GTD approach recommends, and attaching DEADLINE and SCHEDULE
means that fewer things fall through the cracks.


Thomas S. Dye

  parent reply	other threads:[~2013-01-22 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 20:19 M
2013-01-22 21:14 ` Thorsten Jolitz
2013-01-22 21:39   ` Nicolas Richard
2013-01-22 21:56     ` Thorsten Jolitz
2013-01-22 21:40   ` M
2013-01-22 21:55     ` Thorsten Jolitz
2013-01-23  8:59     ` Tomas Hlavaty
2013-01-23 10:20     ` OT: using ZIP based files with git (was: How to deal with small projects which are often changing their status/ person) Karl Voit
2013-01-22 21:39 ` Thomas S. Dye [this message]
2013-01-22 22:27   ` How to deal with small projects which are often changing their status/ person M
2013-01-22 22:49     ` Thomas S. Dye
2013-01-23  1:59 ` Eric Abrahamsen
2013-01-23  9:15 ` Julian Burgos

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:

  List information:

* 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

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone