From: Mike McLean <mike.mclean@pobox.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Valid use cases for lists?
Date: Thu, 20 Aug 2015 11:18:43 -0400 [thread overview]
Message-ID: <CANid5Q44-5A8TWoNqj9tBxe74055q15t8sP1NqHjP=KE2Lye0Q@mail.gmail.com> (raw)
In-Reply-To: <878u97gija.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Wed, Aug 19, 2015 at 3:55 PM, Rasmus <rasmus@gmx.us> wrote:
> Chris Patti <cpatti@gmail.com> writes:
>
> > I'm guessing I'm missing something obvious here, and that's why I'm
> asking.
>
> Export. List are used everywhere.
>
I also use them for “simple” projects. I have a set of Task TODO keywords
for one-off tasks. I have a set of Project TODO keywords for projects.
Typically a project is a heading with a Project keyword and a number of
(level + 1) headings with Task keywords. For projects that span several
days/weeks this works well.
Some things that I do fall between Project and Task in the complexity. The
items needs 1-2 things done and discrete and different points in time
(temporal dependency, first A then B) or with different co workers
(collaboration) or both. The overall work, however, will only take 0-2
days. It's too big for a single task. It's too small for a Project. It's
related items that conceptually belong together. In Goldilocks fashion, a
check-box list is just the right size.
#+begin_example
** TODO Medium Sized “project” [1/3]
- [X] Get information from John
- [ ] Process information and send to Mary for review
- [ ] Finalize and submit final to Joe (based on Mary’s comments and
changes)
#+end_example
[-- Attachment #2: Type: text/html, Size: 1798 bytes --]
next prev parent reply other threads:[~2015-08-20 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 19:32 Valid use cases for lists? Chris Patti
2015-08-19 19:55 ` Rasmus
2015-08-20 15:18 ` Mike McLean [this message]
2015-08-21 3:59 ` Peter Salazar
2015-08-21 18:39 ` Rasmus
2015-08-23 17:18 ` Peter Salazar
2015-08-19 20:00 ` Kyle Meyer
2015-08-19 21:02 ` Florian Beck
2015-08-20 14:06 ` Matt Lundin
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='CANid5Q44-5A8TWoNqj9tBxe74055q15t8sP1NqHjP=KE2Lye0Q@mail.gmail.com' \
--to=mike.mclean@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).