From: Gareth Smith <gds@doc.ic.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Collaborating with TODO lists and clocks.
Date: Mon, 29 Apr 2013 21:34:39 +0100 [thread overview]
Message-ID: <87txmpoz34.fsf@doc.ic.ac.uk> (raw)
In-Reply-To: <87obcybgmc.fsf@berkeley.edu> (Richard Lawrence's message of "Sun, 28 Apr 2013 12:27:23 -0700")
Thanks for the reply Richard!
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> Is there a reason you don't want any clock data to end up in the shared
> tasks.org?
>
> If not, one thing you could do is:
>
> 1) When claiming a task, each person uses a tag for their name (in
> addition to, or instead of, just changing the TODO state). Then that
> person "owns" the clock data for that task.
>
> 2) Then use the :tags option on a clock table to filter the clock data
> for just the tasks you personally have worked on; each person can have
> their own table (in tasks.org).
That sounds like a good idea - thanks!
I hadn't thought of using :tags on a clock table. I still worry if we'll
find ourselves in a situation where more than one of us has clocked in
some time on the same task.
For example, often I clock into a task while I do the work of
sub-dividing it into smaller tasks. And often when I'm actively working
on a task, I'll create a sub-task of my current-clocked-task on the
fly. It seems to me that if I continue with this sort of working
practice, and attempt to collaborate with others who work similarly,
then we might quickly find that it's not easy to describe a given task
(or even subtask) as being "owned" by a single person.
Again, perhaps my workflow is at fault, and I should be organising
myself in a more principled way. And perhaps in practice I'll find that
tasks do tend to be owned by just one person anyway.
Thanks for the quick reply!
Gareth.
> For example, suppose you have a task like:
>
> * TODO Frobnicate something
>
> You claim it by changing that to:
>
> * IN_PROGRESS Frobnicate something :gareth:
>
> Check that in, then start your clock in this tree.
>
> Somewhere else in the file, you have a clock table like:
>
> #+BEGIN: clocktable :maxlevel 3 :scope file :tags "+gareth"
> #+CAPTION: Gareth's working time on all tasks
> # ...
> #+END:
>
> which will show you the clock data for just the tasks you've worked on
> (i.e., are tagged in).
next prev parent reply other threads:[~2013-04-29 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 18:30 Collaborating with TODO lists and clocks Gareth Smith
2013-04-28 19:27 ` Richard Lawrence
2013-04-29 20:34 ` Gareth Smith [this message]
2013-04-30 1:50 ` Richard Lawrence
2013-04-30 18:21 ` Gareth Smith
2013-09-05 7:31 ` Samuel Loury
2013-09-05 7:42 ` Sebastien Vauban
2013-09-05 8:52 ` Samuel Loury
2013-09-05 11:22 ` Sebastien Vauban
2013-09-05 11:54 ` Thorsten Jolitz
2013-09-05 13:32 ` Samuel Loury
2013-09-05 13:29 ` Samuel Loury
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=87txmpoz34.fsf@doc.ic.ac.uk \
--to=gds@doc.ic.ac.uk \
--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).