From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tim Cross <theophilusx@gmail.com>
Subject: Re: @name-tags instead of TODO keywords to assign people (was: Org
 mode for meeting minutes)
Date: Mon, 04 Nov 2019 08:03:21 +1100
Message-ID: <87r22ooep2.fsf@gmail.com>
References: <87imo5j9ks.fsf@sbs.ch> <2019-11-03T21-44-51@devnull.Karl-Voit.at>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:52259)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <theophilusx@gmail.com>) id 1iRN24-0004qy-CP
 for emacs-orgmode@gnu.org; Sun, 03 Nov 2019 16:03:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <theophilusx@gmail.com>) id 1iRN22-0004gv-Ca
 for emacs-orgmode@gnu.org; Sun, 03 Nov 2019 16:03:31 -0500
Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]:44920)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <theophilusx@gmail.com>)
 id 1iRN20-0004gV-CU
 for emacs-orgmode@gnu.org; Sun, 03 Nov 2019 16:03:29 -0500
Received: by mail-pg1-x52f.google.com with SMTP id f19so813211pgk.11
 for <emacs-orgmode@gnu.org>; Sun, 03 Nov 2019 13:03:27 -0800 (PST)
In-reply-to: <2019-11-03T21-44-51@devnull.Karl-Voit.at>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Karl Voit <news1142@Karl-Voit.at>
Cc: emacs-orgmode@gnu.org

+1. This is how I do it as well. This approach makes it easier to not
only see what tasks have been assigned to what people, it also provides
a way to generate a custom agenda (report) showing what tasks each has
and what the state is for each task.

Tim
Karl Voit <devnull@Karl-Voit.at> writes:

> * Christian Egli <christian.egli@sbs.ch> wrote:
>>     
>> The idea is that you use type todos using the people involved at the
>> meeting. Below is an example how this could look:
>>
>> ``` org
>> #+title: Meeting minutes
>>
>> #+TYP_TODO: Fred Sara Lucy Mike | DONE
>
> I'd challenge the decisions on using TODO keywords for people
> although the Org manual also suggests to do so.
>
> TODO keywords are single classification. This means that you are not
> able to assign more than one person to a task. I'm using @tags for
> the same purpose which allows me to assign tasks to more than one
> person and keep TODO keywords independent to the person. For
> example, when you resolve a task, you lose the information who was
> assigned to the task.
>
> Therefore, I'd use:
>
> * Meeting
>
> ** TODO Prepare the demo     :@Fred:
> ** STARTED Contact customer  :@Sara:
> ** TODO Work on the document :@Fred:@Lucy:@Mike:
>
> More on that on
> https://karl-voit.at/2019/09/25/categories-versus-tags/ including an
> elisp snippet I'm using to filter according to @name-tags.
>
> YMMV. HTH.


-- 
Tim Cross