Re: Proposal: an "important-news" IETF announcement list
Tim Wicinski <tjw.ietf@gmail.com> Sun, 26 September 2021 14:54 UTC
Return-Path: <tjw.ietf@gmail.com>
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 20CA23A2741; Sun, 26 Sep 2021 07:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Z9RQsZMBzsY2; Sun, 26 Sep 2021 07:54:18 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 687FB3A273F; Sun, 26 Sep 2021 07:54:18 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id y26so25200277lfa.11; Sun, 26 Sep 2021 07:54:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3I8JOE4C8TbsX5GvC8JbosyGgafQlCILCR0+SG/gzrs=; b=D1vS7bnahPqvXtNpM4DxDyoSIoN0sx9lhKB1l4wZRheZFWU309blz+RtTgckvtkSXF p/iZ5WY42TNAJI1qNjqQk+YP9iI/ki86YAOqUOkW9DNOLwmlnlqh0YGA0q5MpO4FA5u1 pWSqx4UMPZPirnnQlF6V0+Mq05DD9bhaa5RsRR2IqW7WNDgCDJ7LsreHFGJLeLFKB88v OzmYGQwO9mS6OsFfo2Rwqq8FIT+g8ElvDOA5yP2v1rWBSs7fN6YK6m6ROl2lh36815QV dM+xC6sE2sKXbBtvQoQATNjGX7f9ZP25EU65NN8XUfH29wm7J25DgJGeyN5ISqllIcEb tvoA==
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=3I8JOE4C8TbsX5GvC8JbosyGgafQlCILCR0+SG/gzrs=; b=W0bzs1sLMl50yg8eyWmu1ybOf+vUTpDEzbDmi9scoeNfv3zdEFTQYtJKHvBmnV7a3o DEE4XwxBZP0p5OtUy4F7g1gAqFmodJpiyqIR5lZJ2vnq9iWr+f31r2cd7xrLJbG6rV0L lwG3GXYPUCfw3n82toOZ9pSd5ZqKl4eAdlV0p37uK0nmi4F9dWnEz0D0szVUONY7bS1C acpxWWqHgUVd79kfst2C7Na996ZXfQCcQsBhJ8f4+/3zrDfGrbBearazWogxRxi+/qhB z5vspxkstJZI7Q6uT6/MYtBO0iZom/mK9EN5v3NKH2qHTfr9/quqMCpTrxjIXzk5ce/P +kqg==
X-Gm-Message-State: AOAM533WYv6J4xD2EFzNUmQehpwrrzY1QfSRPrsWoOBbL6xx46SCeF4j El0UdZAxz38aBbPfZ/R+vqtnyLQ7tL0Po9TkBEwspML9
X-Google-Smtp-Source: ABdhPJwAgjqIxBYknlowQj7LXeBG2QVfYfMDzuQ19C+3RIh6C7jJVknyCzxbEl+iImm45LGtHl8A3KgiLQm18rY8A/A=
X-Received: by 2002:a2e:4b09:: with SMTP id y9mr23088566lja.201.1632668056429; Sun, 26 Sep 2021 07:54:16 -0700 (PDT)
MIME-Version: 1.0
References: <71651F0B-0C5C-45D5-9780-926A25C9403E@ietf.org> <D148B2AA-E909-4C7A-BE68-65B104B2C338@gmail.com>
In-Reply-To: <D148B2AA-E909-4C7A-BE68-65B104B2C338@gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 26 Sep 2021 10:54:04 -0400
Message-ID: <CADyWQ+G_rjwYqJ49gWGWgugeA_Y7cwCRp_7LQ56cvn04ebt3+Q@mail.gmail.com>
Subject: Re: Proposal: an "important-news" IETF announcement list
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IESG <iesg@ietf.org>, Working Chairs <wgchairs@ietf.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008a329c05cce727e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/jljMc9aKrbpN5Ft8lF3Ax2O4dss>
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: Sun, 26 Sep 2021 14:54:24 -0000
As someone who files ietf-announce into a folder because there are too many messages, I feel most able to respond to this.... I propose the name be "ietf-announce-announce" because it tells me as a consumer that "this is more important messages that must be read, rather than the regular important messages like Yet Another interim for anima or cbor (*)". I do think that the whole focus on Datatracker accounts is really the wrong way to look at engagement. tim (*) no offenses to anima or cbor working groups, they do fine work. On Sat, Sep 25, 2021 at 12:03 PM Bob Hinden <bob.hinden@gmail.com> wrote: > Lars, IESG, > > I have some questions that would be helpful to know before evaluating this > proposal. See below. > > Bob > > > > On Sep 24, 2021, at 12:25 AM, IETF Chair <chair@ietf.org> wrote: > > > > Hi, > > > > at the moment, ietf-announce is the main announcement list of the IETF, > > seeing regular posts from various roles and bodies in the organization, > > and from the Datatracker. Over the last year, ietf-announce has seen > > around 1200 emails, averaging around 4.6 emails per workday. > > Like what Brian and other have said, 4.6 emails per workday doesn’t seem > like a burden to me. BTW, assuming “workday” means Monday-Friday, it’s > only 3.3 emails per day over a year. > > > The ietf-announce lists currently distributes the following types of > > announcements. All but the first type are automatically generated by > > various tools: > > > > 1. Announcements sent manually by the IETF Chair, the IAB Chair, the > > IRTF Chair, the Chair of the LLC Board, the IETF Executive Director, > > the NomCom Chair, and the IETF Secretariat > > 2. Announcements of new and updated WG charters > > 3. WG closure announcements > > 4. Announcements of new non-WG mailing lists > > 5. Announcements of new RFCs > > 6. IESG and LLC telechat announcements > > 7. Announcements of document actions > > 8. Announcements of IESG conflict-review results > > 9. Last call announcements for I-Ds > > 10. Interim WG meeting announcements > > Please break this down further. That is, how many emails of each type > per year. It’s hard to evaluate this proposal without knowing that. > > > The ietf-announce list currently has 3095 subscribers, which is a > > fraction of the overall IETF community. Only 961 of these subscribers > > have Datatracker accounts; out of 13311 overall Datatracker account > > holders. > > This is disturbing. How can one function in the IETF when you aren’t > getting information about meetings, draft deadlines, new working groups, > BOFs, etc.? > > How many of these data tracker accounts are active? I wouldn’t be > surprised that a large portion of them haven’t been used for a while, or > sent email, etc. > > > > When asking IETF participants about why they are not > > subscribed, the volume of email on the list > > - especially automatically-generated Datatracker email - is the most > often > > mentioned reason. > > How many "automatically-generated Datatracker email” are there? Are all > except for 1. in the numbered lists data tracker generated? > > > > > The IESG is therefore considering creating a new mailing list for > > important organizational announcements only. We are hoping that a > > subscription to a new low-volume mailing list will be acceptable to > > IETF participants that find ietf-announce too noisy, and will help us > > disseminate important news and announcements more widely and effectively. > > > > Here are the details about this proposal: > > > > * The name of the new mailing list is important-news. > > Suggest “ietf-important-news”, like “ietf-announce”. > > > > > > - The ietf-announce mailing list will continue to operate as-is. > > > > - Posting rights to important-news are restricted to the same set of > > roles as for ietf-announce. > > > > - All emails sent to important-news will be CC’ed to ietf-announce. > > > > * Posts > > > > - important-news will only receive the first type of announcements in > > the numbered list above, i.e., important announcements that are > > manually sent by various organizational roles. > > > > - important-news will not receive any of the other types of email sent > > to ietf-announce. In the rare case that one of these is of > > sufficiently broad community interest to be distributed via > > important-news, this will occur as a manual action by one of the > > roles authorized to post to important-news. > > > > * Subscriptions > > > > - Every participant with a current Datatracker account will be > > automatically subscribed to important-news. > > > > - Every participant creating a new Datatracker account will > > automatically be subscribed to important-news. > > > > - important-news is also open to manual subscriptions to anyone > > without a Datatracker account. A welcome message will be sent to > > new important-news subscribers, explaining what it’s for and that > > we’d hope they stay subscribed. It will also include instructions > > or ideally a link for unsubscribing. > > > > - Any important-news subscriber can unsubscribe at any time. > > > > The IESG is inviting community feedback to iesg@ietf.org about this > > proposal by 7 October 2021. > > > > Lars Eggert > > IETF Chair (on behalf of the IESG) > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@ietf.org > > https://www.ietf.org/mailman/listinfo/ietf-announce > >
- 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