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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 25 February 2015 17:04 UTC

Return-Path: <Ted.Lemon@nominum.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 C822C1A1A48 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 09:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 g4eHSm071vz8 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 09:04:16 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4D2A1A1A2F for <ietf@ietf.org>; Wed, 25 Feb 2015 09:04:16 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 42BCBDA01F3 for <ietf@ietf.org>; Wed, 25 Feb 2015 17:04:16 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0636853E0B1; Wed, 25 Feb 2015 09:04:16 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 25 Feb 2015 09:04:15 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 25 Feb 2015 09:04:15 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D275D180-272B-43C7-BDF0-FE2B438DEB60@lucidvision.com>
Date: Wed, 25 Feb 2015 12:04:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.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>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rSgJaLAQcIM5xLgeX5xOk95heBI>
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 17:04:17 -0000

On Feb 25, 2015, at 11:58 AM, Thomas Nadeau <tnadeau@lucidvision.com> wrote:
> No one approached us for this either.

Nobody has visibility into all the activities of the IETF.   The way volunteer organizations work is that people scratch their own itch, and hopefully it's of collective benefit.   If this hackathon is a good idea (as a lot of people seem to believe) then it would be great if, now that it's been floated and is going to be tried, the next hackathon had more broad involvement of the community.

But the expectation that someone will approach you is kind of absurd.   If you want to be involved, approach the people who are already involved.   Don't wait for them to approach you.   Of course, you didn't know about this in advance--the first I heard of it was less than a week ago.   But now you know, and there are plans to do this at IETF 93; if you think a general hackathon framework at the IETF would be a good place for the yang hackathon work you are doing, then you should be involved in planning the IETF 93 hackathon.