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

Henrik Levkowetz <henrik@levkowetz.com> Mon, 23 May 2011 10:16 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-liaison-tool@ietfa.amsl.com
Delivered-To: yaco-liaison-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB47EE06E6 for <yaco-liaison-tool@ietfa.amsl.com>; Mon, 23 May 2011 03:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.202
X-Spam-Level:
X-Spam-Status: No, score=-102.202 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ED5m1dzTgiKr for <yaco-liaison-tool@ietfa.amsl.com>; Mon, 23 May 2011 03:16:41 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfa.amsl.com (Postfix) with ESMTP id 1B305E06DA for <yaco-liaison-tool@ietf.org>; Mon, 23 May 2011 03:16:41 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:62953 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.75) (envelope-from <henrik@levkowetz.com>) id 1QOSBB-0001rr-Vu; Mon, 23 May 2011 12:16:07 +0200
Message-ID: <4DDA33E5.2020804@levkowetz.com>
Date: Mon, 23 May 2011 12:16:05 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
References: <4D483171.7090508@levkowetz.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-71AFC890035! 4@amsl.com> <036801cbfbb1$118c1f50$34a45df0$@olddog.co.uk> <32D56C0A-9FF1-4F9F-A536-2B7D2055BCEF@amsl.com> <8E5CD944-6CD4-410F-A72F-0A820156B6E2@vigilsec.com> <4 DB59F15.5050307@yaco.es> <5FF3BB1A-FE4C-4AE0-8484-AAC07B6E2A64@vigilsec.com> <4DB 80322.4080004@yaco.es> <F13B9074-B218-40F5-A473-F056E6E35BFD@amsl.com> <4DCABBAB.3000002@yaco.es> <4DCABF26.1060009@levkowetz.com> <E1F07D46-99CC-44F9-BBC6-ADAE8CE17B58@amsl.com> <4DDA0283.9070501@yaco.es>
In-Reply-To: <4DDA0283.9070501@yaco.es>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig51E9643660215C059B93199D"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: esanchez@yaco.es, smccammon@amsl.com, housley@vigilsec.com, amorris@amsl.com, adrian@olddog.co.uk, pfaltstr@cisco.com, lear@cisco.com, rpelletier@isoc.org, glen@amsl.com, yaco-liaison-tool@ietf.org, henrik-sent@levkowetz.com
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, 'Eliot Lear' <lear@cisco.com>, =?ISO-8859-1?Q?=27Patrik_F=E4ltstr=F6m=27?= <pfaltstr@cisco.com>, 'Ray Pelletier' <rpelletier@isoc.org>, adrian@olddog.co.uk
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, 23 May 2011 10:16:43 -0000

Hi Stephanie,

On 2011-05-23 08:45 "Emilio A. Sánchez" said:

<<snip>>

>     So you can add people to the list in the following ways:
> 
>     * Adding a new SDO manager in the django admin interface.

And more specifically, you need to go to:
  http://datatracker.ietf.org/admin/liaisons/liaisonmanagers/

There are several steps you need to go through to add a brand new
Liaison Manager.  This will be simplified a lot with the new database
schema, but for now, with the old layout, it's a bit messy:

* If the person you wish to add as a Liaison Manager isn't in the list at
  all, you click on the grey "Add SDO Liaison Manager" field above the
  table to the right, and use the looking-glass to search for the person
  and select the appropriate SDO in the drop-down list.  Click 'Save' and
  you'll be back in the list of Liaison Managers.

  (If he doesn't even exist as a person in the system yet, he needs to be
  added first -- you probably would do that through the rolodex app, although
  it can be done directly in the Django admin interface too).

* If the Person who is now a liaison manager doesn't have a login for the
  system, you'll see 'Add login: <<email-addr>>' with <<email-addr>> in red
  in the fourth column of the table for your new Liaison Manger.  Click on
  the red link and fill in the needed information in the form this leads to.
  Then go back to the list of Liaison Managers and refresh it.

* If the new Liaison Manager doesn't have an entry as a Liaison User, the
  fourth column for him will now show 'Add liaison User <<name>>', with <<name>>
  in red.  Click on the red link and check the information which has been auto-
  filled in the form.  Fix if needed and click 'Save'.  Go back to the list
  of LiaisonManagers and refresh.

Your new liaison manager should now be set up with everything needed, and
you should see him in the drop-down list when you go to edit a liaison.  If
not, there's a bug, as Emilio said ,;-)


Best regards,

	Henrik