Re: [yaco-liaison-tool] Acceptance?

Alexa Morris <amorris@amsl.com> Wed, 13 October 2010 15:25 UTC

Return-Path: <amorris@amsl.com>
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 ABCE63A696F for <yaco-liaison-tool@core3.amsl.com>; Wed, 13 Oct 2010 08:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.23
X-Spam-Level:
X-Spam-Status: No, score=-3.23 tagged_above=-999 required=5 tests=[AWL=-0.632, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 BTrewk6zGHFw for <yaco-liaison-tool@core3.amsl.com>; Wed, 13 Oct 2010 08:25:22 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 6DDC23A6956 for <yaco-liaison-tool@ietf.org>; Wed, 13 Oct 2010 08:25:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 8E085E08BF; Wed, 13 Oct 2010 08:26:39 -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 khJ-Y+Na4ias; Wed, 13 Oct 2010 08:26:39 -0700 (PDT)
Received: from [192.168.0.193] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c1a.amsl.com (Postfix) with ESMTPSA id 394A7E07EF; Wed, 13 Oct 2010 08:26:39 -0700 (PDT)
Message-Id: <33823D34-F7E5-40E8-B714-D2B1ED067974@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: Emilio Sanchez <esanchez@yaco.es>
In-Reply-To: <AANLkTi=JvKzPJisrLDHDWL-_r0hAc3sq4B3oJ=+882cx@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--561247899
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 13 Oct 2010 08:26:37 -0700
References: <04B4A66E-0041-427C-9375-ECD05FC416A7@cisco.com> <AA92480F-8E45-4DBA-A439-0787D9631924@amsl.com> <AANLkTimzcpiY6UUWLdPh_4Yi-=gcFXtE1qJsq7hRbOtw@mail.gmail.com> <FD2245CE-F2BE-432F-B07C-73AA1503BB5F@amsl.com> <AANLkTinHeEBcXvGC+eMj1qcTqK=QaA4ORQBb7i6BOtw6@mail.gmail.com> <B70DD3FD80DB4F23A67BD76C2A4ACF2D@ams3mxglf1> <AANLkTi=JvKzPJisrLDHDWL-_r0hAc3sq4B3oJ=+882cx@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: yaco-liaison-tool@ietf.org
Subject: Re: [yaco-liaison-tool] Acceptance?
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: Wed, 13 Oct 2010 15:25:26 -0000

See inline:

On Oct 13, 2010, at 12:44 AM, Emilio Sanchez wrote:

>
>
> 3.  When you enter an outgoing liaison statement it doesn't seem to  
> show up in the liaison list once it is submitted.  However, if you  
> attempt to submit the same liaison a second time it says that a  
> liaison of that name has already been submitted.
>
>
>      When you send an outgoing liaison you have to mark that you  
> have prior approval to send it. There is a checkbox to do this.  
> Probably you didn't check it so the liaison is not public until  
> someone approves it. The person who can approve the liaison depends  
> on who you select the liaison comes from (If the liaison comes from  
> a WG then the Area director can approve, if it comes from the IETF  
> then the IETF chair should approve it.
>
>      If you check that checkbox when creating the liaison then is  
> supposed you have obtained prior approval so the liaison will go  
> public without any other user interaction.
>
>

This is very helpful, thanks! What should we do if we forget to click  
"obtained prior approval"? Would it be possible (or desirable?) to get  
a "you have not indicated that you have prior approval to post this  
liaison. If you do not, please obtain approval before proceeding" or  
some such warning? Otherwise it seems that it: 1) people may be  
confused about what step to take next or 2) the liaison may not get  
posted, without the person quite realizing it that they failed to post  
it correctly.


> Thank you.
>
> Sincerely,
>
> 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
>
>
>
> From: Emilio Sanchez [mailto:esanchez@yaco.es]
> Sent: Tuesday, October 12, 2010 1:20 PM
> To: Alexa Morris
> Cc: Henrik Levkowetz; Russ Housley; Stephanie McCammon
>
> Subject: Re: [yaco-liaison-tool] Acceptance?
>
>    I've manage to fix the server so you can try whenever you want :)
>
> 2010/10/12 Alexa Morris <amorris@amsl.com>
> Thanks! I'll check back tomorrow and spend some time playing in the  
> tool.
>
> Much appreciated,
> Alexa
>
> On Oct 12, 2010, at 1:12 PM, Emilio Sanchez wrote:
>
>>    Hi Alexa,
>>
>>    In the beta server beta.lsmt.yaco.es you have different test  
>> users (username/password):
>>
>> admin/admin
>> This user is an IETF Liaison Manager
>> external/external
>> This user is an SDO Manager of 3GPP and WIPO
>> This user is an SDO Authorized of IEEE 802 and Open Grid Forum
>> internal/internal
>> This user is the Area Director of the Application Area
>> This user is a Working Group Secretary of 'Performance Metrics for  
>> Other Layers' group.
>> internal2/internal2
>> This user is the IETF/IESG Chair
>> This user is the IAB Executive Chair
>>     Probably you want to use admin/admin cause this user is able to  
>> do almost anything.
>>
>>     By the way, it seems that the beta server is down right now.  
>> I'm opening a ticket to our systems team so it will be fixed  
>> tomorrow early in the morning.
>>
>>     Regards,
>>
>> 2010/10/12 Alexa Morris <amorris@amsl.com>
>> Henrik, Emilio,
>>
>> Looks like the Secretariat should get familiar with the new tool  
>> ASAP! :-)
>>
>> I am reviewing, along with Stephanie McCammon (who processes  
>> liaisons for the Secretariat) the new user manual. And I'd like us  
>> to be able to play with the tool a bit as well, but I'm not sure if  
>> we have a username / password to get into it. We may have received  
>> one some time ago, not sure, but if we did I cannot locate it.
>>
>> Can someone please create an account on the tool so that we can  
>> familiarize ourselves with it?
>>
>> Many thanks,
>> Alexa
>>
>> Begin forwarded message:
>>
>> From: Patrik Fältström <paf@cisco.com>
>> Date: October 11, 2010 8:03:07 AM PDT
>> To: Henrik Levkowetz <henrik@levkowetz.com>
>> Cc: yaco-liaison-tool@ietf.org
>> Subject: Re: [yaco-liaison-tool] Acceptance?
>>
>>
>>
>> On 11 okt 2010, at 16.51, Henrik Levkowetz wrote:
>>
>> Is it sorted out who is doing all the work with assigning the roles  
>> at time of launch?
>>
>> No.  What would you suggest as the optimal approach?
>>
>>
>> Have whoever handle the statements@ietf.org do the following:
>>
>> 1. Add the IAB and IETF chairs, wg chairs, area directors etc as  
>> apropriate (as described in the document).
>>
>> 2. Add the liaisons in the IETF assigned and named on the IAB list  
>> of liaisons.
>>
>> [done]
>>
>> Later: Have those liaisons be able to report (or possibly add) the  
>> external liaisons that should be able to file incoming liaisons.
>>
>>  Patrik
>>
>> _______________________________________________
>> yaco-liaison-tool mailing list
>> yaco-liaison-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-liaison-tool
>>
>>
>> -----------
>> Alexa Morris / Executive Director / IETF
>> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
>> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
>> Email: amorris@amsl.com
>>
>> Managed by Association Management Solutions (AMS)
>> Forum Management, Meeting and Event Planning
>> www.amsl.com <http://www.amsl.com/>
>>
>>
>
> -----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>
>
>
> _______________________________________________
> yaco-liaison-tool mailing list
> yaco-liaison-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-liaison-tool
>
>
> _______________________________________________
> yaco-liaison-tool mailing list
> yaco-liaison-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-liaison-tool

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>