Re: Gather.town hour every month?

Toerless Eckert <tte@cs.fau.de> Mon, 15 March 2021 16:41 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 689483A1690 for <ietf@ietfa.amsl.com>; Mon, 15 Mar 2021 09:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 poRxVSS3momz for <ietf@ietfa.amsl.com>; Mon, 15 Mar 2021 09:41:11 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82CCB3A1404 for <ietf@ietf.org>; Mon, 15 Mar 2021 09:41:11 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 074E1548042; Mon, 15 Mar 2021 17:41:04 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id F0149440166; Mon, 15 Mar 2021 17:41:03 +0100 (CET)
Date: Mon, 15 Mar 2021 17:41:03 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Carsten Bormann <cabo@tzi.org>, IETF <ietf@ietf.org>
Subject: Re: Gather.town hour every month?
Message-ID: <20210315164103.GC42031@faui48f.informatik.uni-erlangen.de>
References: <738E6E6B-BD7E-46A2-8E92-BA32EF19836A@tzi.org> <20210315120032.GA42031@faui48f.informatik.uni-erlangen.de> <3F1414A9-C93F-4EBD-B221-4F5EF312C6F8@tzi.org> <20210315122926.GB42031@faui48f.informatik.uni-erlangen.de> <24355.1615820917@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <24355.1615820917@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7ibRaxlYfonJj8DtDlJPORhY8Mo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 15 Mar 2021 16:41:14 -0000

Thanks, Michael, inline

On Mon, Mar 15, 2021 at 11:08:37AM -0400, Michael Richardson wrote:
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > Sure. But gather.town could be made available for several hours
>     > before/after the event to encourage pre/post event gatherings of the
> 
> I think that Carsten is suggestion that the gather.town meeting *is* the
> event.  My understanding is that there is a "free" tier for less than 50
> participants, but I'd prefer that the IETF write some kind of contract,
> because I prefer being the customer, not the product.

How do you think they could/would use us as a product ?
(not that i disagree with the sentiment, just curious).

> I note that virtual interim meetings are often much smaller (usually less
> than 50, often less than 12) so maybe it doesn't need as much CPU.  And we
> ought to be having only one at a time, although if you check the upcoming.ics
> calendar, then you do see that occasionally there are overlaps.

So the plan is still to primarily rely on meetecho ?
As you said, the way meetecho works, it does not seem to
be built around the notion of "no humans involved", and hence
it seems it will always cost some money, making experimentation
more expensive to justify.

>     > community to experiment, discuss around the event. And of course, it
>     > would foster the opportunity of multiple groups to informally coalesce
>     > their events onto such a day. Maybe need to have a simple side meeting
>     > style wiki to reserve room/time slot (room 1 from 1PM - 3PM taken for
>     > the foobar meeting).
> 
> You are starting to attach structure here to what I thought was intended to
> be a rather informal, rather social occurance.  If you want some structure,
> then make it more like our bits'n'bytes, with 4-slide "posters" in certain places.

I was more brainstorming:
-> What can we get within budget ?
-> If it doesn't make a difference whether it's 1 hour or one day, why not try to figure
   out how to use a day ?
-> If it doesn't make a difference (price wise) what the dungeon is,
   then why not use the one from the last IETF.
-> If so... seems like multiple independent meetings can happen in parallel
   (different meeting rooms in the dungeon).

Lots of _if_. You brought in one daa point of <= 50 people == free, which
makes the idea of multiplexing in parallel look less attractive.

>     > I am not quit sure abou the "range" of audio. I ran into what seemed to
>     > be an MPTCP side meeting (at least thats what the payload turned into)
>     > at the bar one day last week, and that seemed to work nicely for > 20
>     > people, so the audio must have passed far enough. But i ran into
>     > problems of audio not passing more than 2 people wide, even though i
>     > think it was not the boundary of a private space...
> 
> I think that it depends upon how that space is setup.
> The interaction distance setting has been removed, and I suspect that it's
> now an "acoustic" property of the room.

Ack.

Cheers
    Toerless