Re: making upcoming calendar more useful
Warren Kumari <warren@kumari.net> Thu, 30 September 2021 03:44 UTC
Return-Path: <warren@kumari.net>
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 11C803A1060 for <wgchairs@ietfa.amsl.com>; Wed, 29 Sep 2021 20:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
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 KBwfD4XStoGM for <wgchairs@ietfa.amsl.com>; Wed, 29 Sep 2021 20:44:06 -0700 (PDT)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 A4A263A1065 for <wgchairs@ietf.org>; Wed, 29 Sep 2021 20:44:06 -0700 (PDT)
Received: by mail-vs1-xe32.google.com with SMTP id p9so201224vst.9 for <wgchairs@ietf.org>; Wed, 29 Sep 2021 20:44:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ncIvXWDOGdr13ekRu6UIbcY+46Zno1UErzBrt1guCsM=; b=fQp8oI8H0z89laeFahTIX554GdpXbFg/YsVUMyph6JcT+59KYEm0JzBFuEBmFqHZm0 9FwGdKlY5P69frAXMITTRQOU5MaA8Gzva0PPf9QnYlEzyKIax57BiGVgf2N3OtQzWBBJ 2kK4JgF9p15uXke5xn/r65NhXSi8IhlPmBc1bSaHKOec2ueP24K3o7beL9H+/cobRq0G vxnGSxnbYy9hmDpGYlgniIUhiegxw8kdlCwHU250kbSVZIUdK1th1NNscexUechZkLOb 4ZXXqrDO415zhxBL2euI4sWh/abWeobccQYjjRVV7LLK7v8mXmJPS4U9d/34FeIvfncG Rkag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ncIvXWDOGdr13ekRu6UIbcY+46Zno1UErzBrt1guCsM=; b=PX6SFvDORnFeVdOsi4GKnLyd+tbY+beXcD71gQGUqtIBFIjdSXJ91Lh3BAhEUONedO UDNDSq8hqwSFSaZ7IgJAZfah7d31OF2pMadJoFBmqRmSMU5Ou8niQTKDG2cPhYjPeVJS YDPIingaAWevK4TezwJtYn+BMWVHUABDJfRvvNdyXdOcC0/DYVg5JCHZa4gQYv7wYa4m 6pxcteiZ1GakBsCsmVYIha3WL3VRWIypDV94nnyGtBbFaUf/TjDkJ3Y+QUQobdvmhCHR YaKepEFG6m+3GA9eUIcVYivJ5gg8JqktG5UXZ0LTYsXDvCnKbmPAW1w+N5VOmYxFghDh HsKQ==
X-Gm-Message-State: AOAM531t+4xXhb1KGXHWuerLZHHMWnVbbLAkzN674wTeyi3OQNkUrO+h 4idOr3WIlccUoZeEMO5vDibFq1Gvpw/oTboowS0vOQ==
X-Google-Smtp-Source: ABdhPJxQp/P3jo/sHCfEW2YrYH/RNbA1LFvkVzT4DnNKpdhiEVr3kM+0rWwI1Q9FFBI/mFUOE5c1Gz20zGi3mkeOZTI=
X-Received: by 2002:a67:fdd3:: with SMTP id l19mr3486625vsq.37.1632973444965; Wed, 29 Sep 2021 20:44:04 -0700 (PDT)
MIME-Version: 1.0
References: <f22d22ea-80da-e595-d91f-c577461766a3@huitema.net> <44B61547-1B28-4D1C-88C1-4AD7BA7F9639@lear.ch> <69E7C755-D09C-447B-B327-4F13C19A3EED@eggert.org> <475d7515-f71a-c3f0-e455-03336226cc47@lear.ch> <04F3603A-514B-49DF-81C5-36023CBBB69E@eggert.org> <CALaySJLseu4Ci_=-OZDN1NKLimnfLSjnPFyv2bwOnOxL6q4RGg@mail.gmail.com> <752027E351A479CDF4CE8CA3@PSB> <5447.1632936013@localhost> <794C7E6FB3F5BDC24B62E30F@PSB>
In-Reply-To: <794C7E6FB3F5BDC24B62E30F@PSB>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 29 Sep 2021 20:43:54 -0700
Message-ID: <CAHw9_iJWThuSjvMdQyEzbqOKYKY2oHUmaWfk2KGbZt9V-B0hWg@mail.gmail.com>
Subject: Re: making upcoming calendar more useful
To: John C Klensin <john-ietf@jck.com>
Cc: IETF <ietf@ietf.org>, Lars Eggert <lars@eggert.org>, Michael Richardson <mcr+ietf@sandelman.ca>, Working Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001d791e05cd2e4270"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/EPxHZ84rFUcIbtvCQNullXQ4WUw>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2021 03:44:12 -0000
On Wed, Sep 29, 2021 at 6:51 PM John C Klensin <john-ietf@jck.com> wrote: > > > --On Wednesday, September 29, 2021 13:20 -0400 Michael > Richardson <mcr+ietf@sandelman.ca> wrote: > > > > > John C Klensin <john-ietf@jck.com> wrote: > > > Announcement list --selective digests, avoiding four > > separate > interim meeting postings at the same time for > > the same WG, > encouraging calendar subscriptions, etc.-- > > then I think we > address the real problem while splitting > > up lists even more just > create distractions. > > > > On the topic of calendaring, and "upcoming" being more useful > > for planning. I've asked for the various area meetings, such > > as the RTG Chairs Chat, IESG telechat, IoT Directorate, etc. > > to be on the calendar. > > > > My purpose is allow people who are planning meetings to know > > what else is occuring. Maybe we can do a "this week at the > > IETF" page. > > > > There are tooling issues for some of these requests. > > But, the major pushback I got was that some of these events > > are not open to anyone, and so shouldn't be listed. I > > disagree :-) > > I do too, for at least two reasons. One is that transparency > suggests that we should not be secretive about which closed > meetings are being held. The other, more important, is that > including the closed meetings makes it much easier for those who > might be involved in, or concerned about, them to spot potential > or actual conflicts. > +1. I think that the transparency of having closed meetings listed will also cause people to reconsider if their meeting *really* has to be closed. W > > john > > -- Perhaps they really do strive for incomprehensibility in their specs. After all, when the liturgy was in Latin, the laity knew their place. -- Michael Padlipsky
- Proposal: an "important-news" IETF announcement l… IETF Chair
- Re: Proposal: an "important-news" IETF announceme… Melchior Aelmans
- IETF calendar (was: Re: Proposal: an "important-n… Toerless Eckert
- Re: Proposal: an "important-news" IETF announceme… Bob Hinden
- Re: Proposal: an "important-news" IETF announceme… Christian Huitema
- RE: Proposal: an "important-news" IETF announceme… Adrian Farrel
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Salz, Rich
- Re: Proposal: an "important-news" IETF announceme… David Noveck
- Re: Proposal: an "important-news" IETF announceme… Tim Wicinski
- Re: Proposal: an "important-news" IETF announceme… Lucas Pardue
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Stephen Farrell
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Carsten Bormann
- Re: Proposal: an "important-news" IETF announceme… Marc Petit-Huguenin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Alexey Melnikov
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- making upcoming calendar more useful Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Martin Thomson
- Why last calls matter more than ever [Re: Proposa… Brian E Carpenter
- Re: making upcoming calendar more useful John C Klensin
- Re: making upcoming calendar more useful Warren Kumari
- Re: making upcoming calendar more useful Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Spencer Dawkins at IETF
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- The links page [was: something else] Brian E Carpenter