Re: Turning off Etherpad

Robert Sparks <rjsparks@nostrum.com> Wed, 15 September 2021 18:31 UTC

Return-Path: <rjsparks@nostrum.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 B21F73A0A1D for <wgchairs@ietfa.amsl.com>; Wed, 15 Sep 2021 11:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 w3GTVP9BtNjZ for <wgchairs@ietfa.amsl.com>; Wed, 15 Sep 2021 11:31:33 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 EE9BC3A0A40 for <wgchairs@ietf.org>; Wed, 15 Sep 2021 11:31:32 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 18FIVCYw074735 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 15 Sep 2021 13:31:12 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1631730672; bh=t5J0y/t9G1w+0ppRK5yuwI5szkjZejs6bgT6WyW71+w=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=vbOYWC9neWbuv8goaxXN1E4YK0tUKFzddar9J9iLoYfLpOacHL94twZ5a8QH7Hj1F mh3Ffgc+hu302rTbvEQ7Xk80XHdmdz3eVgyBR3XXS6MNOEJohVOr4TnbJMQKN9vQEK dFypPoKdrmBo7ZzTDTuYkhgJmHcfj06V3CqsIFBs=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
Subject: Re: Turning off Etherpad
To: Toerless Eckert <tte@cs.fau.de>
Cc: Working Chairs <wgchairs@ietf.org>
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>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <73da4b89-9e91-b05d-9bb1-1fe97391eb7d@nostrum.com>
Date: Wed, 15 Sep 2021 13:31:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <20210811161105.GD23297@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/vDO9XNeX3l5PH9oxqP9axd8Pr7U>
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 18:31:38 -0000

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/