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

Warren Kumari <warren@kumari.net> Wed, 25 February 2015 21:49 UTC

Return-Path: <warren@kumari.net>
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 93BBF1A88F3 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 13:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 lMwtwdDwWbMy for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 13:49:30 -0800 (PST)
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180]) (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 70E571A87C9 for <ietf@ietf.org>; Wed, 25 Feb 2015 13:49:30 -0800 (PST)
Received: by wesx3 with SMTP id x3so6375125wes.6 for <ietf@ietf.org>; Wed, 25 Feb 2015 13:49:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5vTm7e/pglr0DBFvYP63JR2Eh+xgGr4Gbgre2ywgD1Q=; b=d55jhhu7nG/WH6zVajjGMipu1xByILaoN5cOw3b6W6L8XGhTRTWhL6OKXUCDX2rD+t m7dKL4/YMxG9nu2VtGj+855QvwLlKZa+5Hxi+YguOIbICDbrOrO90EuA++dmco18BeBi lRaldHIGS11SgukC8WnmrgSVqLZoV0+v76bkRvWqyrqBH/WsT6qI7t2dACIobfkQ4sU1 2D/cLMVEPK5hB4Q1lJDfrNMlmOqpSsIgPQIV8FGSCHCzJOXyUL3jIG+DPKdHZH0nzQjr 9qMW58Rc96/2Bk0hXOOWgkpruLa96UUzVVJJu9zvX8aqQoOyZ6WApnDnebMVNV0xnTdM cUQg==
X-Gm-Message-State: ALoCoQlw7OWhlVV3MhglmtnRNiOKi5jm/K8klxSzjQQCLDS+KHW8ELWyxYKQmfVu7NhHW6bHB02x
MIME-Version: 1.0
X-Received: by 10.194.84.176 with SMTP id a16mr9942245wjz.113.1424900969231; Wed, 25 Feb 2015 13:49:29 -0800 (PST)
Received: by 10.194.158.229 with HTTP; Wed, 25 Feb 2015 13:49:29 -0800 (PST)
In-Reply-To: <D1137564.3E89E%eckelcu@cisco.com>
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> <54EE3016.3040106@gmail.com> <D1137564.3E89E%eckelcu@cisco.com>
Date: Wed, 25 Feb 2015 16:49:29 -0500
Message-ID: <CAHw9_iKTpRkYM7MaKRDcA38hgSYsH5Nz=XwVscvPpYhRZg4MWA@mail.gmail.com>
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
From: Warren Kumari <warren@kumari.net>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iQczuQzUTGHFU63StOBEe4b8hzU>
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 21:49:32 -0000

On Wed, Feb 25, 2015 at 3:54 PM, Charles Eckel (eckelcu)
<eckelcu@cisco.com> wrote:
> We are using the Cisco community page to host the ongoing discussion
> forum. Here is the info found there as to how IETF and Cisco are both
> involved in the Hackathon (sorry for poor formatting resulting from
> copy/paste).
>
> IETF is providing the room and the network for the event.
> Cisco DevNet is running the Hackathon, paying for food, prizes, etc.
> * Hackathon information is hosted on the DevNet site: Cisco DevNet: IETF
> Hackathon at IETF 92, March 21-22
> <https://developer.cisco.com/site/ietf-hackathon/>
> * Ongoing discussion is encourage, and is hosted within the Cisco
> developer community page: IETF Hackathon
> <https://communities.cisco.com/community/developer/ietf-hackathon>
>
> All interested parties click to a reg form on the IETF site: IETF
> Hackathon 2015 Dallas
> <https://www.ietf.org/meeting/92/hackathon-signup.html>
> * Registration is handled entirely by the IETF, in accordance with IETF
> privacy requirements.
> *  Registered attendees will not need to have become DevNet members.
> * Registered attendees will be shown and reminded that their participation
> is subject to the IETF Note Well: Note Well
> <https://www.ietf.org/about/note-well.html>
>
> A link to the same info is:
> https://communities.cisco.com/message/175271#175271 (and yes, there is the
> hassle of getting a CCO account if you do not have one).

Thank you, this answers many of my questions. You forgot to
cut-n-paste one of the (IMO) more useful answers from that page:

"What was the Hackathon not announced earlier?"
"Planning the Hackathon started with very little runway before IETF
92, Dallas. At the time, it was not clear if it would be possible to
do anything in Dallas, or if we would need to wait for IETF 93,
Prague. We were able to pull together a room, network, and champions
for a few technologies very quickly.

Presented with the choice of trying something last minute in Dallas
vs. waiting until Prague, we decided to go for Dallas. The rationale
was that due to the late notice, the Dallas Hackathon would be
relatively small and provide lots of good insights into how to do
things bigger, better, and MUCH earlier for IETF 93."

Cool.

W


>
> Cheers,
>
> Charles
>
> On 2/25/15, 12:27 PM, "Melinda Shore" <melinda.shore@gmail.com> wrote:
>
>>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
>>
>>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf