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

Stephanie McCammon <smccammon@amsl.com> Fri, 15 April 2011 20:23 UTC

Return-Path: <smccammon@amsl.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 EE18CE0687 for <yaco-liaison-tool@ietfc.amsl.com>; Fri, 15 Apr 2011 13:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 Ezcb3NJPODN2 for <yaco-liaison-tool@ietfc.amsl.com>; Fri, 15 Apr 2011 13:23:49 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id D1192E0682 for <yaco-liaison-tool@ietf.org>; Fri, 15 Apr 2011 13:23:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 7CF40E08A8; Fri, 15 Apr 2011 13:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YR8JLC6ej0d; Fri, 15 Apr 2011 13:23:48 -0700 (PDT)
Received: from [64.170.98.157] (unknown [64.170.98.157]) by c1a.amsl.com (Postfix) with ESMTPSA id 449CFE08B6; Fri, 15 Apr 2011 13:23:48 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-10-321796933
From: Stephanie McCammon <smccammon@amsl.com>
In-Reply-To: <4DA46F99.6010802@yaco.es>
Date: Fri, 15 Apr 2011 13:23:47 -0700
Message-Id: <619C8DA6-16B4-461E-B901-71AFC8900354@amsl.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> <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>
To: =?iso-8859-1?Q?Emilio_A=2E_S=E1nchez?= <esanchez@yaco.es>
X-Mailer: Apple Mail (2.1082)
Cc: yaco-liaison-tool@ietf.org, adrian@olddog.co.uk, Eliot Lear <lear@cisco.com>, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <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: Fri, 15 Apr 2011 20:23:53 -0000


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/>
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 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/>
>> 
>> 
>> 
> 

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