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

Tero Kivinen <kivinen@iki.fi> Thu, 16 September 2021 21:17 UTC

Return-Path: <kivinen@iki.fi>
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 7A5193A0A3D; Thu, 16 Sep 2021 14:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=iki.fi
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 0cKmMGe-PxZB; Thu, 16 Sep 2021 14:17:32 -0700 (PDT)
Received: from lahtoruutu.iki.fi (lahtoruutu.iki.fi [185.185.170.37]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD5473A0A3A; Thu, 16 Sep 2021 14:17:31 -0700 (PDT)
Received: from fireball.acr.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) (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) (Authenticated sender: kivinen@iki.fi) by lahtoruutu.iki.fi (Postfix) with ESMTPSA id BD6651B00120; Fri, 17 Sep 2021 00:17:26 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1631827046; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=T6NsGZ/6SljC/XOKJ28sN43Y3D8miegpccMIWVE+S0w=; b=q+UvRadtrdIo3mhy/2QX2x7KRcbmp+Y9Imhed3Y68RC29jU/ZBBOENSXtUZK2wbrG3A9Nj nVMhEdddtJ1wR7Yz74BZkiHdMbpE9x6Lim8AwgvjsQGIQqpZZ8x70b+pfWVaYokPraTJFC U22e+CI5+oqoVSMS6B0TR1Y5CmOLMcXpczuqTmPnoV4dKvyDiMz6YUuvrexG12CR051lS5 TIj3JVUIfRle0wV262Cxj6VkTTNuUe/frWa4Cr2QyKm8KxPxa6uvbb4mtgx8xLIaBl4vzG QSzghHBRD1NUByo6ycSR46tppQEJAp7PRjzQJNXEBqFe7hQ5TkWOXChZAxi3aw==
Received: by fireball.acr.fi (Postfix, from userid 15204) id 207DE25C12B7; Fri, 17 Sep 2021 00:17:26 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID: <24899.46182.82529.393383@fireball.acr.fi>
Date: Fri, 17 Sep 2021 00:17:26 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Carsten Bormann <cabo@tzi.org>
Cc: 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
In-Reply-To: <B6A2905B-6EB9-4A22-AD1A-10C4910408A2@tzi.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>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 8 min
X-Total-Time: 8 min
ARC-Seal: i=1; s=lahtoruutu; d=iki.fi; t=1631827046; a=rsa-sha256; cv=none; b=MfrBb0S3xJo15/jA2tcQQwidIxQC+Cq6uLl6F2sJIcg6YGIpvFSoYLK9/lmnU8EfMXbz5r ikrF18ZHzNLPECnx3JTJXvYOwDVlcGuNbFJSID9oPWnZAwg5U3kifU/uGP+7hHdhwsdKFh W6lpq/l5HSgCeGwHfjDFxgkT5KCpBrKhUrEwnWLiUuS2lMiBQdFbrGfavAIdvhXsu8U9+z Hy4++V+TB33GNbZ7cVTURsq8gDw6AxsvaA5xkGppjqhybJC6xMxc6322qoz2KVIXj8oSTH 8xf8XgVYKh3Gar1czGaw2i30Nk42jzJZWIxaJ/uIZzLDAQuxbMzUoQOogfyWRg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1631827046; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=T6NsGZ/6SljC/XOKJ28sN43Y3D8miegpccMIWVE+S0w=; b=ZKXzmRYmDVqYVhhs+kQU/VRsgPgSi81WOl1U9tdluIPfnZk0V0FUc2mLnHAw1BWp75pmCc T+HMIYt+AT9d508hoE/kcMPXTpk8+F8A+BT2JKdAwybcHp2+pKCDYwG0FLMCWvkq9jw1+x 38bbwre4/1yMpN+I/ZrEy6sUAa+RsYY6zCNWr032nITD6pGb+bbqBx/LOnGQU48iK5peLU oxqGkZuRuc0EYxQlLPt5mBQG/ljM59mhTSTvTv/zM4Y2EhzD55vBoT7RXLwAjjNkzfLGog MSjcrAz9OFzzoAoo5fBhVYsOS591iQMW1Fg41z9Wiu3d6IY1gphR2ByRrs9Vfw==
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen@iki.fi smtp.mailfrom=kivinen@iki.fi
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/iNnw33-m9rx4VBmFup5THX9pvzk>
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:17:41 -0000

Carsten Bormann writes:
> 
> > 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.)

I also think this automatic delete after 30 days would be good
improvement. Or actually I would say 30 days after last edit (and if
the last editor has datatracker account we could send email notifying
that the note will expire in 7 days or similar). 

In addition that we do need an easy way to transfer data from the
notes.ietf.org to the datatracker. I.e., a way I can go to the
datatracker for my WG, and say this note in the notes.ietf.org should
be imported to the datatracker with this title (i.e., interm meeting
notes, or IETF xxx minutes or whatever). 

> Or, don’t offer the service at all?
> (Probably better than deleting it 30 days after creation (!).)
> 
> Most of the people who have done work in the IETF know about the
> value of accessing random traces of that work from the past. After a
> couple of decades, we mostly got rid of the 6-month ideology around
> Internet-Drafts; I wouldn’t want to repeat that painful experience.
> 
> 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.
> 
> Crippling such a service because we can’t figure out how to keep up
> some ideology strikes me as an expression of contempt for the work
> of the IETF’s contributors. You don’t have to feel the same way, but
> it should be well understood that this is the signal that is being
> sent.

The problem with notes.ietf.org is not that we can't keep the data,
itis that we can't find the data. I have no idea what was the etherpad
url for my session 4 years ago. I can most likely find it from the
chair slides if I happened to copy it there, but otherwise I would
need to go and find it from the somewhere else.

If we force people to move pages out from notes.ietf.org after the
session finishes, they are archived in the location where we can
actually find them. They can be stored to the datatracker as minutes
etc, or they can be moved to the working group wiki or similar.

Storing data is useless if people can't find it, and
etherpad/notes.ietf.org are both in that category.
-- 
kivinen@iki.fi