Re: Remote participation ( was Leading a moving target)
Toerless Eckert <tte@cs.fau.de> Fri, 26 July 2019 19:19 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 DFF7A12040D; Fri, 26 Jul 2019 12:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 mt-SF3Z_6THu; Fri, 26 Jul 2019 12:19:06 -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 38D6C1203ED; Fri, 26 Jul 2019 12:19:06 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1B78654800E; Fri, 26 Jul 2019 21:19:01 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0A8BB440041; Fri, 26 Jul 2019 21:19:01 +0200 (CEST)
Date: Fri, 26 Jul 2019 21:19:00 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: IETF list <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>, ietf@meetecho.com
Subject: Re: Remote participation ( was Leading a moving target)
Message-ID: <20190726191900.by37qestti66rrlf@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l_2evidZyrKHFFKBRyu2IVaGTkU>
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: Fri, 26 Jul 2019 19:19:09 -0000
Thanks, Andy. Great to hear it did work out that well for you.
I always found the meetecho setup to be very good especially also the
support from the meetecho team. If there is anything to complain about
is that i think the quality of the video from remote participants was
lower than even what i think to remember from the past. I wonder if its
really set to rate adapt to the available bandwidth or artifially limited
to some low maximum. It really distracted from the experience, which
otherwise (especially also including the jabber channel) would have been
very close to the person being there in person.
Cheer
Toerless
In-Reply-To: <CAA=duU2X1SjyPN0azuSpCykp4Wh8TNruO-knzYR=BLTJvLxU7A@mail.gmail.com>
On Fri, Jul 26, 2019 at 12:35:40PM -0400, Andrew G. Malis wrote:
> With Adrian's post about our remote participation technology and the
> growing trend to remote participation, I would like to just post a
> reaction, while it's fresh in my mind, to being a remote participant for
> the first time.
>
> I would like to start by saying that I was very pleased how how well
> Meetecho works. I watched the short online tutorial video (which is a bit
> out of date, and perhaps should be updated) and read the support page
> walkthrough of the various buttons, icons, etc., and didn't experience any
> problems during the week. While I was prepared to virtually raise my hand
> (I had a headset on just in case), I found that the integrated jabber
> window made it unnecessary - I was able to make my comments via jabber and
> the jabber scribe or WG chair read them to the room. I was also able to use
> the jabber window to communicate with @Meetcho if there were any mike or
> camera issues, and they were EXTREMELY responsive!
>
> I also found Etherpad very useful when it's used. Not all WGs use it, but I
> would encourage all of those that don't use it to switch to it for the live
> meetings. There was a bit of trouble this meeting with duplicate Etherpads,
> but that's a tooling issue that I'm sure will be addressed for the next
> meeting. An excellent way to use Ethernet is prior to the meeting for the
> WG chair or secretary to paste in the meeting agenda, and then the notes
> for each item on the agenda can just be typed in following each agenda
> topic. It's also a good practice that if anyone is going to add to the
> Etherpad, they type in their name at the top of the page, so that their
> text color can be attributed to them.
>
> Being a remote participant, I did miss the hallway conversations and such.
> But I didn't miss the airports, too-cold AC in the rooms, and other minor
> annoyances of travel. It's certainly a trade-off.
>
> What could be improved? This probably isn't immediately feasible, but two
> cameras in each room (one pointed to the front, the other to the mike line)
> would be huge. That way you can watch both ends of the conversation at
> once. Also, in the Meetecho UI, it might be better to increase the size of
> the camera image and have the camera image and the slides vertically placed
> one on top of each other, rather than the smaller camera image over to the
> side. Or perhaps that could be an option. I know that you can make the
> camera image larger, but then you lose the slides.
>
> But on the whole, being remote worked much better than I had expected, and
> for that I would like to thank everyone that's been working on making this
> possible, starting with the Meetecho team.
>
> That said, my preference is still to attend in person if possible. :-)
>
> Cheers,
> Andy
--
---
tte@cs.fau.de
- Leading a moving target Spencer Dawkins at IETF
- RE: Leading a moving target Adrian Farrel
- Re: Leading a moving target Kathleen Moriarty
- Remote participation ( was Leading a moving targe… Andrew G. Malis
- Re: Remote participation ( was Leading a moving t… Toerless Eckert
- Re: Remote participation ( was Leading a moving t… Michael Richardson
- Re: Remote participation ( was Leading a moving t… Bron Gondwana
- Re: Remote participation ( was Leading a moving t… Andrew G. Malis
- Re: Leading a moving target John C Klensin
- Re: Leading a moving target Keith Moore
- Re: Leading a moving target Mark Andrews
- Re: Remote participation ( was Leading a moving t… Meetecho IETF support