Re: Meetecho was Re: Concerns about Singapore

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 12 April 2016 12:19 UTC

Return-Path: <swmike@swm.pp.se>
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 3047712EC2E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level:
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 2UkM3EWr2oJu for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:19:48 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A99212E182 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:19:45 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 48DD0A2; Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460463583; bh=BG5qUpRFnBsM005sJcMNarS2ny3XHRlLEj1Ufz5/pQI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=1AsQFGKPbE/JYFQFqoIE7egZCeWT+E7VcG6DWHmslbp3u/+XmoO5VQ7gNyppOHtn/ FkQ70RNMR3BvTPZVV+nqUhSwo6/bZi0w1PrdhK45uKCEkvhFwOvsJATRaklgUOoV3D TF2ET6sdvHggXpC3OrIP4mjA33rR7gLM00mYYQxY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 22A71A1; Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
Date: Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jared Mauch <jared@puck.nether.net>
Subject: Re: Meetecho was Re: Concerns about Singapore
In-Reply-To: <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net>
Message-ID: <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se>
References: <20160411223403.GA6743@gsp.org> <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com> <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YKb3Q9EDKb0WeOcORLmB0u21AAM>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Apr 2016 12:19:51 -0000

On Mon, 11 Apr 2016, Jared Mauch wrote:

>
>> On Apr 11, 2016, at 8:08 PM, <lloyd.wood@yahoo.co.uk> <lloyd.wood@yahoo.co.uk> wrote:
>>
>> try listening to the first twenty minutes of this.
>> then tell me if IETF WG meetings with remote presentation
>> via Meetecho are anything other than a complete waste
>> of time.
>>
>
> The NTPWG had a very successful experience, including remote presenters, and remote people going back and forth with their interaction.
>
> I would say your experience is atypical, and certainly not the desired outcome.

+1 on this.

I have spent the past meetings doing frequent jabber scribe work. I use 
Meetecho to do this, and I place myself next to the front participant mic 
(so I can see the name tag of the person speaking), and then I type on 
jabber the name of who the person speaking in the mic. There is (I've been 
told) now a suggestion to the IETF secritariat to reserve the seat next to 
the front mic (at table) for Jabber scribe, and this would be great. Now 
we just need to teach everybody to flash their badge to the jabber scribe 
as well.

I have long offered to call out the slides (which is typically needed for 
people who are on audio+jabber only) if someone wanted it, but the past 
few meetings nobody has requested that. My guess is that most people use 
Meetecho because it gives the complete view of what's going on, you get 
chat+presentation+video+sound, and you can also ask questions (which was 
used numerous times in the sessions I participated in).

Generally, I'm very happy with Meetecho (wonders of HTML5+WEBRTC to be 
able to run this in just a browser). There were some initial sound 
problems on monday morning, but that was quickly rectified.

I also really appreciate the fact that I can call out "meetecho" in the 
jabber room to notify them of potential problems, and they immediately 
dispatch someone to fix the problem (including alerting the A/V crew if 
it's a local issue).

So while there were a few hiccups, I'd say most of the time Meetecho and 
the local A/V works great.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se