Re: [hackathon] IETF103 Hackathon --- the weekend after?

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 23 July 2018 13:09 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDB1130E81; Mon, 23 Jul 2018 06:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 lNNLPpxLow0m; Mon, 23 Jul 2018 06:09:04 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ABD1130E7F; Mon, 23 Jul 2018 06:09:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20854; q=dns/txt; s=iport; t=1532351344; x=1533560944; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GZ4+dQphRHfQ91koZHt9t1+B6uibUVuQu/1tQbmCjjQ=; b=UStxMupEmE1zyzVvwJKzlvNqSh44wzHH8qcZhcrY4izEf0wlhct2qCEx vM5+WrRYyAB4C7bGeHDh52vFgq6+2osC1K+CFkcALDWJSOudt/wZvu2Qt D/1VtwX+OR3CAs8caDpCdnrZxW427ilaz1z7NCHu5I6hpka9vDlYL9+FM I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CdAQCs0lVb/49dJa1bGQEBAQEBAQEBAQEBAQcBAQEBAYJXTCpjfygKg3SUN4IMdY84hwoLGAEKgVSCL0YCF4MGITgUAQIBAQIBAQJtHAyFNgEBAQECAQEBIUUGCwULAgEGAhEDAQIBJwMCAgIlCxQJCAIEAQ0FFAuCNksBgRtcCA+ScptHgS6KSAWJAoIWgREngWxJNYFBgVoBAQEBgX4WgksxgiQCmWwJAoh0hjoOjWSRegIRFIEkNCGBUnAVOyoBgj6CMYhkhT5vAY0rgRsBAQ
X-IronPort-AV: E=Sophos;i="5.51,393,1526342400"; d="scan'208,217";a="146998420"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jul 2018 13:09:03 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id w6ND92IF007920 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 23 Jul 2018 13:09:03 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 23 Jul 2018 08:09:02 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1320.000; Mon, 23 Jul 2018 08:09:02 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Ondřej Surý <ondrej@sury.org>, Eric Rescorla <ekr@rtfm.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, Nick Feamster <feamster@CS.Princeton.EDU>, IETF discussion list <ietf@ietf.org>, hackathon <hackathon@ietf.org>
Thread-Topic: [hackathon] IETF103 Hackathon --- the weekend after?
Thread-Index: AQHUIUKM4oWOdpL9D0qUWNukLIoMuqSangcAgABMroCAAbIcgIAALU+A
Date: Mon, 23 Jul 2018 13:09:02 +0000
Message-ID: <EC3B7705-322A-42CB-A28A-6DC5ACA0F7C4@cisco.com>
References: <32558.1532212248@localhost> <207247CC-FCBC-49F8-9E9D-42329322D41D@cs.princeton.edu> <CABcZeBO2UK1U+SiQTaSSniCpyDa+H05QZTR92UZrWsCjB9o+rw@mail.gmail.com> <639F1A21-C348-4FDB-BCEE-C4EE4460DB0E@sury.org>
In-Reply-To: <639F1A21-C348-4FDB-BCEE-C4EE4460DB0E@sury.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.e.1.180613
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.211.218]
Content-Type: multipart/alternative; boundary="_000_EC3B7705322A42CBA28A6DC5ACA0F7C4ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/e7uwLRL2xVg_DFbqcBkuxjUb1Dg>
Subject: Re: [hackathon] IETF103 Hackathon --- the weekend after?
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2018 13:09:07 -0000

Another consideration is that from a space and network perspective, running the hackathon the weekend before the week of meetings works better than after the week of meetings. Plus, at IETF 103, the schedule is such that meetings end Thursday, so having the hackathon the weekend after would require 3 extra days on the tail end, Friday, Saturday, and Sunday.
At IETF 102, we teamed up with the Netdev community (https://www.netdevconf.org/0x12/index.html), which ran its conference the week before IETF. We plan to do the same for IETF 104 in Prague. Perhaps we should look for a similar opportunity with IEEE in which an IEEE event is the week before IETF. More collaboration with IEEE, especially in the context of a future IETF hackathon, would be great.

Cheers,
Charles

From: ietf <ietf-bounces@ietf.org> on behalf of Ondřej Surý <ondrej@sury.org>
Date: Monday, July 23, 2018 at 12:27 AM
To: Eric Rescorla <ekr@rtfm.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Nick Feamster <feamster@CS.Princeton.EDU>, "ietf@ietf.org" <ietf@ietf.org>, "hackathon@ietf.org" <hackathon@ietf.org>
Subject: Re: [hackathon] IETF103 Hackathon --- the weekend after?

+1 here, I am certainly sure that I won’t attend Hackathon after the IETF. I just want to be back home after the full week. The current timing works best.

Ondřej
--
Ondřej Surý <ondrej@sury.org<mailto:ondrej@sury.org>>

On 22 Jul 2018, at 05:33, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote:
I agree with Nick here. We use the hackathon as a pre-meeting interop, helping us flesh out issues for the WG meetings during the week. Having the hackathon afterwards would not serve the same purpose.

An additional concern here is that people are pretty wiped out after an IETF meeting. This was true even before we started having the hackathon the weekend before and I think it would be difficult for people to be effective at the hackathon afterwards.

-Ekr


On Sat, Jul 21, 2018 at 3:58 PM, Nick Feamster <feamster@cs.princeton.edu<mailto:feamster@cs.princeton.edu>> wrote:
I thought the current scheduling worked very well, as a practical matter.

As a first-time hackathon goer and relative newcomer to IETF, placing the hackathon before the WG meetings was very useful for us, in that it allowed us to meet up with folks and get stuff done—design and otherwise—which we could talk about in the WG meeting itself.

In the sense that the hackathon serves as an informal pre-WG working meeting, I found it very useful. It also nicely sequenced with ANRW on Monday.

-Nick

> On Jul 21, 2018, at 6:30 PM, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>> wrote:
>
> Signed PGP part
>
> I understand that the IEEE meeting will be located in the same
> hotel/conference center as IETF103, the week afterwards.
> There is a desire to foster more collaboration between IEEE and IETF.
>
> I want to suggest that we consider moving the Hackathon from the
> Saturday/Sunday before IETF103, to the Saturday/Sunday afterwards,
> such that it is now sandwiched between IETF and IEEE meetings.
>
> I recognize that perhaps it's too late to rejig this, and there are issues
> relating to the network infrastructure, hotel bookings, and the like.
>
> I suggest the following points:
>  a) We might attract IEEE-types to the Hackathon.
>
>  b) We will give a reason for IETF-types to remain in Bangkok after IETF,
>     in order to mix with IEEE-types.
>
>  c) The Hackathon has now made the week 7 days for sure: arrive Friday
>     morning, stay until Friday afternoon.  Few who come for the Hackathon
>     are going to stay another weekend and attend IEEE, unless they already
>     do stay.
>     Moving the Hackthon means people could arrive Sunday and depart on
>     the following Sunday or Monday.  Same number of hotel nights, but more
>     overlap.
>
>  d) Without something on the weekend between IETF and IEEE, there are likely
>     to be no additional interactions,
>
>  e) the Friday unstructured time experiment might actually work.
>
> One might also contemplate starting the Hackathon on Friday or Friday
> afternoon, possibly finishing earlier on Sunday.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr%2BIETF@sandelman.ca>>, Sandelman Software Works
> -= IPv6 IoT consulting =-
>
>
>
>
>

_______________________________________________
hackathon mailing list
hackathon@ietf.org<mailto:hackathon@ietf.org>
https://www.ietf.org/mailman/listinfo/hackathon

_______________________________________________
hackathon mailing list
hackathon@ietf.org<mailto:hackathon@ietf.org>
https://www.ietf.org/mailman/listinfo/hackathon