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

Dean Bogdanovic <deanb@juniper.net> Tue, 24 February 2015 20:55 UTC

Return-Path: <deanb@juniper.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 B15731A88E5 for <ietf@ietfa.amsl.com>; Tue, 24 Feb 2015 12:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 kqrmgX9z_cde for <ietf@ietfa.amsl.com>; Tue, 24 Feb 2015 12:55:14 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0122.outbound.protection.outlook.com [207.46.100.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60B391A6EFC for <ietf@ietf.org>; Tue, 24 Feb 2015 12:55:14 -0800 (PST)
Received: from BN1PR05MB424.namprd05.prod.outlook.com (10.141.58.148) by BN1PR05MB423.namprd05.prod.outlook.com (10.141.58.146) with Microsoft SMTP Server (TLS) id 15.1.87.18; Tue, 24 Feb 2015 20:55:12 +0000
Received: from BN1PR05MB424.namprd05.prod.outlook.com ([169.254.8.9]) by BN1PR05MB424.namprd05.prod.outlook.com ([169.254.8.9]) with mapi id 15.01.0087.013; Tue, 24 Feb 2015 20:55:12 +0000
From: Dean Bogdanovic <deanb@juniper.net>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [92all] IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Topic: [92all] IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Index: AQHQUFOc82PFzjIpgEOOfBqJDSi1IJ0AFiOAgAAA6QCAAAWrgIAADXgAgAAEWYCAABApAIAACQOA
Date: Tue, 24 Feb 2015 20:55:12 +0000
Message-ID: <8DB221D1-5AEC-4BB9-A44B-E326B9AE8FF4@juniper.net>
References: <20150224170152.6224.60832.idtracker@ietfa.amsl.com> <DBC7E705-B163-46E8-AC9B-97BDC33E7C68@apple.com> <54ECBC5E.2030001@dcrocker.net> <CAHw9_iKpmEOFyZ5Mi=6KcsEoLHDVCwFTi5q_0GfK-d5B1X_Hdg@mail.gmail.com> <7E5194B1-4717-4225-85C6-E969EF7800A7@apple.com> <D1120FE3.3E483%eckelcu@cisco.com> <54ECDDA0.6010904@dcrocker.net>
In-Reply-To: <54ECDDA0.6010904@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.1510)
x-originating-ip: [66.129.241.10]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=deanb@juniper.net;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB423;
x-microsoft-antispam-prvs: <BN1PR05MB4231CDD536630ABA5F009BCAC160@BN1PR05MB423.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB423;
x-forefront-prvs: 04976078F0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51704005)(22813001)(16313002)(199003)(24454002)(479174004)(189002)(82746002)(2656002)(50226001)(102836002)(66066001)(57306001)(33656002)(101416001)(2950100001)(86362001)(99286002)(2351001)(83716003)(87936001)(19580405001)(68736005)(2900100001)(92566002)(64706001)(19580395003)(97736003)(76176999)(50986999)(77156002)(62966003)(46102003)(122556002)(93886004)(106116001)(36756003)(110136001)(40100003)(105586002)(2501003)(106356001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB423; H:BN1PR05MB424.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E533ECBEF5D18A4EB7529EFE82FB30E0@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2015 20:55:12.3086 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB423
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vCcbhmEkp8BSW6-6KXLgd6rIwGI>
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: Tue, 24 Feb 2015 20:55:15 -0000

Dave,

I agree with Tom's statement that there is too much corporate marketing around this hackathon.

On Feb 24, 2015, at 3:22 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 2/24/2015 11:25 AM, Charles Eckel (eckelcu) wrote:
>> I¹ll take the blame for the unfortunately short notice. We started
>> planning only a couple weeks ago, and thought that having something at
>> IETF 92 is better than nothing.
> 
> 
> It's important that we be careful not to consider this in terms of
> blaming anyone about this (or any, IMO) specific event.  Each of the
> activities -- certainly including this one -- is fully worthy.
> 

> However there is a long-standing pattern of late announcements of
> special activities surrounding IETF Week.
> 
> I see this as a presumption about who can and will attend, namely the
> hard-core devotees who have the funding and long-term commitment to attend.

I fully disagree with this statement and it is very disrespectful. I know many people personally who have been coming to IETF for more then 25 years and they are interested in such a hackathon, but can't change their plans.
> 
> The problem is with who this de facto excludes.

IMO, too many people

Dean

> 
> I think the important issue to for all of us to get our heads in a place
> that worries about more advanced notice.  Once we think of 2- or 3-month
> (or whatever we feel appropriate) deadlines, we will all come up with
> ideas for activities as we usually do -- last-minute -- but relative to
> the earlier deadline, rather than the actual event.
> 
> d/
> -- 
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>