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

"Thomas D. Nadeau" <tnadeau@lucidvision.com> Wed, 25 February 2015 19:46 UTC

Return-Path: <tnadeau@lucidvision.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 2EA251A870C for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 11:46:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.895
X-Spam-Level:
X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 glywsWzccCYh for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 11:46:36 -0800 (PST)
Received: from lucidvision.com (unknown [50.255.148.178]) by ietfa.amsl.com (Postfix) with ESMTP id 058161A802E for <ietf@ietf.org>; Wed, 25 Feb 2015 11:46:35 -0800 (PST)
Received: from [192.168.1.134] (unknown [50.255.148.177]) by lucidvision.com (Postfix) with ESMTP id 6FBF42F47A70; Wed, 25 Feb 2015 14:46:35 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.com>
Date: Wed, 25 Feb 2015 14:46:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <54103A5A-0A32-4AAC-ACBE-7B507D799CD3@lucidvision.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>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YnQ2Tia0cux9efO-DL1qynir9S8>
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 19:46:38 -0000

	Sure, but that isn't a good excuse IMHO. I don't think anyone should approach me personally, but 
there are WG chair/WG/all-WG-chair mailing lists that are commonly used to communicate with the IETF leadership
and participants.

	But that is diverging from my original point. Why is there so much corporate advertising and branding on this?
Why can't we just use an IETF web/wiki for this?  Its a bit offensive to be courted with signup for Cisco's dev net program
after clicking on an apparently IETF-sponsored link. The point I was making earlier is that its inappropriate based 
on the IETF's past approach to these things. No one has given a good reason why either.

	--Tom



> On Feb 25, 2015:12:04 PM, at 12:04 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
> 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.
> 
>