Re: Proposal: an "important-news" IETF announcement list
Robert Sparks <rjsparks@nostrum.com> Wed, 29 September 2021 14:53 UTC
Return-Path: <rjsparks@nostrum.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 C2F733A1ABA; Wed, 29 Sep 2021 07:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level:
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 ETu6LQwsaC1U; Wed, 29 Sep 2021 07:53:46 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0FFE03A1C09; Wed, 29 Sep 2021 07:53:11 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 18TEqxeA078791 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 29 Sep 2021 09:53:00 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1632927181; bh=WRfKq4jFSZPisY0Jt9bJrvc5F13dUXBbnpyN06svat8=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=JQ4XNxa1rU6OmfHqFj/J/u4nJUjCz5oEpZYszxhsDJlUY9Y0BCTjoP4Y16fC1jJ8/ 4/PqfRD1VGW8Fv4P2kZOu+DIKJzwpKgZreZq+T46awaNbKmnrtItrJDX+37IYn93Vv xlxU97Wxg/NOmoZYqsm5xYQd19c2MUNE1SWAwi+I=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, Lars Eggert <lars@eggert.org>
Cc: Working Chairs <wgchairs@ietf.org>, IETF <ietf@ietf.org>
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> <29d2a637-f629-b494-1cb5-75510e6149dc@isode.com>
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Proposal: an "important-news" IETF announcement list
Message-ID: <2152b7c0-9538-76cd-e0a7-0efe81c3cce1@nostrum.com>
Date: Wed, 29 Sep 2021 09:52:54 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <29d2a637-f629-b494-1cb5-75510e6149dc@isode.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/HiitZgDt0LI53IasYS4cYHX7WoM>
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: Wed, 29 Sep 2021 14:53:51 -0000
On 9/29/21 9:32 AM, Alexey Melnikov wrote: > Hi Barry, > > On 29/09/2021 15:08, Barry Leiba wrote: >>> 1. Announcements sent manually by <various roles> = 284 >>> 2. Announcements of new and updated WG charters & WG closures = 44 >>> 3. (included in above 44) >>> 4. Announcements of new non-WG mailing lists = 13 >>> 5. Announcements of new RFCs = 275 >>> 6. IESG and LLC telechat announcements = 39 >>> 7. Announcements of document actions = 175 >>> 8. Announcements of IESG conflict-review results = 14 >>> 9. Last call announcements for I-Ds = 174 (+ 4 for other actions) >>> 10. Interim WG meeting announcements = 256 >>> >>> The "important-news" proposal would only retain those under (1) above. >> I think that 1, 4, and 6 should all be retained as is (and in the new >> list, if it's created). >> >> I think that 2, 5, 7, 8, 9, and 10 should be in a weekly summary, one >> single message per week. > > I have a slight problem with this proposal because if it is > implemented it would not be possible to find last call announcements > by draft name. I think this is a rather important feature when > searching archive. This aspect - search for "thing" by looking for it in email Subject lines is what's driven so much of what people are now proposing to condense. Alexey points to a big use case - since people _reply_ to Last Call messages, searching for the subject is an easy way to find threads. Note the CCs on the Last Call messages currently going to IETF Announce. Similarly, the "string of interims announcements" that was brought up is the way it is now because people _asked_ for one message per session that they could easily search for and easily visually scan for these (with the date) by subject. It started as one message. I'm happy to change this to whatever/wherever, but recognize that what's happening now was shaped by community feedback. > > Unfortunately I don't have a solution for this problem. > > Best Regards, > > Alexey >
- 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