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

Eric Rescorla <ekr@rtfm.com> Sun, 22 July 2018 03:33 UTC

Return-Path: <ekr@rtfm.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 11A47130E3D for <hackathon@ietfa.amsl.com>; Sat, 21 Jul 2018 20:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 i0YYHlGT4B-M for <hackathon@ietfa.amsl.com>; Sat, 21 Jul 2018 20:33:51 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BEB2130E14 for <hackathon@ietf.org>; Sat, 21 Jul 2018 20:33:50 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id q5-v6so14123335ljh.12 for <hackathon@ietf.org>; Sat, 21 Jul 2018 20:33:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HnHgbXyEKOyge7enN+C3r9unAFf81fbabm5D1HekE3k=; b=Ey6wg8axUeec0dm4d9u2oiDWE8AaTIZUVJaxtNCwqdTRFIrE8JsxA2Sg5f/YE1WAto kOvlWLnInUYMiQEsckVX0GpmuaNS6NSRNZOfZvxGUoMXpyqLfFfTuBTHY34D7WDDw8+l bwiCRcHKntiF3WEbhwWfyg6XUWczIMqB27mZl1+Rh3oC4q8D2kHOzwYF+YK7xr4tGQbt zk1ApBFVcnXOCHkUlzAsW/j9Cv/HxFwwrG/y1wcSZVHJmYpD3vUSdfBmIm5QK/Cvp5fs G+8tUWviiXHwKWJVXYGFdeyt0SSM7rWl9pRCXKRr6jgR5VMdx7KXVRRx+yqys4idHB4X 5Q1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HnHgbXyEKOyge7enN+C3r9unAFf81fbabm5D1HekE3k=; b=klu5oTY2YpR308HuzeHcjvlAfRyGQbjsxH6s0AYELXZG8wIaMDBsg4TV5Pl1EyzZ3+ ZNk9sh8kijsr9BD2enr0T05BrWFTH065jieQFooZbfJn1OplINqr8M3u6Cw2bQQYf47d aWK4xJ99+SwnhYjk0yPI0ECStyRoKqHu2ldE1AuYrZqVuc6mtHZ1Hx1b5CklBYpFdpHB nKKp4bhmNuUZhf/JqNSVEVXdImpzIy/U/IfFn0WHmgoOthNnY7R3HBN2pUWk2BPmnxQq cuZn0Wcywv3af7g/dlsiDkKvZG+BKBgezRhWc3gxZiLRZ2FcriNXt3v0mjVPKWTTdgD7 UP0g==
X-Gm-Message-State: AOUpUlFZ8XzZ84DYsC6qA+7H2tNhCSzTJh+fJHLhZqPuIdEJyKLXbe5h Bfa6XY/s6WZLzTWTFNbTz+ICihtHTqjY/b+jX+Jvnw==
X-Google-Smtp-Source: AAOMgpcIs8TA+3lt4AirhXQBpu7ASCMFTEg44htC9gcdbpd97uff1Lb7k+nyjqW2hNtlFIvTGUcsH4W6afClxelmWqs=
X-Received: by 2002:a2e:1b83:: with SMTP id c3-v6mr5189983ljf.0.1532230428655; Sat, 21 Jul 2018 20:33:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:4091:0:0:0:0:0 with HTTP; Sat, 21 Jul 2018 20:33:07 -0700 (PDT)
In-Reply-To: <207247CC-FCBC-49F8-9E9D-42329322D41D@cs.princeton.edu>
References: <32558.1532212248@localhost> <207247CC-FCBC-49F8-9E9D-42329322D41D@cs.princeton.edu>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 21 Jul 2018 20:33:07 -0700
Message-ID: <CABcZeBO2UK1U+SiQTaSSniCpyDa+H05QZTR92UZrWsCjB9o+rw@mail.gmail.com>
To: Nick Feamster <feamster@cs.princeton.edu>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <ietf@ietf.org>, hackathon <hackathon@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a161905718e325e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/gabwkfGy2hNM8s2PKDH1IUSJUsQ>
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: Sun, 22 Jul 2018 03:33:55 -0000

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>
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>
> 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>, Sandelman Software Works
> > -= IPv6 IoT consulting =-
> >
> >
> >
> >
> >
>
>
> _______________________________________________
> hackathon mailing list
> hackathon@ietf.org
> https://www.ietf.org/mailman/listinfo/hackathon
>
>