Re: reception not useful for WG chairs

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 18 May 2019 21:44 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48029120046 for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 14:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Gge1HH3atPOj for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 14:44:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08DAC120021 for <wgchairs@ietf.org>; Sat, 18 May 2019 14:44:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 810C03826B for <wgchairs@ietf.org>; Sat, 18 May 2019 17:44:05 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 9DEC3CA3; Sat, 18 May 2019 17:44:54 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9B5EAC91 for <wgchairs@ietf.org>; Sat, 18 May 2019 17:44:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 'Working Group Chairs' <wgchairs@ietf.org>
Subject: Re: reception not useful for WG chairs
In-Reply-To: <ybly336par7.fsf@w7.hardakers.net>
References: <CE03DB3D7B45C245BCA0D2432779493630556890@MX307CL04.corp.emc.com> <1756.1557154162@localhost> <20190506145757.GC19509@kduck.mit.edu> <23268.1557158691@localhost> <DE8DA2AF-9666-42D1-BFC0-2E207B1D6862@gmail.com> <30ecf2f6-9c9b-1eca-3ba6-8319829c2ffc@cisco.com> <26329.1557173327@localhost> <sa6mujuj873.fsf@chopps.org> <22493.1557605363@localhost> <da3c395d-3fef-dfb3-4e46-939eee5eeb7c@cisco.com> <20190514011432.bdvcznxca2nvd4ar@faui48f.informatik.uni-erlangen.de> <b3e5dafc-50ff-09ef-066a-52c9ba11e563@pi.nu> <6A39D1BB-7F81-4B77-B7A8-8D9EAC142C02@gmail.com> <BE4D4204-6071-459C-AC09-97ED35D17D9E@viagenie.ca> <4AC557B0-67B9-442B-824D-F522703AEB72@akamai.com> <CD86E244-47DA-4525-BB44-0F1C293CE0D0@cisco.com> <2D09D61DDFA73D4C884805CC7865E6114E1893EC@GAALPA1MSGUSRBF.ITServices.sbc.com> <ybly336par7.fsf@w7.hardakers.net>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sat, 18 May 2019 17:44:54 -0400
Message-ID: <10981.1558215894@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/28HOHm-Wlz_Bs_BM_QZepMhv8Vc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 May 2019 21:44:59 -0000

Wes Hardaker <wjhns1@hardakers.net> wrote:
    > Here's a turn around question for the crowd: what would it take to make
    > the general reception a viable spot to meet and serve the purpose of a
    > pre-meeting meet-and-greet with people you need to talk with?  What
    > could be done other than "throw out everyone I don't need to talk to",
    > which I don't think is a viable solution.  If it's too loud, what could
    > we do?  If it's too popular, what if we removed food/drink for the first
    > hour (so only the dedicated showed up)?  What if we held it in a bigger
    > room?  What if we had per-topic/area group-tables?  What *would* work?

This is why I changed the subject :-)

1) I think that removing food/drink is not the right direction.
   Spreading it out so that it's not all gone during the first hour would
   help me better.  There are usually lines.  I don't like standing in lines
   when I could be talking/drinking.
   Given that we have lines, let's harness them rather than banish them.

   Have the line go through some standing tables the way that good stores
   make use of banking lines to sell you chips and USB charge cables you
   didn't know you needed.
   Put ADs at those tables.  Supply ADs with food via waiter.

2) I objected to HotRFC overlapping the second hour of the reception.
   Others objected to my objection, maybe because for them, the reception was
   already useless, and they saw no point in dragging out the pain.
   But, I think that also goes in the wrong direction, and that removes many
   people that you'd like to talk to from the reception.

3) Don't close the room at 7pm.  That usually doesn't happen, we don't get
   kicked out,  but the bar usually does pack up.

4) Consider if we should start slightly later than 5pm...

5) noise.  can we do this in a few, connected smaller rooms rather than one
   huge room?  Can we hang carpets?  That's what they did for noise (and
   heat) in medival castles..
   So it's very much hotel/conference facility dependant,alas.
   (this is why it is nice to keep going back to the same hotels...)
   I was just thinking about London Metropole... spread the reception out all
   over the place... but no, that's *too* much decentralization.
   But a nice thing when we where there, was the newcomers' space basically
   opened upon into the bigger reception room.
   The alcoves in Seoul were very nice for conversation, but we didn't really
   harness that for the reception.

   If we did do this in a multitude of smaller rooms, then we could close up
   some rooms, but not all rooms.


Back to (2), if HotRFC needs to be on Sunday, let's make it 4pm to 6pm, have
it near the reception, which starts at 6pm.  Maybe we want to project it from
a smaller room into a bigger reception room.  That should be easy given
meetecho.

Poster sessions: an alternative (for some people) to HotRFC may be to have a
small poster session with an idea.   Maybe that's too formal. I'm not sure.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-