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

Nico Williams <nico@cryptonector.com> Wed, 25 February 2015 21:11 UTC

Return-Path: <nico@cryptonector.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 634C51A889F for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 13:11:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level:
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] 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 JG-Dqo3k_evZ for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 13:11:01 -0800 (PST)
Received: from homiemail-a63.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6A31A8783 for <ietf@ietf.org>; Wed, 25 Feb 2015 13:11:01 -0800 (PST)
Received: from homiemail-a63.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTP id AACC62F4065; Wed, 25 Feb 2015 13:11:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=V5f3Ofp0kB0fIN aAUV0h8sPe+zA=; b=dlXpnmYnUd8o4CsZCYyg6sGc7jbqhlktYVaDNS0gQIHwgT 5Taf0XU8m0Be6Vd6Ih9tw0wbDa5DzbE2CxQT26z++Ea+PcKWumiYw/ejFhSz5D0j iAMIJWRkxCc6uf7fFw5CxYfZw2H+63o/wTej2ZB9jtPaCxRE4CbxvOgduYj/A=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTPA id 30E252F4060; Wed, 25 Feb 2015 13:11:00 -0800 (PST)
Date: Wed, 25 Feb 2015 15:10:59 -0600
From: Nico Williams <nico@cryptonector.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Message-ID: <20150225211057.GB8747@localhost>
References: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54EE2DD7.1030408@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aVeTmaBgkjU6rX6yGF_Wvr9qTtE>
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:11:02 -0000

On Wed, Feb 25, 2015 at 11:17:27AM -0900, Melinda Shore wrote:
> The "community" page requires a Cisco login.  Regardless, wouldn't it
> makes sense to answer the questions where they're being asked?

Then it's not a community page, as you imply.

I've nothing against a vendor sponsoring an IETF hackathon.  I've
nothing against advertising for the sponsor on the hackathon page.  I've
not even got anything against the hackathon focusing on technologies of
interest to the sponsoring vendor: those of us who have other
technologies we'd rather work on can organize our own.  There may be a
question keeping general meeting revenue from funding such a constrained
*and* sponsored hackathon.

I've also got nothing against a vendor [whose employees participate at
the IETF] piggybacking on an IETF meeting by co-locating their events in
the same city, same general area of the same city, and even the same
conference venue, provided that they a) don't use IETF meeting revenue
to fund their events, and b) don't compete for time slots with the IETF.
We can't do anything about (b), of course, but we can do something about
(a).

I'm not happy with vendor logins on an IETF page of any kind.

Also, the IETF NOTE WELL should apply to any IETF hackathon, and any
deviation from that would definitely require discussion *ahead* of the
announcement of the hackathon.

BTW, this thread has already cost quite a lot of labor.  Setting rules
of the road for sponsoring IETF events related/overlapping/co-located
to/with an IETF meeting is key to not doing this again.

Nico
--