Il 10/04/2016 20:04, John C Klensin ha scritto:
--On Sunday, April 10, 2016 19:33 +0200 Meetecho IETF support
<[email protected]> 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.
Good point. A "one minute to disconnection" warning would be trivial to
add. We'll introduce it in the next version.
Thanks,
the Meetecho team
john
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet
