[Tools-discuss] Collection of glitches on the nonwg mailing lists list

John C Klensin <john-ietf@jck.com> Wed, 05 June 2024 01:29 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3F7C1D5C7D for <tools-discuss@ietfa.amsl.com>; Tue, 4 Jun 2024 18:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsvkTpRev0Ox for <tools-discuss@ietfa.amsl.com>; Tue, 4 Jun 2024 18:29:57 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9D3DC1DA1EF for <tools-discuss@ietf.org>; Tue, 4 Jun 2024 18:29:56 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1sEfTN-0006AQ-8z; Tue, 04 Jun 2024 21:29:53 -0400
Date: Tue, 04 Jun 2024 21:29:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: tools-discuss@ietf.org, Greg Wood <ghwood@staff.ietf.org>
Message-ID: <BDC0BD8CA3C26B3F174FC1E8@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Message-ID-Hash: AM2727BXVDNHB5DUQVRJAUWIVXQIURIU
X-Message-ID-Hash: AM2727BXVDNHB5DUQVRJAUWIVXQIURIU
X-MailFrom: john-ietf@jck.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Orie Steele <orie@transmute.industries>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Collection of glitches on the nonwg mailing lists list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/0jZQQMBcGOabhaXWDHBUCsOevBk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

Sorry.  While the message below was sent to tools-help as directed on
the relevant page, I have just discovered it is a more general
problem.   Especially given Greg's recent note on the IETF list about
other Postorium/ Mailmain 3 issues, it may be worth warning others
and perhaps more general discussion.

Apparently, if one goes to https://datatracker.ietf.org/list/nonwg (a
place some, I suspect many) of us go to track down information about
particular mailings lists, what they are called, and the location of
subscription information and archives, many of the entries have
broken links. In a non-trivial number of cases, the problem is that
the entry for list "foo" points to
https://mailman3.ietf.org/mailman3/lists/Foo@ietf.org/ where it
should point to
https://mailman3.ietf.org/mailman3/lists/foo@ietf.org/, where the
actual information is available.

While "i18ndir", as discussed below, may be obscure, I note, as
particularly interesting, that
   alldispatch
   architecture-discuss
   art
   eligibility-discuss 
   gen-art
   hotrfc
   iab
   i-d-announce
   ietf-announce
   ima
   int-area
   mib-doctors
   mtgvenue
   ops-area
   rfp-announce
   rsab
   terminology
   tools-help
   tools-discuss
   training-wgchairs
   travel-grants-committee
   tsv-art
   wgguide
that is by no means a complete list but illustrates that the problem
spans a broad range of IETF Areas and IETF-related activities and
groups including the LLC, IAB, IRTF, and RFC Editor policies
(although RSWG does not appear on the list at all, something I think
has been noted previously).  Many other lists work.  I don't know if
they have been individually reported and patched or if there is some
pattern I cannot discern.

But it is probably time, before we conclude that the transition to
Mailman3/ Postorius is complete, for someone to go through that page,
test all the links, and fix the ones that produce "no found"
errors... and do that before IETF 120 for which a subset of those
listed above (and maybe others) might be particularly important. 

Suggestion if that cannot be done Real Soon Now: It appears as if
there is a dedicated "page not found" catcher in Postorius because,
all of the bad links produce the same "Page not found": "This page
either doesn't exist, or it moved somewhere else." page.   Can that
be modified to suggest that people inspect the URL that produced that
page and, if it contains upper-case characters, they experiment with
changing them to lower case and trying the URL again.  I've tried
several, but not all, of the cases listed above and those that I
tried worked.  Obviously not ideal, but better than leaving people
wondering and frustrated.

More below about digging into a specific case and a few other
problems.

best,
   john



--On Tuesday, June 4, 2024 20:11 -0400 John C Klensin
<john-ietf@jck.com> wrote:

> Hi.  
> On <https://datatracker.ietf.org/list/nonwg>, the entry for
> "i18ndir" points to
> <https://www.ietf.org/mailman/listinfo/I18ndir>, which produces a
> "page not found" message.   
> 
> This appears to be another instance of a case-sensitivity problem
> because https://www.ietf.org/mailman/listinfo/i18ndir produces a
> relevant page.  
> 
> I'm uncertain about the status of that list.  On the one hand, the
> directorate was closed some time ago.    On the other, it might be
> the last useful centralized list for i18n discussions or, if there
> is another one, it should probably be reflected on the i18ndir page
> once it can be found in the obvious way.
> 
> Also, IIR, while the directorate was active, directorate (and hence
> mailing list) membership was by invitation.  This page seems to
> imply that anyone can now join, which might or might not be what is
> wanted.
> 
> The ADs should probably make up their minds and then the link should
> be corrected and the mailing list page tweaked and/or the entry
> moved from the "nonWG" page to the "concluded" one.
> 
> General suggestion to the tools team: Unless we have decided that
> the "owners" of a mailing list should be secret, it would be a good
> idea to list them, and maybe their addresses, on the mailing list
> pages. If we have decided their names are secret, I question that
> decision given that, e.g., we make WG Chair names and the like
> public.  At worst, the names should be omitted only if list owners
> request that and get approval some someone like a relevant AD.   
> 
> Probably even more important, there have been enough problems with
> reaching people via ietf.org address aliases that, unless you are
> confident that those problems have been solved --now and forever--
> identifying mailing list "owners" by name (and probably address) on
> the mailing list pages is particularly relevant.
> 
> best,
>    john