Re: [yaco-liaison-tool] The liaison tool: Status Update

"Emilio A. Sánchez" <esanchez@yaco.es> Thu, 07 April 2011 09:06 UTC

Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-liaison-tool@core3.amsl.com
Delivered-To: yaco-liaison-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1A0B28C113 for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 02:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.967
X-Spam-Level:
X-Spam-Status: No, score=-1.967 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZqnm3Cpf3La for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 02:06:20 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 0F7253A68F4 for <yaco-liaison-tool@ietf.org>; Thu, 7 Apr 2011 02:06:19 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1941629wwa.13 for <yaco-liaison-tool@ietf.org>; Thu, 07 Apr 2011 02:08:03 -0700 (PDT)
Received: by 10.227.42.143 with SMTP id s15mr624066wbe.143.1302167283394; Thu, 07 Apr 2011 02:08:03 -0700 (PDT)
Received: from [192.168.0.197] ([77.227.215.107]) by mx.google.com with ESMTPS id y29sm902334wbd.38.2011.04.07.02.08.00 (version=SSLv3 cipher=OTHER); Thu, 07 Apr 2011 02:08:01 -0700 (PDT)
Message-ID: <4D9D7EFC.8040503@yaco.es>
Date: Thu, 07 Apr 2011 11:08:12 +0200
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <pfaltstr@cisco.com>
References: <4D483171.7090508@levkowetz.com> <A9723AE7-F5B8-4722-BBB6-80F71C6AED31@amsl.com> <4D485061.3090204@levkowetz.com> <1FD00AF1-C1C6-4D33-9E70-E2B3D3ED11A6@cisco.com> <4D494292.1000809@levkowetz.com> <D4C88766-1C27-4212-B833-EF9F3B06452C@cisco.com> <4D49D50A.9000408@levkowetz.com> <18D7B1E6-2A70-4C5A-8C0E-9D43AD489599@cisco.com> <4D4B0946.7070302@levkowetz.com> <AF68B07C-FB34-4B7D-B710-848C710E20E1@cisco.com> <4D4BB18F.8020808@yaco.es> <09D40B0B-3058-4416-AC88-49C072EE93E0@cisco.com> <1EA3B690-E6A3-4988-8D2A-8A73147117EA@amsl.com> <C09F0708-AD85-4B96-BB63-537DE1936373@cisco.com> <4D9C5C79.40904@levkowetz.com> <4D9C72BB.8020605@yaco.es> <4D9D74E6.3080808@levkowetz.com> <37685D0B-E5C4-4AAF-AF3F-CA61663D789B@cisco.com>
In-Reply-To: <37685D0B-E5C4-4AAF-AF3F-CA61663D789B@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: yaco-liaison-tool@ietf.org, Eliot Lear <lear@cisco.com>, Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [yaco-liaison-tool] The liaison tool: Status Update
X-BeenThere: yaco-liaison-tool@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of the Yaco / Liaison Statement Management Tool Project details <yaco-liaison-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yaco-liaison-tool>, <mailto:yaco-liaison-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-liaison-tool>
List-Post: <mailto:yaco-liaison-tool@ietf.org>
List-Help: <mailto:yaco-liaison-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-liaison-tool>, <mailto:yaco-liaison-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2011 09:06:20 -0000

    Hi Patrik,

El 07/04/11 10:34, Patrik Fältström escribió:
> On 7 apr 2011, at 10.25, Henrik Levkowetz wrote:
>
>> Hi Emilio,
>>
>> On 2011-04-06 16:03 "Emilio A. Sánchez" said:
>> ...
>>
>>>     I don't understand what data want's to edit Patrik when he say 'who
>>> holds the action item'. If he refers to the person who can 'take care'
>>> of a liaison, this person is selected automatically.
>>
>> But if the SDO Liaison Manager is changing, then liaisons which still
>> need to be taken care of will need to be updated, no?
>
> Any individual that have a role that have edit access to certain liaisons (depending on whether the liaison is incoming, outgoing and what external organisation is involved) must be able to update the action date and responsible person (that holds the token of action).

    If you can edit a liaison then you can change its deadline date.

> I have also seen cases when for example responses of some kind of liaisons have been added without having "link to older liaison" has not been set, so that kind of "cleanup" must also be possible.

    Same here, if you can edit the liaison then you can add the 
reference to other liaison.

> For example, as liaison to Unicode Consortium from IETF, I should have such edit rights on the liaisons that have to do with Unicode Consortium (in or out).
>
> ITU-T liaison (Eliot) should have such edit rights to any ITU-T related liaison.
>
> Normally otherwise, an individual only have edit rights to either liaisons they have posted, or liaisons they are token holders of.
>
> Or something like that.
>
> The important thing is to be able to update the liaisons. And we can trust our (IETF) liaisons, so to get fine-grained access rights is not so important. The ability to get things right in the database is. Having bad data in the database -- as now -- is not working in the long(er) run.

    I suppose, as I said in my previous mail, that the problem is who 
can 'take care' (mark as done) a liaison. Right now this action can be 
done by anyone whose email is listed in the liaison. But probably I 
should add the people that can edit the liaison to the ones that can 
'take care' of it.

    Best,

>     Patrik
>