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

Yoav Nir <ynir.ietf@gmail.com> Wed, 23 January 2019 19:10 UTC

Return-Path: <ynir.ietf@gmail.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 CE7CA1277BB for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2019 11:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Y2lHfOKl-zJU for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2019 11:10:45 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 659F41286D9 for <ietf@ietf.org>; Wed, 23 Jan 2019 11:10:45 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id n190so568813wmd.0; Wed, 23 Jan 2019 11:10:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zV9JMwryg/m0vdBry1YaT+Tlyd1Bkb8Nf07C768+yyg=; b=BrHZ2AaRjQUI4DF2XrLOrhqTAExGl1ZL8dNwGBE3sYHkx/FckHiODsfL5Ay1lGHBC8 cekoOGlzLdShxGB4khrb+J3toRm2+/kyfYLIX14zzQI6XEw1AwaxD4vdvI3DioaIR3Wj MkDw0uo1B+v1N9CWGH0tAgbhSrXB8MKq+90CcYoCq25trFymzpjycZyaiEWErSwUtGkY cjfKRzXcHf4G3sOz0MtAUwQMGMQmht3EqvukBv/OCowz+d4zJRKDbWdFPprlPIB/ww/x zStztY5NVkPFghmgbPZjXc4fKjaVk/MRs+hF4nLiNz3ThIKvufXjNiqBcr38VKfh9Itu TcrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zV9JMwryg/m0vdBry1YaT+Tlyd1Bkb8Nf07C768+yyg=; b=KuqVOezI98pCw64gKlGYhHmoA8LGu/8vJotfznpoaM1Rt8Poh1Z09Z5v54BKvAJH4+ phQfI4cbrMEplrLDA4dJsxm6Dwr4CqA2PNphzAcf1GEfUeKWpGprdmQBX01nmxoT94bR eneCOulBwR83zj0FQWlXWCfIttFQcEQyCpDoRLzobSOU79sfQ88JTXIvCiolYcew2ae9 2pQcWpHgYf/2v0pq7aBLZUgRmdGykY+5SN9RRAbO++PdjB2PkSJurUuGXm48Rhn+16N9 LounWVjTAPqNECSOFXkDPZVtgik/6gjPczsxQdgC+D2zpWOMooq6e38aD4Sef59ApnZ0 reXQ==
X-Gm-Message-State: AJcUukc59omfqlkqWrhU0HJUUUazSzOP9b2SHmPrAnAzjepQv1qD+AAk 0/rnC8vbDiue6kY/xpUQkKk=
X-Google-Smtp-Source: ALg8bN7VESZ2QBHf05hlD5EWjEMYBrdgLxWdEsktN3cDcm58KYYyOdoyUbyuaJlSJxcGYLOrtuSEAg==
X-Received: by 2002:a1c:c181:: with SMTP id r123mr3927014wmf.8.1548270643885; Wed, 23 Jan 2019 11:10:43 -0800 (PST)
Received: from [192.168.1.12] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id a132sm68443590wmh.5.2019.01.23.11.10.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 11:10:41 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: sr.ht --- "sir hat" --- alternatives to Github
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <015601d4b303$5e7cd4a0$4001a8c0@gateway.2wire.net>
Date: Wed, 23 Jan 2019 21:10:38 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, "ietf@ietf.org" <ietf@ietf.org>, "wugh@ietf.org" <wugh@ietf.org>, Lloyd Wood <lloyd.wood@yahoo.co.uk>, Carsten Bormann <cabo@tzi.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D7CDE67-2DE3-4809-8DC3-1FCB6AD7D334@gmail.com>
References: <25946.1547751133@localhost> <2062850122.1176466.1548052316757@mail.yahoo.com> <7C2EF2A7-B267-43BB-9A07-56835D184E71@tzi.org> <1a427a5b-dba7-5d18-393a-c39e99e1fbd8@joelhalpern.com> <20190121152616.GE81907@kduck.mit.edu> <009b01d4b238$901cb460$4001a8c0@gateway.2wire.net> <CABcZeBPZnP6R1=PWM1sLbRv0qVP4D+p9z0KmWarvHLfU2x_p=A@mail.gmail.com> <015601d4b303$5e7cd4a0$4001a8c0@gateway.2wire.net>
To: tom petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sAK-hm9KgA17a4CeyK7iqYhIgAM>
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: Wed, 23 Jan 2019 19:10:49 -0000


> On 23 Jan 2019, at 12:07, tom petch <daedulus@btconnect.com> wrote:
>> 
>> Here we seem to be saying that answer is Github, all you have to do is
>> ensure that your way of working is amended to fit that answer.
> 
> No, I don't think that's accurate.
> 
> A number of us found that developing drafts by email was not working for
> us. We had experience with revision control systems in general and
> Github
> in particular, so tried Github, and found it works, refining from there.
> It's not perfect, but it was close enough to win the make/buy decision.
> 
> <tp>
> 
> Of course it works for you but think of the arithmetic. A mailing list
> has hundreds, may be a thousand or more, people on it of whom a handful,
> less than ten perhaps, are authoring or editing; the vast majority are
> just trying to keep up with the proposed changes and comment thereon.
> 
> What that small number of authors are now doing, at least on some of the
> lists I follow, is requiring everyone to go to Github to see the changes
> that they are proposing, perhaps discussing them there and finally
> coming back to the list with, more or less, a fait accompli. (I have
> seen an AD wanting to know what discussion there was on the list over an
> issue to which the answer is none - the discussion took place outside
> the IETF technology).
> 
> So I now see e-mails tellling me
> 
> "This has caused confusion in the past; see
> <https://github.com/httpwg/http-core/issues/103>. "
> 
> or
> 
>>> 
> https://github.com/wkumari/effect-encrypt/commit/974db6cb13faecbf5b1704c
> 1da580b320843d0b3
> 
> or
> 
> where changes were made, you can see them in the working copy at:
> https://github.com/netconf-wg/rfc5277bis/blob/master/draft-ietf-netconf-
> subscribed-notifications-11.txt
> 
> So this technology will be good for the "in-crowd" but potentially bad
> for peer review and wider participation..
> 
> Tom Petch

I’m no big fan of GitHub, but it is possible to “watch” a repository and get a web or email notification for every issue or conversation.  It’s not quite the same as having the conversation actually be over email, but it still gets you the conversation delivered in email.

Yoav