Re: Turning off Etherpad

Toerless Eckert <tte@cs.fau.de> Wed, 15 September 2021 20:23 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 8CDA63A0FDC for <wgchairs@ietfa.amsl.com>; Wed, 15 Sep 2021 13:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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 CoecPxpgesZP for <wgchairs@ietfa.amsl.com>; Wed, 15 Sep 2021 13:23:03 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C36683A0FD1 for <wgchairs@ietf.org>; Wed, 15 Sep 2021 13:23:02 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 141D4548053; Wed, 15 Sep 2021 22:22:57 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0A74F4E24F2; Wed, 15 Sep 2021 22:22:57 +0200 (CEST)
Date: Wed, 15 Sep 2021 22:22:57 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Working Chairs <wgchairs@ietf.org>
Subject: Re: Turning off Etherpad
Message-ID: <YUJWIUozz1JYeAG9@faui48e.informatik.uni-erlangen.de>
References: <192452e3-3858-3ecd-7d9b-c616251c67ac@nostrum.com> <9535DBFD-BCF1-44B1-A8B0-E278B581D771@gmail.com> <20210811012424.GC23297@faui48f.informatik.uni-erlangen.de> <24A3B72D-6BD2-4899-89DE-E53B33291FC0@mnot.net> <20210811161105.GD23297@faui48f.informatik.uni-erlangen.de> <73da4b89-9e91-b05d-9bb1-1fe97391eb7d@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <73da4b89-9e91-b05d-9bb1-1fe97391eb7d@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/lD5IpVY6plcNA7eln16x8uTCvno>
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: Wed, 15 Sep 2021 20:23:09 -0000

Thanks Robert. I think i understand some of the policy rasons,
as we discussed in the thread. We also ran into similar problems
with old mailin lists in discussion on the internet-history mailing
list.

I will stick to my suggestion for the successor system going forward:

  -> have a button to create a freezed copy of a page unde a new URL.
  -> with the option "public searchable: [Y/N]

The public searchable frozen cpy URL would be what would be archived
publically!

Cheers
    Toerless

On Wed, Sep 15, 2021 at 01:31:05PM -0500, Robert Sparks wrote:
> Toerless -
> 
> The tools team discussed the suggestions to try to archive what was in
> etherpad, and, with input from the leadership, decided not to do so. You'll
> see from the other notes that I just sent what should happen with any
> content that people feel should be preserved.
> 
> We are looking at ways to signal strongly to new users of notes.ietf.org
> that the content is not archival.
> 
> RjS
> 
> On 8/11/21 11:11 AM, Toerless Eckert wrote:
> > On Wed, Aug 11, 2021 at 11:27:41AM +1000, Mark Nottingham wrote:
> > > My understanding was always that etherpad was a best-effort, ephemeral service; i.e., there was no guarantee (implicit or explicit) of stability or availability. That's probably the right policy, given that there able to be edited by *anyone on the Internet*.
> > Yes. But my comments where not about the intent of etherpad,
> > but if/what we would want to do now to preserve history, even
> > if that was not a desire when we started using it.
> > 
> > The main question IMHO is whether we could publish the whole content
> > of etherpad or not. I would like to see that question answered. If
> > the answer is yes, then we can discuss if and/or how to do that.
> > 
> > If the answer is no, then i guss a tar file could still go into the
> > IETF vault, and later generations could figure out if/who might
> > be able to take a look at it.
> > 
> > > We might consider a somewhat more formal and explicit policy on service stability and availability (on a service-by-service basis), so that folks aren't surprised by this in the future. E.g., the W3C has:
> > >    https://www.w3.org/Consortium/Persistence
> > Right. My suggestion for codimd was exactly around that IMHO:
> > 
> > - declare CodiMD content to be public.
> > - automatically make older CodiMD content read-only
> > 
> > The conflict between this goal and the design of etherpad/codiMD is that
> > boh seem to be based on confidentiality by obscurity, e.g.: no
> > public search and/or list of pages...
> > 
> > Cheers
> >      Toerless
> > 
> > > Cheers,
> > > 
> > > 
> > > > On 11 Aug 2021, at 11:24 am, Toerless Eckert <tte@cs.fau.de> wrote:
> > > > 
> > > > So, what is he plan for archiving etherpad.ietf.org ?
> > > > Can/will the be made read-only/no new data ?
> > > > 
> > > > Or is all that content that may still have URLs in emails and other places
> > > > pointing to it deemed to be lost except for the subset of pages that
> > > > where converted into IETF meeting minuts by WG chairs ?
> > > > 
> > > > If all this content is meant to be lost because it is too difficult to
> > > > change to read-only, is this the same strategy for codimd ? Aka:
> > > > if you do not save it, it will be lost at some point in time ?
> > > > 
> > > > If converting to read-only is too difficult, maybe the whole tree
> > > > can just be put up for download as a tar file for any future researchers...
> > > > However, i am not sure if all the content is meant to be public, or if
> > > > we did assume some degree of possible confidentiality because of non-searchable
> > > > namespace.
> > > > 
> > > > Btw: I think it would be great if codimd would solve these issues:
> > > > You can only create new names under whatever.ietf.org/2021/<your-string-here>
> > > > and after 2 years the whole years directory tree turns read-only with
> > > > indexing/search...
> > > > 
> > > > Cheers
> > > >     Toeless
> > > > 
> > > > On Tue, Aug 10, 2021 at 06:05:34PM -0700, Fred Baker wrote:
> > > > > People use it in recording our minutes. Losing it would be unfortunate.
> > > > > 
> > > > > > On Aug 10, 2021, at 2:01 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> > > > > > 
> > > > > > Chairs -
> > > > > > 
> > > > > > We are making plans to turn down etherpad.ietf.org in a few weeks. Let me know of any concerns or need for delay.
> > > > > > 
> > > > > > RjS
> > > > > > 
> > > > -- 
> > > > ---
> > > > tte@cs.fau.de
> > > > 
> > > --
> > > Mark Nottingham   https://www.mnot.net/

-- 
---
tte@cs.fau.de