Re: [vmeet] Meetecho sessions start/stop time
John C Klensin <john-ietf@jck.com> Sun, 10 April 2016 18:05 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id D00EC12B053
for <vmeet@ietfa.amsl.com>; Sun, 10 Apr 2016 11:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996]
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 p__VntrjFX2Q for <vmeet@ietfa.amsl.com>;
Sun, 10 Apr 2016 11:05:00 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 9429712B074
for <vmeet@ietf.org>; Sun, 10 Apr 2016 11:05:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com)
by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD))
(envelope-from <john-ietf@jck.com>)
id 1apJjH-000F5b-Am; Sun, 10 Apr 2016 14:04:59 -0400
Date: Sun, 10 Apr 2016 14:04:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Meetecho IETF support <ietf@meetecho.com>, vmeet@ietf.org
Message-ID: <20F7413E33810665077E7003@JcK-HP8200.jck.com>
In-Reply-To: <570A8E5C.8040301@meetecho.com>
References: <570A8E5C.8040301@meetecho.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/HqJdcKeB6hKAFK77yP3S9EAM0C8>
Subject: Re: [vmeet] Meetecho sessions start/stop time
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>,
<mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>,
<mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Apr 2016 18:05:02 -0000
--On Sunday, April 10, 2016 19:33 +0200 Meetecho IETF support <ietf@meetecho.com> wrote: > Folks, > > just to clarify that Meetecho sessions do start 5 minutes > before the WG meeting scheduled start time, and never stops > before the meeting has actually finished. > > Only when the previous meeting runs *very* long, we have to > shift the start time of the following Meetecho session. This > is needed in order to avoid overlaps in the recordings. This > was the case of the 6LO session on Thursday, which started at > 17.30 sharp because the MTGVENUE session ended at 17.30. Understood, but I encountered another problem that you might want to think about. There were a couple of times when I was typing something into Jabber (via Meetecho) when the session ended. That resulted in the screen, and Jabber session, abruptly clearing, so I couldn't finish the message for the Jabber log, copy the partially-finished one so I could later send something similar in email, or otherwise salvage what had been typed already. I don't have suggestions other than maybe keeping the Jabber window/link open for several minutes after the meeting ends and/or putting up an "about to go down, save work if you want it" warning with a bit of delay, or something of that nature. I'd simply run a session with a separate Jabber client, but that introduces some extra synchronization problems. john
- [vmeet] Meetecho sessions start/stop time Meetecho IETF support
- Re: [vmeet] Meetecho sessions start/stop time John C Klensin
- Re: [vmeet] Meetecho sessions start/stop time Dave Crocker
- Re: [vmeet] Meetecho sessions start/stop time Paul Kyzivat
- Re: [vmeet] Meetecho sessions start/stop time Meetecho IETF support
- Re: [vmeet] Meetecho sessions start/stop time Dan York
- Re: [vmeet] Meetecho sessions start/stop time Dave Crocker