Re: [Tools-discuss] Content at notes.ietf.org is not archival

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 16 September 2021 21:09 UTC

Return-Path: <brian.e.carpenter@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 3AB313A0975; Thu, 16 Sep 2021 14:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-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 d8AR90wYW-Ol; Thu, 16 Sep 2021 14:09:33 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 DFE1A3A0971; Thu, 16 Sep 2021 14:09:32 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id v2so4722950plp.8; Thu, 16 Sep 2021 14:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=kT8DpYsvh9kFCSjmcyndersnnasrttXbULRC0BNU8kQ=; b=WKE8GnGObBfEuKTHPCIGuxLS+c6HV08dr7Np+Sv3ZLZ4kqi2R4o8AbZCP+ruWRKt/s cdcrAulKSGxTFuTzjMzckVrJNMhk6avDmaGUGuwvAZs+YepZbaI7dZOymxUZ5B590SPW Jnju/oktQWwkSfy3kkT+dk3Bs92liNd9agif78hBEhnEKozpPzWc0yyzDoXUQ/uCcv1B f0HIaRib5lZ+6CVUSusfRJqiIyAGXWIAFKSxpag9JwrngkzXVylyNJEUcDMB3BoIJ5QJ jUgL/ZiZ3qiYw5u4UKLFLL0nBFKjPTWHv05AL06ksQPg5/WYpD4/JBrC4Qcg86TQR5t3 y+NQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kT8DpYsvh9kFCSjmcyndersnnasrttXbULRC0BNU8kQ=; b=W/uTREDkPcOw/8Km8ZhzgL7xqEkLvGoznm30ZdSxLY6/ooMyO8n1+G0/JvBAnIUAxY 7kTvaXLadBOx81pBmBSSma0m4dKau4eVvgwg9yfQT39cNIXS+7U5MWwbxIsFRNGahSy7 m4eYWni/0YI/irzMJ+K14B8o+Z8AhaZJk5OMzr0P3T6Prgh5CFH2OQqN4RUqWLhhdO+R vVnNmbeMeoHpFCdhRJJLwu0Zj6e5HF/vUglxg4wr1FqVKpYS9tQoV3PFQniD5vg3VJd9 fzZF2aYe3LwcD2Ra3ENmpfOBPhkI9wEmzZGeBmTk7AAsFFgB4yUm4QlI5bpW/8XG5W3i T37w==
X-Gm-Message-State: AOAM532J8Yzk6qbj2ddimVaMfyY8JTMJJ1TvagQjPhay7YatKswLjVhM C/y173G6CTsX/pdc04cObPTadct2UcPHtQ==
X-Google-Smtp-Source: ABdhPJxrydoUBeaclSwfZgyAIxmdPDyuD8kXKepbP+QmTfiisbX8sHjVv2tOWlfZilI6W2OtPUEdkw==
X-Received: by 2002:a17:902:e0c1:b0:13b:76f5:c3b4 with SMTP id e1-20020a170902e0c100b0013b76f5c3b4mr6318307pla.85.1631826570958; Thu, 16 Sep 2021 14:09:30 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id b13sm8668536pjk.35.2021.09.16.14.09.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Sep 2021 14:09:30 -0700 (PDT)
Subject: Re: [Tools-discuss] Content at notes.ietf.org is not archival
To: Michael Richardson <mcr+ietf@sandelman.ca>, Carsten Bormann <cabo@tzi.org>, Working Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, tools-discuss <tools-discuss@ietf.org>
References: <f2ea0c4f-9500-391d-b8d1-dcc3ac4a7b1c@nostrum.com> <CABcZeBOeKxO6KOWyC8WBqUxYyqAwqYdKOesBN+2nxtWAy17Mbg@mail.gmail.com> <ADDEE9BD-790B-4E44-982B-DAA15F50722A@tzi.org> <2B11D777-9D50-490F-B7C6-9DD769C789A6@mnot.net> <B6A2905B-6EB9-4A22-AD1A-10C4910408A2@tzi.org> <1534366.1631820151@dooku>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <93bdbb89-4aca-267c-6970-11f1c307003d@gmail.com>
Date: Fri, 17 Sep 2021 09:09:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <1534366.1631820151@dooku>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/U4CYI4ZdK4nfEiyRuvQFWo6SXkg>
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, 16 Sep 2021 21:09:38 -0000

On 17-Sep-21 07:22, Michael Richardson wrote:
> 
> Carsten Bormann <cabo@tzi.org> wrote:
>     >> On 16. Sep 2021, at 09:46, Mark Nottingham <mnot@mnot.net> wrote:
>     >> 
>     >> Or, just automatically delete notes 30 days after creation.
> 
>     > (Again, I don’t know whether this was a serious proposal. 
 I’ll treat
>     > is as such for the purpose of this message.)
> 
> Well, I'm serious.
> I think 30 days might be way too long.
> 
> WG and design team leaders should know to download minutes at the end of the
> session.  It's not hard.
> But, in order to train that, the contents needs to disappear within the 
day,
> and there will be some crying.   Some WG session minutes will go away.

One day is too short; back in the good old days, when most of us suffered
jet lag after each meeting, a week to capture the minutes and copy-edit
them was hardly enough. But I do agree, this is a major duty of WG chairs
or secretaries, and needs to be done promptly. 

I wouldn't call it notes.ietf.org. I'd call it temp.ietf.org. Or at least,
put everything in notes.ietf.org/temp/ and move it to notes.ietf.org/recycle/
after 30 days and then to /dev/null after another 30 days. Something like
that, anyway, depending on how it would integrate with HedgeDoc.

   Brian 
> 
>     > Collecting notes in our own service (as opposed to hackmd.io or Google
>     > docs) gives us more control.  Another benefit of having a common
>     > service is that, after a while, everybody knows how to use it and 
we
>     > can integrate it into other tools.
> 
> Agreed.
> 
>