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

Qin Wu <bill.wu@huawei.com> Fri, 17 September 2021 04:16 UTC

Return-Path: <bill.wu@huawei.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 AFC903A1C75; Thu, 16 Sep 2021 21:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 xLZ47IjcCMpX; Thu, 16 Sep 2021 21:16:00 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 971403A1C70; Thu, 16 Sep 2021 21:16:00 -0700 (PDT)
Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H9gYM4JkKz67bGn; Fri, 17 Sep 2021 12:13:27 +0800 (CST)
Received: from dggeml704-chm.china.huawei.com (10.3.17.142) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.8; Fri, 17 Sep 2021 06:15:56 +0200
Received: from dggeml753-chm.china.huawei.com (10.1.199.152) by dggeml704-chm.china.huawei.com (10.3.17.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Fri, 17 Sep 2021 12:15:55 +0800
Received: from dggeml753-chm.china.huawei.com ([10.1.199.152]) by dggeml753-chm.china.huawei.com ([10.1.199.152]) with mapi id 15.01.2308.008; Fri, 17 Sep 2021 12:15:55 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, 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>
Subject: RE: [Tools-discuss] Content at notes.ietf.org is not archival
Thread-Topic: [Tools-discuss] Content at notes.ietf.org is not archival
Thread-Index: AdereobGCmUYmZlNTriGcv6ttZe/1g==
Date: Fri, 17 Sep 2021 04:15:55 +0000
Message-ID: <424dea8d0f064391b74bbf568fc99758@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.123.117]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/KAUIizbi53NW9AiTo21B8wfDo2g>
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: Fri, 17 Sep 2021 04:16:06 -0000

-----邮件原件-----
发件人: WGChairs [mailto:wgchairs-bounces@ietf.org] 代表 Brian E Carpenter
发送时间: 2021年9月17日 6:16
收件人: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>; 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>
主题: Re: [Tools-discuss] Content at notes.ietf.org is not archival

On 17-Sep-21 09:14, Henk Birkholz wrote:
> Minutes are not the only notes taken at notes.ietf.org. I would stop 
> using it, if things would simply disappear, obviously. How is this a 
> good idea?

Henk, I may well be old-fashioned, but when I want something to be kept, I keep it: save it on my disk, and make sure it's in a directory that gets backed up routinely.

Anybody who used geocities.com knows why.

(I'm biased on this question. In about 1993 I tried to persuade Tim Berners-Lee to make an expiry date obligatory for every HTML page.
I still think he was wrong to refuse.)

[Qin] Create date is more useful than expiry date when you read some blog and trace the history of idea in the HTML page. :-)

It's also important to specify this from the start. We probably don't want rough notes to become part of the public record of standards activities, and subject to subpoena.

    Brian
> 
> 
> On 16.09.21 23:09, Brian E Carpenter wrote:
>> 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.
>>>
>>>
>>