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

Henrik Levkowetz <henrik@levkowetz.com> Mon, 18 April 2011 06:58 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-liaison-tool@ietfc.amsl.com
Delivered-To: yaco-liaison-tool@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id B1571E0655 for <yaco-liaison-tool@ietfc.amsl.com>; Sun, 17 Apr 2011 23:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.676
X-Spam-Level:
X-Spam-Status: No, score=-101.676 tagged_above=-999 required=5 tests=[AWL=-0.773, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDyfcf7+J0W3 for <yaco-liaison-tool@ietfc.amsl.com>; Sun, 17 Apr 2011 23:58:31 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfc.amsl.com (Postfix) with ESMTP id BA645E078A for <yaco-liaison-tool@ietf.org>; Sun, 17 Apr 2011 23:58:30 -0700 (PDT)
Received: from 146.scnet.cz ([217.117.217.146]:56540 helo=[192.168.2.75]) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.75) (envelope-from <henrik@levkowetz.com>) id 1QBiPA-0007Ai-WF; Mon, 18 Apr 2011 08:57:57 +0200
References: <4D483171.7090508@levkowetz.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> <4D9D7BBC.4030708@yaco.es> <4D9D80D5.50302@levkowetz.com> <4D9D85CF.1030100@yaco.es> <4D9DA1B6.6010103@levkowetz.com> <54B04D20-1849-400D-9690-0926EBD944F1@amsl.com> <4DA2CAF1.8080608@yaco.es> <2EEB40DE-A7E8-45E0-9194-6FE0DEFC8CF0@amsl.com> <4DA46F99.6010802@yaco.es> <619C8DA6-16B4-461E-B901-71AFC8900354@amsl.com> <4DABDA97.5000101@yaco.es>
In-Reply-To: <4DABDA97.5000101@yaco.es>
Mime-Version: 1.0 (iPhone Mail 8F190)
Content-Type: text/plain; charset=utf-8
Message-Id: <8D9BF66E-F63F-48D2-9DBC-E10B75855E5A@levkowetz.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (8F190)
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Mon, 18 Apr 2011 08:57:48 +0200
To: =?utf-8?Q?"Emilio_A._S=C3=A1nchez"?= <esanchez@yaco.es>
X-SA-Exim-Connect-IP: 217.117.217.146
X-SA-Exim-Rcpt-To: adrian@olddog.co.uk, lear@cisco.com, henrik@levkowetz.com, esanchez@yaco.es, amorris@amsl.com, smccammon@amsl.com, rpelletier@isoc.org, housley@vigilsec.com, pfaltstr@cisco.com, glen@amsl.com, yaco-liaison-tool@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: "yaco-liaison-tool@ietf.org" <yaco-liaison-tool@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Eliot Lear <lear@cisco.com>, =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <pfaltstr@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.12
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/options/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: Mon, 18 Apr 2011 06:58:35 -0000

Hi Emilio,

Aargh! Mea culpa! I'll merge and release the right one today.

Sorry!

    Henrik

On 18 Apr 2011, at 08:30, "Emilio A. Sánchez" <esanchez@yaco.es> wrote:

>   Hi Stephanie.
> 
>   It seems that Henrik merged an old branch. Well, this is good cause in that branch there were unmergched changes.
> 
>   Henrik, do you remember that you create a new liaison branch to work over the same tool currently deployed? The changeset that resolves Stephanie's problem is http://trac.tools.ietf.org/tools/ietfdb/changeset/3040
> 
>   Best,
> 
> El 15/04/11 22:23, Stephanie McCammon escribió:
>> 
>> 
>> Hello everyone,
>> 
>> Henrik was able to do the merge, however the tool is still not
>> functioning properly. It still tells me that I am not allowed to send a
>> liaison to the ITU-T SG 15. Please look into this as soon as you have a
>> chance.
>> 
>> Adrian,
>> 
>> The new liaison tool will not let me post the response liaison to the
>> ITU-T SG 15 regarding COM15-LS293-E, and while we are working this out
>> you may want to try posting it for yourself. The CC field should now be
>> editable for you. Please let me know if you have any questions.
>> 
>> Sincerely,
>> 
>> Stephanie
>> 
>> 
>> On Apr 12, 2011, at 8:28 AM, Emilio A. Sánchez wrote:
>> 
>>> Hi Stephanie.
>>> 
>>> The last fix is applied in a repository branch, it needs to be merged
>>> into trunk and then update the code of the production server.
>>> 
>>> Henrik, could you do the merge?
>>> 
>>> Best,
>>> 
>>> El 12/04/11 17:24, Stephanie McCammon escribió:
>>>> 
>>>> 
>>>> Hi Emilio,
>>>> 
>>>> I have just tried to post the liaison on behalf of Adrian Farrel and it
>>>> still says that I am not allowed to send it and reverts the form back to
>>>> saying that it is from me. Could you please look into this again?
>>>> 
>>>> Thank you,
>>>> 
>>>> Stephanie
>>>> 
>>>> 
>>>> On Apr 11, 2011, at 2:33 AM, Emilio A. Sánchez wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> I have fixed this issue in
>>>>> http://trac.tools.ietf.org/tools/ietfdb/ticket/648
>>>>> 
>>>>> Now the tool takes into account which user are you imporsonating in
>>>>> order to check if he/she is allowed to send a liaison to an specific
>>>>> SDO.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> El 08/04/11 19:58, Stephanie McCammon escribió:
>>>>>> 
>>>>>> 
>>>>>> Hello Everyone,
>>>>>> 
>>>>>> I just tried to post an outgoing liaison and received an error that
>>>>>> said
>>>>>> I was not allowed to send an outgoing liaison to ITU-T SG15. I was
>>>>>> attempting to post it on behalf of Adrian Farrel who is listed as the
>>>>>> liaison manager for ITU-T SG 15. Can this be fixed?
>>>>>> 
>>>>>> Thank you,
>>>>>> 
>>>>>> Stephanie
>>>>>> 
>>>>>> 
>>>>>> On Apr 7, 2011, at 4:36 AM, Henrik Levkowetz wrote:
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> On 2011-04-07 11:37 "Emilio A. Sánchez" said:
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> Right now the field person of the LiaisonDetail model stores the
>>>>>>>> PersonOrOrgInfo of the user that creates the liaison. The real one
>>>>>>>> so if
>>>>>>>> the secretariat is sending a liaisons the person field has the
>>>>>>>> secretariat user person.
>>>>>>>> 
>>>>>>>> But this info is not used to grant any privilege over the liaisons.
>>>>>>> 
>>>>>>> Ah. So that field could more properly have been called 'creator'. Ok.
>>>>>>> 
>>>>>>> Best,
>>>>>>> 
>>>>>>> Henrik
>>>>>>> 
>>>>>>>> Best,
>>>>>>>> 
>>>>>>>> El 07/04/11 11:16, Henrik Levkowetz escribió:
>>>>>>>>> Hi Emilio,
>>>>>>>>> 
>>>>>>>>> I'm not sure you, Patrik and myself are talking about the same thing
>>>>>>>>> here. See more below.
>>>>>>>>> 
>>>>>>>>> On 2011-04-07 10:54 "Emilio A. Sánchez" said:
>>>>>>>>>> Hi.
>>>>>>>>>> 
>>>>>>>>>> El 07/04/11 10:25, Henrik Levkowetz escribió:
>>>>>>>>>>> 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?
>>>>>>>>>> 
>>>>>>>>>> I'm revising the code. The persons who are allowed to 'take
>>>>>>>>>> care' of
>>>>>>>>>> a liaison are:
>>>>>>>>>> 
>>>>>>>>>> * The secretariat (always)
>>>>>>>>>> * Any person whose email is listed under 'cc', 'reply_to', 'poc',
>>>>>>>>>> 'response_contact', 'technical_contact' and the submitter. Of
>>>>>>>>>> course
>>>>>>>>>> only if this person has an user in the datatracker.
>>>>>>>>>> 
>>>>>>>>>> One option is edit one of this field (but this is so ugly).
>>>>>>>>>> 
>>>>>>>>>> I think that the best option is allow to the 'take care' a if the
>>>>>>>>>> current user is allowed to edit the liaison (This check is done
>>>>>>>>>> on the
>>>>>>>>>> fly and checks if the user is currently an sdo manager of the
>>>>>>>>>> liaison).
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> There's an entry in the LiaisonDetails class which is 'person'.
>>>>>>>>> This would be the person who holds the token to handle a liaison,
>>>>>>>>> maybe? If so, I think that's the entry Patrik would like to update.
>>>>>>>>> 
>>>>>>>>> But if this entry isn't used anywhere, then we need to figure out
>>>>>>>>> the distinction between the set of people who 'can take care of' a
>>>>>>>>> liaison, and the person who has the token.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Best,
>>>>>>>>> 
>>>>>>>>> Henrik
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> Stephanie McCammon
>>>>>> IETF Registrar
>>>>>> 48377 Fremont Blvd, Ste. 117
>>>>>> Fremont, CA 94538
>>>>>> T: +1.510.492.4081
>>>>>> F: +1.510.492.4001
>>>>>> 
>>>>>> Association Management Solutions (AMS)
>>>>>> Forum Management, Meeting, and Event Planning
>>>>>> www.amsl.com <http://www.amsl.com> <http://www.amsl.com>
>>>>>> <http://www.amsl.com/>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> Stephanie McCammon
>>>> IETF Registrar
>>>> 48377 Fremont Blvd, Ste. 117
>>>> Fremont, CA 94538
>>>> T: +1.510.492.4081
>>>> F: +1.510.492.4001
>>>> 
>>>> Association Management Solutions (AMS)
>>>> Forum Management, Meeting, and Event Planning
>>>> www.amsl.com <http://www.amsl.com> <http://www.amsl.com/>
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> Stephanie McCammon
>> IETF Registrar
>> 48377 Fremont Blvd, Ste. 117
>> Fremont, CA 94538
>> T: +1.510.492.4081
>> F: +1.510.492.4001
>> 
>> Association Management Solutions (AMS)
>> Forum Management, Meeting, and Event Planning
>> www.amsl.com <http://www.amsl.com/>
>> 
>> 
>> 
>