Re: sr.ht --- "sir hat" --- alternatives to Github

"John Levine" <johnl@taugh.com> Tue, 22 January 2019 19:51 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C99BD131007 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2019 11:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 header.b=ko9ZqY6I; dkim=pass (1536-bit key) header.d=taugh.com header.b=kQ6zcwi0
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 mnD31RN7z5_T for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2019 11:51:31 -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 EB3B2128AFB for <ietf@ietf.org>; Tue, 22 Jan 2019 11:51:30 -0800 (PST)
Received: (qmail 30942 invoked from network); 22 Jan 2019 19:51:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=78dc.5c477441.k1901; bh=5M7MZ0xYw4dHLUDOffo/BY7eCrBQqsJKO7GWrDu0/G0=; b=ko9ZqY6IWuQvel+p6HsQGO6gnjCifvH59/LOuEzq83OQNnsE2LKCebiZPronWbUVKNLOJVGRTTfdrkxj5zAEKDiazRMfFh579mCAWxD8Twq/2zE9Cp5F2KJn7HKcBwO/PFdCkEahgOgTEf5p1uadu45PjDebK81QxDvtZG30oMIAxJ3G/szkrTTSLDmFzeLTv4ZEuyowv4ELU0b/LVZg3yVgyhJFg0rR4IAIuMXa3EN6COZECWUDtmbw8uvkNODY
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=78dc.5c477441.k1901; bh=5M7MZ0xYw4dHLUDOffo/BY7eCrBQqsJKO7GWrDu0/G0=; b=kQ6zcwi0S8Epe04JfCLg1wqMABMyzyA7Tm43ixdx0WqJWRRYsy3LrlYK426QO1EWeLn1/cNSfxc4KmT7d2v+LUw71gdjNT3IkraRHywJO3PcawXAnbrCpJWmv69RJpOOr9jpzXKY5QXxr8ZoPf5bcxpSOtSudc/4Ype3X+rppwVG36Bd+kuSPwvwlZFalx+8Ga7QGasrDBu57Loklmn0KGBehUBWVlfbaJ84zaF4x6WbU6Lwez+sOUEWyqymPkS+
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 22 Jan 2019 19:51:28 -0000
Received: by ary.qy (Postfix, from userid 501) id 8873C200D0DE76; Tue, 22 Jan 2019 14:51:28 -0500 (EST)
Date: Tue, 22 Jan 2019 14:51:28 -0500
Message-Id: <20190122195128.8873C200D0DE76@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: sr.ht --- "sir hat" --- alternatives to Github
In-Reply-To: <20190122172530.GB4303@localhost>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mEM01PV7d0WwiCP1iWbOKew3rrI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2019 19:51:33 -0000

In article <20190122172530.GB4303@localhost> you write:
>My concern is that IETF business conducted off IETF lists might be
>problematic.  We have an answer to that: confirm consensus on IETF
>mailing lists.  I'm OK with that.  But I would prefer to have a better
>e-mail interface from GitHub/GitLab/BitBucket/etc.

It's more than that.  IETF business is supposed to be all subject to
the Note Well which affects patents and other issues. We have a
reasonably well agreed way to put the Note Well on the front page of
github repositories doing IETF work.

If we have random subgroups doing work on other random platforms with
random notices or non-notices, it potentially creates complex messes
that will be hard to clean up.

R's,
John