From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gareth Smith Subject: Re: Collaborating with TODO lists and clocks. Date: Mon, 29 Apr 2013 21:34:39 +0100 Message-ID: <87txmpoz34.fsf@doc.ic.ac.uk> References: <87li82se2b.fsf@totherme.org> <87obcybgmc.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWumd-0002Lg-B9 for emacs-orgmode@gnu.org; Mon, 29 Apr 2013 16:34:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UWumZ-0008NY-AS for emacs-orgmode@gnu.org; Mon, 29 Apr 2013 16:34:47 -0400 Received: from smtp1.cc.ic.ac.uk ([155.198.5.155]:40250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWumZ-0008NF-5N for emacs-orgmode@gnu.org; Mon, 29 Apr 2013 16:34:43 -0400 Received: from host86-162-179-23.range86-162.btcentralplus.com ([86.162.179.23] helo=localhost) by smtp1.cc.ic.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1UWumW-0000Mh-0I for emacs-orgmode@gnu.org; Mon, 29 Apr 2013 21:34:40 +0100 In-Reply-To: <87obcybgmc.fsf@berkeley.edu> (Richard Lawrence's message of "Sun, 28 Apr 2013 12:27:23 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Thanks for the reply Richard! Richard Lawrence 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).