Re: [vmeet] meetecho for remote presenters
Simon Pietro Romano <spromano@unina.it> Wed, 13 April 2016 10:30 UTC
Return-Path: <spromano@unina.it>
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 BE44A12DFD1
for <vmeet@ietfa.amsl.com>; Wed, 13 Apr 2016 03:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level:
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001,
RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 61REHeIn4V5b for <vmeet@ietfa.amsl.com>;
Wed, 13 Apr 2016 03:30:08 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id B110F12DE13
for <vmeet@ietf.org>; Wed, 13 Apr 2016 03:30:07 -0700 (PDT)
X-ASG-Debug-ID: 1460543402-05f27525952d09bf0001-CNPnNC
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by
brc2.unina.it with ESMTP id AyEcuUztGENjt6WP (version=TLSv1 cipher=AES256-SHA
bits=256 verify=NO); Wed, 13 Apr 2016 12:30:02 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [143.225.28.167] ([143.225.28.167]) (authenticated bits=0)
by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id u3DAU0vA019060
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Wed, 13 Apr 2016 12:30:01 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: [vmeet] meetecho for remote presenters
In-Reply-To: <3E566B8155D6ECD9DEE2C9D3@JcK-HP8200.jck.com>
Date: Wed, 13 Apr 2016 12:29:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F44A990-5E7B-471F-BCDD-9330385959A5@unina.it>
References: <22117.1459805337@obiwan.sandelman.ca>
<1F26B780-F115-47A7-AEA1-BCA1F98BBF0E@att.com> <5703D26A.60900@meetecho.com>
<81911456-6302-4445-AEFB-E2AEF8DCECEC@att.com>
<5707B55B.6080308@meetecho.com> <3E566B8155D6ECD9DEE2C9D3@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.2098)
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1460543402
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0
tests=BSF_SC0_MISMATCH_TO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.28693
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------
0.00 BSF_SC0_MISMATCH_TO Envelope rcpt doesn't match header
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/o8tVvHfaocBQCy3kpxN-J7VY3sQ>
Cc: vmeet@ietf.org
Subject: Re: [vmeet] meetecho for remote presenters
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: Wed, 13 Apr 2016 10:30:10 -0000
Hello John, I personally fins your points from 1 to 5 definitely reasonable, as well ad technically feasible. Point 6 would probably deserve some more in-depth discussion. Simon > On 12 Apr 2016, at 12:51, John C Klensin <john-ietf@jck.com> wrote: > > Coming back to part of this and dropping the tools list... > > --On Friday, April 08, 2016 15:42 +0200 Meetecho IETF support > <ietf@meetecho.com> wrote: > >> ... >>> Sometimes doing a refresh loses the room information and it >>> prompts for a room name. Huh? And the prompts look really >>> messed up on my screen, with the button on top of the input >>> textbox. >> >> By design, you should be redirected to the same login page you >> used to join in the first place, and it should remember >> whatever you put in there automatically. If that's not always >> working as expected, it's a bug ad we'll have to look into >> that. You're probably ending up in a login page that actually >> forgot part of that info (e.g., the WG you were following), >> which uses a different layout. >> >>> After typing in the registration number, there is a >>> background load of your saved picture, AND a very annoying >>> expansion of the area above the name to display the saved >>> picture or placeholder picture. The reason it's annoying is >>> that when you're trying to log in (or RE-login quickly to >>> avoid missing more of the meeting), the check boxes are >>> moving around the screen right when you're trying to click >>> them, you're chasing them around the screen and losing time >>> waiting for them to settle down. > >> Ack, we'll need to fix that. The avatar feature is a brand new >> one we just added for the meeting here in BA, so there are >> indeed improvements that are needed on the user experience >> there. > >>> Relaunching the window from agenda starts all over from the >>> very beginning login screen. If you previously clicked >>> "remember my login info", it fills in the name and >>> registration info. But you still need to re-click the buttons >>> acknowledging the note well. I also click "remember my login >>> info" again "just in case". It seems like this scenario could >>> be streamlined better when you're re-logging in to an >>> on-going session and you're trying to miss as little as >>> possible. > >> Makes sense, and I guessthe "Note well" part is particularly >> annoying as it prevents you to join if unchecked. If you >> checked it once, you did confirm you read it, and we should >> remember that as well. > > This may be aspirational, i.e., a target rather than something I > expect you to be able to do all of, all at once, but... > > My expectation in a more perfect world that [still] requires > IETF registration and sign-on using a registration number is > that > > (1) You would consult the IAOC and, if needed, IETF Counsel, but > remember that, if one has registered for the IETF meeting, one > has already seen and acknowledged the Note Well. If doing so > the week of the event is needed or if someone is logging in as > an observer (in which case they may be claiming to be > not-Participants and not Contributing anyway), see below. > Otherwise, the checkbox is just clutter and unnecessary > bureaucracy. > > (2) I'm a lot more concerned with participants and efficiency > for them than I am above [passive] observers. I'm willing to > have a "remember me" checkbox for observers but, if some of the > following inconveniences them, that seems a minor price to pay. > An observer who is sufficiently inconvenienced can always sign > up, especially as long as the remote participant registration > fee is zero or nominal. > > (3) During the course of an IETF week (or other set of related > meetings within a short period), I expect to register in the > sense of giving you my name, registration number, assurances > that I've seen and understood the Note Well, preference for > participant versus observer, picture or avatar, etd., a maximum > of one time. "Remember me for the duration" or "Remember me > until..." should probably be the default with "don't remember, I > want to be bothered every time to add some marginal privacy" > available as an option. A "settings" mechanism for changing any > of those things should be available, but it shouldn't be > intrusive. I expect that single registration to work even if I > switch machines. If you have to give me a special token or > unique "log in again, maybe from the different place" URL that > is fine, but the idea should be for me to register once and > thereafter only go through a quick re-validation or > re-authentication process, not be forced to supply all of the > prior information. > > (4) In particular, while I hope restarting sessions will become > much more rare, there should be no circumstances in which a > restart within a given WG meeting requires reentering > registration information, much less reconfirming > participant/observer status, acknowledging the Note Well, being > asked to supply a picture, etc. > > (5) As Dave Crocker has explained in much more detail than my > original comment about the Jabber aspect of the situation did, > precipitous shutting down of a session in a way that loses > information is not acceptable even if it means rethinking what > "session" means. Jabber is not the only issue. "Participant" > is defined in many different ways in the IETF. If I sign a WG > meeting blue sheet, I don't get to un-sign it by leaving the > room before the WG meeting is over. If you are adopting a > variation on the blue sheet definition (which, you will recall, > was used to justify the registration requirement), the > participant list should show all of those who connected to a > given WG, probably with an indication of whether they are > on-line or not and possibly whether they are local or remote, > not just the Jabber definition of "connected right now". Maybe > there is also a difference between someone explicitly signing > off and simply disappearing (possibly as a result of a dropped > connection rather than participant action). Probably that list > shouldn't abruptly disappear when the meeting ends either -- > another matter you should sort out with the IESG (and maybe > IAOC). > > (6) I'm one of the people who believes that we lost something > when overhead projector foils -- which could be easily and > quickly marked up during a talk or discussion-- gave way to > PowerPoint (TM; grumble). No matter how much we campaign for > presentation materials being uploaded well in advance of > sessions, I hope there will always be the possibility of the > kind of last-minute changes that come from last night's hall > conversation or this morning's breakfast (those conversations > are among the things that actually make f2f meetings > worthwhile), so removing the slides from the screen the instant > the projector goes off may not be optimal and shifting > _exclusively_ to "show from local PDF copy of what was uploaded > a week ago" may not be either. > > best, > john > >
- [vmeet] meetecho for remote presenters Michael Richardson
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Fred Baker (fred)
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Brian E Carpenter
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Carsten Bormann
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Simon Pietro Romano
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Simon Pietro Romano
- Re: [vmeet] [Tools-discuss] meetecho for remote p… joel jaeggli
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Brian E Carpenter
- Re: [vmeet] meetecho for remote presenters HANSEN, TONY L
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Brian E Carpenter
- Re: [vmeet] meetecho for remote presenters Meetecho IETF support
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Meetecho IETF support
- Re: [vmeet] meetecho for remote presenters Meetecho IETF support
- Re: [vmeet] [Tools-discuss] meetecho for remote p… Michael Richardson
- Re: [vmeet] meetecho for remote presenters HANSEN, TONY L
- Re: [vmeet] meetecho for remote presenters Paul Kyzivat
- Re: [vmeet] meetecho for remote presenters Meetecho IETF support
- Re: [vmeet] meetecho for remote presenters Paul Kyzivat
- Re: [vmeet] meetecho for remote presenters HANSEN, TONY L
- Re: [vmeet] meetecho for remote presenters Paul Kyzivat
- Re: [vmeet] meetecho for remote presenters Michael Richardson
- Re: [vmeet] meetecho for remote presenters Ray Pelletier
- Re: [vmeet] meetecho for remote presenters Meetecho IETF support
- Re: [vmeet] meetecho for remote presenters John C Klensin
- Re: [vmeet] meetecho for remote presenters Simon Pietro Romano