Re: [Tools-discuss] Meetecho rooms being opened to chairs 10 minutes before sessions would be _really_ helpful

["Livingood, Jason" <[e-mail]>]

Good point, Toerless. For consideration post-108:
- It would be nice if each meeting session could have its own Meetecho conference ID/URL - rather than a small number that are shared. The key is to remove the limited number of shared rooms.
- Allow users to enter a meeting session 60 mins beforehand and for the session to run for 120 mins afterwards before the session terminates. (Seems logical that they must terminate to free up server resources - but enable some normal meeting time run over as well as post-meeting banter/wrap up.)

Jason

PS - I agree that MeetEcho has done a great job for 108! So these are minor suggestions to improve something already working quite well.

On 7/29/20, 10:54 AM, "WGChairs on behalf of Toerless Eckert" <[e-mail] on behalf of [e-mail]> wrote:

    Adding tools-discuss as the authoritative group for MeetEcho feature requests, bcc wgchairs

    I want to be offensive-ranter (ok, better on smaller groups like BIER):

    I find these strict timelines that MeetEcho introduces extremely terrible.

    We had in BIER a poor presenter cut off just because we had a great presentation
    and discussion in a slot in before and therefore ran out of time.

    How is it possible that in a physcial meeting we are able to utilize all possible
    before andd after meeting times, and now going virtual where we should have
    FEWER time constraints, we enforce MORE ?

    No, i don't think 10 minutes before/after is sufficient. I think it should be
    AT MINIMUM IMHO 30 minutes on both sides, before and after.

    Pls. do not understand this big criticism as a big criticism of the tool.
    It is not. It is just a criticism of this feature. The tool itself is on a great trajectory!

    Cheers
        Toerless

    On Wed, Jul 29, 2020 at 03:46:46PM +0200, Tony Przygienda wrote:
    > That's my 2nd middle name ...
    >
    > lack-of-discipline is yours ;-)
    >
    > -- tony
    >
    > On Wed, Jul 29, 2020 at 3:34 PM Greg Shepherd <[e-mail]> wrote:
    >
    > > Coward. :)
    > >
    > > On Wed, Jul 29, 2020 at 6:10 AM Tony Przygienda <[e-mail]>
    > > wrote:
    > >
    > >> I think the 5 mins before hour cut-off keeps things tight and is a good
    > >> thing ...
    > >>
    > >> -- tony
    > >>
    > >>
    > >> On Wed, Jul 29, 2020 at 3:08 PM Jay Daley <[e-mail]> wrote:
    > >>
    > >>>
    > >>>
    > >>> On 30/07/2020, at 1:01 AM, Greg Shepherd <[e-mail]> wrote:
    > >>>
    > >>> Having them stay open 10min after, or even to the actual WG ending hour
    > >>> would be great too. Not everyone is running off to the next meeting.
    > >>>
    > >>>
    > >>> They can only be kept open for 5 minutes after the scheduled close of
    > >>> the meeting as the same server/room is then used for another session and
    > >>> the 5 minute gap is used to close down the audio stream and other tidying
    > >>> up.
    > >>>
    > >>> Jay
    > >>>
    > >>>
    > >>> Greg
    > >>>
    > >>> On Wed, Jul 29, 2020 at 3:54 AM Jay Daley <[e-mail]> wrote:
    > >>>
    > >>>>
    > >>>>
    > >>>> On 29/07/2020, at 10:47 PM, Tony Przygienda <[e-mail]>
    > >>>> wrote:
    > >>>>
    > >>>> Topic says it all. Rather than scrambling to figure out whether
    > >>>> audio/preso/internet works right @ beginning of session 10 minutes dry-run
    > >>>> grace period would be very helpful
    > >>>>
    > >>>>
    > >>>> They are now open 10 mins ahead of the session starting.  It wasn???t
    > >>>> like that on day 1 but was changed for day 2 onwards.
    > >>>>
    > >>>> Jay
    > >>>>
    > >>>>
    > >>>> -- tony
    > >>>>
    > >>>>
    > >>>> --
    > >>>> Jay Daley
    > >>>> IETF Executive Director
    > >>>> [e-mail]
    > >>>>
    > >>>>
    > >>> --
    > >>> Jay Daley
    > >>> IETF Executive Director
    > >>> [e-mail]
    > >>>
    > >>>

    --
    ---
    [e-mail]