Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX

Melinda Shore <melinda.shore@gmail.com> Wed, 25 February 2015 20:27 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E54971A1F73 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 12:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBX2zSTcPGwB for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 12:27:05 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 970461A1BDE for <ietf@ietf.org>; Wed, 25 Feb 2015 12:27:05 -0800 (PST)
Received: by pdbfl12 with SMTP id fl12so7408678pdb.2 for <ietf@ietf.org>; Wed, 25 Feb 2015 12:27:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NFR23pE94J/bd1Ny6C2QrkcFQB3TB3GubVfBKKu7JeA=; b=jVuTpa5dnhB9T5kPkvbSfLyyFApcxsItD5+Irp5I4UYGXeqgBu697yRAHQB14Nt2Do hGwpTuEEb15DEEQkiyPJ8XMl5hewtf2Mz8rlDXhmddZTVlUByf1dRAzqpz+E4iV6DJuU 3oig1+EI0MyyHZhVMUDsn1B/1djabpKVKRajTb5Bw9qcHQoYumcsJZqa4I8sOZE/MjI1 G6rL9jlYve7XnU2AP3dc8PNwUA/Dwb2GAnC2ug4tPKc7qPsBlnGSmY8aqEqVGBFyoQdp HizACmMqAkmhM3CSuDaHCOGql78XwFEz22JB0OUIAA9Bm5KB2dbOfCwc8T8nQs0Bt2Nw B8ag==
X-Received: by 10.66.66.135 with SMTP id f7mr8454103pat.93.1424896024992; Wed, 25 Feb 2015 12:27:04 -0800 (PST)
Received: from spandex.local (63-140-88-158.dynamic.dsl.acsalaska.net. [63.140.88.158]) by mx.google.com with ESMTPSA id nk16sm18659553pdb.78.2015.02.25.12.27.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Feb 2015 12:27:04 -0800 (PST)
Message-ID: <54EE3016.3040106@gmail.com>
Date: Wed, 25 Feb 2015 11:27:02 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
References: <20150224170152.6224.60832.idtracker@ietfa.amsl.com> <09B0A2B7-7D6B-4365-B58C-AAD97C3BE73D@lucidvision.com> <B32A64D5-0B07-4E01-92B1-DEAF21002EE7@netapp.com> <D1132FAF.3E752%eckelcu@cisco.com> <54EDF486.20000@gmail.com> <D275D180-272B-43C7-BDF0-FE2B438DEB60@lucidvision.com> <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.com> <54EE0865.4090101@gmail.com> <CAHw9_iKA7bgZH6iJLw1y7=qz6MJDePgUbCeOtHXnaajCKshRnw@mail.gmail.com> <D1136BA7.3E85D%eckelcu@cisco.com> <54EE2DD7.1030408@gmail.com> <D1136F2B.3E87C%eckelcu@cisco.com>
In-Reply-To: <D1136F2B.3E87C%eckelcu@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_EKIimTt1aoZAmwJQsY3V4saKv4>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 20:27:07 -0000

On 2/25/15 11:25 AM, Charles Eckel (eckelcu) wrote:
> Perhaps, but I¹m trying to scale better, and keeping things in once place
> helps. Similar questions have come from other IETF aliases as well as from
> people outside of the IETF entirely.

Why does the "community" page require a Cisco login?  I really
don't understand what you're doing, here.

Melinda