From nobody Fri Jul 30 15:25:17 2021 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDD93A13A8 for ; Fri, 30 Jul 2021 15:25:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.849 X-Spam-Level: X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 DWjh6tF_IXZy for ; Fri, 30 Jul 2021 15:25:13 -0700 (PDT) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2B943A13A4 for ; Fri, 30 Jul 2021 15:25:12 -0700 (PDT) Received: by mail-ej1-x631.google.com with SMTP id gn26so19414625ejc.3 for ; Fri, 30 Jul 2021 15:25:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=NfwzS4rPuwbP1ZIFlZ69YZ7Hq60mW3jLC57TNEukoCw=; b=XawFKYjGJZ54VXIk8VWmnqqF5FS6N6EZgtRvr4qo6H343wlXO+ZZntNM4RE0LY+ST6 VvshEBNmZdYh1FQjmwemlK9Fe/rh4fwqdJ4hpLWf7Z6pP5kQfxAe+iM5wPoskACF4m/o +cKgF1YkqpVqLMdJ3SyRXEnWd4qE+5bjSr3YWO3czzqUomkUqW9+UKYVOmvH+Xgh47M+ 8GCBobYUX5ZMsROJNNU3D48SoWPid64zKfUfjH1c3UxqHqNe8vCWpjuarKQa99JuaaXw 0NEMi3gPN0y+qPsX5w1l7StBMVSj4jfmrZX2hPjTDxJYNryHYK3PPwYBERd5pk58gAVu IH2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=NfwzS4rPuwbP1ZIFlZ69YZ7Hq60mW3jLC57TNEukoCw=; b=ljAddzLipZZZIr2jNGdH5gM76LLPlC7nso3a+jqnQ4NQ2mYcScSETWAFhtjGPB1oyZ pc64oDdT7KpHIc3tqOAsVWNQn0PFROCyKnd8V7QMJQUUUIUIT0hGB+ec3tBI6or8jynS m8YOo6k6LUXrl4ds29wbIpPYq7fd4cveYT4H/rd/RLmwhkikyNkX5BwvpoTtUoLqETE1 l9prqygaaGBKatsPN+bP9OjUlS1tJuoWFGf7GWVo1IFOPP1sffcSKX4uotQ62geBRCqZ 7MNa4+jX3JJGMtVSsmLcnH1ZdE3nIugqdVy6Ca3YkkWVvlN294602Lw5E2fqdcdewpk/ FKAA== X-Gm-Message-State: AOAM532xWHeNBT5f8iQzWJGyw2HDFCOpt8gAL0TJif/TIRkw8Q6srrrU j35w/Q0mC+GSfzjPYKX9wE5lk7uo2sinrEo3UJU= X-Google-Smtp-Source: ABdhPJyV932I/PCFgufsbzZTpjjqSkO5RRW5dTMTS0unxLCEziHYwv92IKltNFdnDQb3bSRW0861wpI+gdYwXFLDAFM= X-Received: by 2002:a17:906:ae8f:: with SMTP id md15mr4774388ejb.198.1627683910686; Fri, 30 Jul 2021 15:25:10 -0700 (PDT) MIME-Version: 1.0 References: <124013E8-300D-4CD4-9E36-9D166716BFE0@gmail.com> In-Reply-To: <124013E8-300D-4CD4-9E36-9D166716BFE0@gmail.com> From: Jen Linkova Date: Sat, 31 Jul 2021 08:24:59 +1000 Message-ID: Subject: Re: Closing the queue To: Fred Baker Cc: wgchairs@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2021 22:25:15 -0000 On Sat, Jul 31, 2021 at 6:33 AM Fred Baker wrote= : > > I would suggest that one say =E2=80=9CI=E2=80=99m closing the queue after= =E2=80=9D, and have a way to tell meet echo that it should stop putti= ng new people in the queue. Actually I'd say that "hard lock" might be suboptimal - sometimes we might still want people joining after the queue is closed as an exception - like an AD making comments etc. In real life even after the queue is closed people still can jump to the mic to respond to comments etc. Personally I'd be very happy if I can click on "closing the queue in 15 secs" and the queue section goes, for example, orange and the title says "QUEUE: CLOSING". After 15 sec it goes red(*) and marked as CLOSED. As a result it's clearly visible for the participants that it's closed and for the chairs that they need to re-open before/during the next talk, white there is still possible to join it. (*) color examples are chosen randomly and might not accommodate color-blind cases. > Sent from my iPad > > > On Jul 29, 2021, at 6:58 PM, Jen Linkova wrote: > > > > =EF=BB=BFWhile I'm very happy with Meetecho (wow, I've just managed to = chair a > > session single-handed!), there is one missing feature which would make > > me very happy. > > > > Wouldn't it be great if we have a button to mark the queue "closed"? > > It might be just me but I really, really hate interrupting people just > > to say "I'm closing the queue after". Having smth like "The queue will > > be closed in 5..4..3..2..1" would be even better.. > > > > Is there anyone else missing this feature? Or I'm just not aware of > > the best current practices in keeping the session on time? > > > > -- > > SY, Jen Linkova aka Furry > > --=20 SY, Jen Linkova aka Furry