IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Fwd: Re: [Tools-discuss] Etherpad no longer on standard port

"John R. Levine" <johnl@iecc.com> Fri, 06 March 2020 22:47 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE9863A0CBD for <tools-development@ietfa.amsl.com>; Fri, 6 Mar 2020 14:47:02 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.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 6YDIdUJ-JtWV for <tools-development@ietfa.amsl.com>; Fri, 6 Mar 2020 14:47:00 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C1093A0CB4 for <tools-development@ietf.org>; Fri, 6 Mar 2020 14:47:00 -0800 (PST)
Received: (qmail 95948 invoked from network); 6 Mar 2020 22:46:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=176c4.5e62d2e3.k2003; i=johnl-iecc.com@submit.iecc.com; bh=0oAmAQvnq31PBGNMRo5cWO0Q4E6vszJcJKdaSUewjZU=; b=a+GVEBoJEp2TZIg7wEbuIJvHlfL9yo4KkK6FuJH+PZ9XeQ/uW5SN+levsAIDtVn2SYT6C1stB865NdFI3wLSGgwGq+xGbRICMidoILczMgizlNiIq+vRRpIMBRm+yKV8j97+asL1pK8JFml1YN4oR5DzaAzBo4M/9SiNCS0XmHtczX5VQe9JLhSuisOmvwfXByWyn/lztdOov5hP4OMDAkXvKm5dz09ZZRG2Cwjurgay/54ISi51I0R7ZvK3q2d/
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 06 Mar 2020 22:46:59 -0000
Date: Fri, 06 Mar 2020 17:46:58 -0500
Message-ID: <alpine.OSX.2.22.407.2003061744020.23366@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Robert Sparks <rjsparks@nostrum.com>, IETF Tools Development <tools-development@ietf.org>
Cc: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1d345839-14a3-af07-bd8b-58df5528d328@nostrum.com>
References: <D17E43EE-27AB-4471-9E8A-420EECD4BB79@tzi.org> <1d345839-14a3-af07-bd8b-58df5528d328@nostrum.com>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/0KZZoJ9q0-rB9FV22nhbiXhe2vE>
Subject: Re: [TOOLS-DEVELOPMENT] Fwd: Re: [Tools-discuss] Etherpad no longer on standard port
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 22:47:03 -0000

>> I repeat my ceterum censeo that hackmd/CodiMD is a viable candidate, but

> This looks like it would be easy to deploy to me and it passes a first 
> sniff-test at keeping it going.
>
> I was able to do a one-click deploy in heroku, and tweaking options to make 
> it be fairly wide open was simple.
>
> By default, it requires some simple registration (it allows on-instance 
> registration with an email address that it doesn't verify). In the long run, 
> it could be made to require datatracker credentials with what I currently 
> think isn't a _lot_ of work (depending on the current quality of the django 
> libraries to facilitate becoming an OAUTH2 provider).

HackMD is a commercial product from hackmd.io.  That doesn't make it 
impossible, and the price doesn't look ridiculous, but it does mean that 
it'd needs a a budget from the LLC if we want to use it beyond testing.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email