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

[Stephanie McCammon <[e-mail]>]

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

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