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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 25 February 2015 18:42 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 D69CC1A1AAA for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 10:42:16 -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 1jVBfdOML7bd for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 10:42:15 -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 8A0BB1A0387 for <ietf@ietf.org>; Wed, 25 Feb 2015 10:42:15 -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 5538ADA01EA for <ietf@ietf.org>; Wed, 25 Feb 2015 18:42:15 +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 29EAA53E09D; Wed, 25 Feb 2015 10:42:15 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 25 Feb 2015 10:42:15 -0800
Content-Type: text/plain; charset="iso-8859-1"
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: <54EE0865.4090101@gmail.com>
Date: Wed, 25 Feb 2015 13:42:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B37212B3-708A-4F14-8B4B-EE309E6213D5@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> <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.com> <54EE0865.4090101@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-yGaq1skvoJ2Sd9RMS_co6jP_xs>
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 18:42:17 -0000

On Feb 25, 2015, at 12:37 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> That's nonsense, Ted.  Nobody's saying "You didn't approach *me*".

Actually, that is _exactly_ what was said.

> What we're saying is that there are questions about where the list
> of technologies came from

Come on, please lose the passive voice and own it.   _You_ have questions about where the list of technologies came from.   I can tell you where: the organizer(s) (I don't know if it's singular or plural, I wasn't involved) had a deadline, and they came up with some ideas, and they threw the spaghetti against the wall to see if it would stick.  Nobody has copious free time at IETF.   Everything is best-effort.   Getting things right is _always_ an iterative process.

> Might have made more sense to wait until
> summer, give the thing a better chance of success because of
> better planning.

Best is the enemy of good enough.   I would rather see people try to do things and not do them perfectly than that they not try.   Speaking as someone who's tried a number of initiatives at the IETF, it is actually hard to organize them and get people to come, and after a while you stop trying because it's a skinner box where you always get a shock when you push the button.

We are smart people at the IETF, and _any_ proposal will have some obvious omission that we will spot.   If the way we express our discovery of this potential optimization is to use accusatory language that suggests that something improper has been done, as is _amazingly frequently the case_, then there's another IETF cynic we've created out of a formerly willing volunteer.

As a hint here, the right thing to say if you think the agenda is to Cisco-intensive is "I'd like to see more 'foo' in the next Hackathon," or even better, "how can I help," not "this looks fishy."