IETF Logo Mail Archive

[Gendispatch] Re: Archival Dysfunction

Joel Halpern <jmh@joelhalpern.com> Thu, 11 July 2024 20:03 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F4BC14F5E9 for <gendispatch@ietfa.amsl.com>; Thu, 11 Jul 2024 13:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 0-LEz8i3DuTN for <gendispatch@ietfa.amsl.com>; Thu, 11 Jul 2024 13:03:37 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8976EC14EB19 for <gendispatch@ietf.org>; Thu, 11 Jul 2024 13:03:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4WKlzF2mtTz1ntVn; Thu, 11 Jul 2024 13:03:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1720728217; bh=Z79l7fsvBfW/iNNS/86gfoCSOOmsZLUZl28HhQlLix8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=o0LsYEpJM9t/Eit4fLzGXFIw9rVKXQTz6xmIg2Mtigr/Sh8uG2DdJ8kQECbBmRwOd 7Wp5CWMfJhpNT2Pp4VYYlOS5e7Duu/tEyySj4Q/zKEyyP2CwA4oNhvCYDGiM209bYh lpOk09awz5wgjAxTZuONlSrDRRQOEbxMkMlc63os=
X-Quarantine-ID: <1f10NM98AtR1>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.41] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4WKlz84pX3z1ntXJ; Thu, 11 Jul 2024 13:03:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------hUaJbHySgPTUNwRgnHbcTlSF"
Message-ID: <c338dfe1-2fc5-4056-85bf-28ae742412b3@joelhalpern.com>
Date: Thu, 11 Jul 2024 16:03:31 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: David Schinazi <dschinazi.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <9442CCBF-EDF4-4FD7-AFBA-29EA301FB3DA@akamai.com> <4c00d259-653f-43d1-973e-2f9d38876585@gmail.com> <LV8PR11MB85368D25E41B14A968638AD6B5A42@LV8PR11MB8536.namprd11.prod.outlook.com> <DE8F40AE-8F7E-479C-B4FC-C2CB6929581D@brianrosen.net> <BYAPR05MB53183DC5B81AF7C757932DF0AEA42@BYAPR05MB5318.namprd05.prod.outlook.com> <CAPDSy+4GNt3aXkd2McYEo5U47wM=szrCYfk3-g=ijDMvviOjEg@mail.gmail.com> <9997553d-15e2-4a44-849a-67345fa55fd8@cs.tcd.ie> <CAPDSy+529fQj=J9=920fapZQe8n1hLeKZj4Gv9_qGBmw=eX5WA@mail.gmail.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CAPDSy+529fQj=J9=920fapZQe8n1hLeKZj4Gv9_qGBmw=eX5WA@mail.gmail.com>
Message-ID-Hash: JIXHBDOSN6YSXEOEORI3AGY5MKTRYFA3
X-Message-ID-Hash: JIXHBDOSN6YSXEOEORI3AGY5MKTRYFA3
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ron Bonica <rbonica@juniper.net>, Brian Rosen <br@brianrosen.net>, Robert Wilton <rwilton@cisco.com>, Rich Salz <rsalz@akamai.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Gendispatch] Re: Archival Dysfunction
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/0LNsO_bmskrrSd_Hf_JDwif8S68>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

My understanding is that the usual reason for "taking years" is that the 
process of reaching and confirming rough consensus takes time.  This has 
nothing to do with what tool we use to record that rough consensus.

Yours,

Joel

On 7/11/2024 12:50 PM, David Schinazi wrote:
> By GitHub I mainly meant "move the process minutiae to something that 
> doesn't take years to update". GitHub happens to be my favorite such 
> solution, but we can instead use tools from the previous century if we 
> think that's best for some reason :-)
> David
>
> On Wed, Jul 10, 2024 at 1:50 PM Stephen Farrell 
> <stephen.farrell@cs.tcd.ie> wrote:
>
>
>     Hiya,
>
>     On 10/07/2024 17:12, David Schinazi wrote:
>     > the day-to-day minutiae can move to GitHub
>
>     That'd be an escalation in githubbery. IIUC at the moment,
>     individual WGs decide to use github or not and if so, how.
>     Requiring a GH a/c to access/comment on process minutiae,
>     or being significantly disadvantaged though not having such
>     an a/c would be a significant enough change.
>
>     S.
>
>

v2.46.0 | Report a Bug | By Email | System Status