Re: Meetecho was Re: Concerns about Singapore

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 12 April 2016 12:35 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 D96BD12EC53 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level:
X-Spam-Status: No, score=-4.517 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_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 rwxYkdtSwAzB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:35:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD3812DFF4 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:35:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCZlPS026515; Tue, 12 Apr 2016 13:35:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CCZlPS026515
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460464547; bh=5uFHgPQDiAIHLbkHd6i1Hs8v5WA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=e9xNVLzZOt5aH1GXui3zhagOOP/k8pJkd1viu6lBVisGIE9SUi1SXMJt2Jqlhwapm ZD1Xeh/HsvRKZQbkh9iC/AsmH8WDdJbefl13c0Qin9rXzcH3zZVPf6jqgt4snlwvkA wW5b9zxgpMSkYEpmPuTzCECjIXH3Mi9tbQDGndME=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BDZl32192067906d ret-id none; Tue, 12 Apr 2016 13:35:47 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCZeAl014471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 13:35:40 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Meetecho was Re: Concerns about Singapore
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se>
Date: Tue, 12 Apr 2016 13:35:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6105314ca86919853e4a12a21c94d38as3BDZl03tjc|ecs.soton.ac.uk|2ED8F5F5-126E-44C1-A4E4-54E9C7881CDD@ecs.soton.ac.uk>
References: <20160411223403.GA6743@gsp.org> <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com> <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net> <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se> <2ED8F5F5-126E-44C1-A4E4-54E9C7881CDD@ecs.soton.ac.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BDZl321920679000; tid=s3BDZl32192067906d; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CCZlPS026515
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zOPbZ_Ord8DR7gQtPPpyf5cv6_0>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
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:35:53 -0000

> On 12 Apr 2016, at 13:19, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> 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 also do this, and agree it’s a good idea.

> 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).

I also noticed that remote people don’t seem to want slide numbers called out now. Might be interesting to see if we have stats on numbers of people listening to the old school audio-only streams, or on non-Meetecho participants in Jabber (the login IDs of Meetecho people is distinctive there…), just to get some data points on current trends.

> 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).

Just like Beetlejuice :)

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

Agreed.

Tim

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