Re: reception not useful for WG chairs

Christian Hopps <chopps@chopps.org> Thu, 16 May 2019 20:13 UTC

Return-Path: <chopps@chopps.org>
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 BE57E1202DC for <wgchairs@ietfa.amsl.com>; Thu, 16 May 2019 13:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Tsd2slWb01g1 for <wgchairs@ietfa.amsl.com>; Thu, 16 May 2019 13:13:53 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 71E491202CD for <wgchairs@ietf.org>; Thu, 16 May 2019 13:13:51 -0700 (PDT)
Received: from tops.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 695F5601E2; Thu, 16 May 2019 16:13:50 -0400 (EDT)
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> <CE03DB3D7B45C245BCA0D243277949363056B432@MX307CL04.corp.emc.com>
User-agent: mu4e 1.1.0; emacs 26.2
From: Christian Hopps <chopps@chopps.org>
To: wgchairs@ietf.org
Cc: Wes Hardaker <wjhns1@hardakers.net>, "STARK, BARBARA H" <bs7652@att.com>
Subject: Re: reception not useful for WG chairs
In-reply-to: <CE03DB3D7B45C245BCA0D243277949363056B432@MX307CL04.corp.emc.com>
Date: Thu, 16 May 2019 16:13:49 -0400
Message-ID: <sa636letawy.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/S-DVuR5xqs8AFqxY1hkoohWU-lI>
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: Thu, 16 May 2019 20:13:56 -0000

Black, David <David.Black@dell.com> writes:

>> What if we had per-topic/area group-tables?
>
> That would be a good move, perhaps for just the first part of the reception..

Right, so that's very similar to my minimal change suggestion:

- Rename "Newcomers" to "Leadership Reception (open)", convert to cash bar, give leadership a couple free drink tickets to incentivize attendance.

Thanks,
Chris.


>
> Thanks, --David
>
>> -----Original Message-----
>> From: WGChairs <wgchairs-bounces@ietf.org> On Behalf Of Wes Hardaker
>> Sent: Thursday, May 16, 2019 1:31 PM
>> To: STARK, BARBARA H
>> Cc: 'Working Group Chairs'
>> Subject: Re: reception not useful for WG chairs
>>
>>
>> [EXTERNAL EMAIL]
>>
>> "STARK, BARBARA H" <bs7652@att.com> writes:
>>
>> > The email that told us the newcomers reception would be discontinued
>> > said this was because the speed-mentoring session was perceived as
>> > being far more valuable/useful and it wasn't necessary to have
>> > both.
>>
>> Yes, and no to the above.  Functionally, it was serving two
>> purposes: 1) the original purpose: allowing newcomers to meet up with
>> chairs and ADs, 2) its transformed purpose: allowing chairs and ADs to
>> meet up with chairs and ADs.
>>
>> It's intended original purpose was #1, and it seems the consensus is
>> that #2 is what everyone is saying they're missing with lots of points
>> about what the general reception can't be used.  However, the problem
>> that #1 wasn't meeting it's purpose is mostly unrelated to the
>> quick-connections session.  The purpose was still not being met,
>> regardless.
>>
>> 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?
>>
>> --
>> Wes Hardaker
>> USC/ISI