Re: [Ietf-and-github] I-D Action: draft-ietf-git-using-github-01.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 22 October 2019 04:36 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5B8120058 for <ietf-and-github@ietfa.amsl.com>; Mon, 21 Oct 2019 21:36:19 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 C9jJyKY2MWBE for <ietf-and-github@ietfa.amsl.com>; Mon, 21 Oct 2019 21:36:17 -0700 (PDT)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 02C1012004F for <ietf-and-github@ietf.org>; Mon, 21 Oct 2019 21:36:17 -0700 (PDT)
Received: by mail-pg1-x52d.google.com with SMTP id 23so9158175pgk.3 for <ietf-and-github@ietf.org>; Mon, 21 Oct 2019 21:36:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=0kOyGw6XJaGhlH8S4J+9iMFYWn7GQ0vcvrn8C9vdjEI=; b=Ef0hefHJOKM6eanwkG2d+3W5scejIBSXWj0GAzHcBHLjVpbXNdhG88/A2UKDh71rJo Lb7L8I6ZuS8yYzNzg8M8SNgWjgEIP+uD7fAhBc8Azw/ufu7Ybtn7kl5U2BjUdFxvA/LU qP4745l0fkMUEWCecmeypVp+yBCcurucgGESJN3Sk2KGu5CnLm/zdAvqUT84aKLoRLtK ralLgkwedrD9xL0ikUYMDrdc8zz+EPgaxwlVauOTDMmoOU11lhRnecJJyhjcWZ8GG34i pv3+Vc+rI71TjpqIO3UO/PpkfVdj2cunQwH/v3C1k4Fb2mEmehZbJ7O6fayA5+cXZhYc 37Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0kOyGw6XJaGhlH8S4J+9iMFYWn7GQ0vcvrn8C9vdjEI=; b=FonORF0UscvM9hq9uZAXZN+LBOIl3Sq7QHR7fImd40sAh4jJnM+jgt8hPPlpW6z+PD CCAYSQYSXWDOeBEf9CYF3qw/1FC0+5RQnXFqFq3qF2GR+M0BlWiBMyayDw6inCa4RUlq 1U2/jxUWH8c6uByFsjLwfNYiQKzCURH9NfpuPbZHWf4wBKzaYTCBzLCQMQtYuo+1REg9 NeA+25s2U837Inh51WphykRw0BuQkJA98JhnZMeJyiI2bpN0JQeuCe3j40zJRD5+JR3V 2DWSxbWLNWPr5Gup8yfSxxZEfM6HsimMW4+WOMh5VgurWeXeNSQGgeApWhXRtXGxwOGt 5Vaw==
X-Gm-Message-State: APjAAAUY50i6OpCU6nRWa17P8sOqVA2i7NeVe5WTQ8bOW3NtM1lfRnA7 GxpLOyRXKLXCDc5XCy6+i9N59BGdp3g=
X-Google-Smtp-Source: APXvYqxuQtxS1cDUmxFvmDV4whSuBywpWfc0njNDist7LMbndjMyUeLhA+hG03W6lU8RO9W7lKJjkw==
X-Received: by 2002:a17:90a:1b2a:: with SMTP id q39mr1945385pjq.119.1571717241940; Mon, 21 Oct 2019 21:07:21 -0700 (PDT)
Received: from [192.168.178.30] (233.148.69.111.dynamic.snap.net.nz. [111.69.148.233]) by smtp.gmail.com with ESMTPSA id o123sm823416pfg.161.2019.10.21.21.07.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Oct 2019 21:07:20 -0700 (PDT)
To: Martin Thomson <mt@lowentropy.net>, ietf-and-github@ietf.org
References: <157076296718.20514.13633614592241624527@ietfa.amsl.com> <4984f4a9-384d-c0f4-d709-3aa620d2c1b8@gmail.com> <448e593b-c717-4c30-b230-d98e54cfc860@www.fastmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <fbbfddbc-0b25-fed4-e849-fc431470c1b7@gmail.com>
Date: Tue, 22 Oct 2019 17:07:19 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <448e593b-c717-4c30-b230-d98e54cfc860@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/yFqVJpy-G5wRXJWRlibANoH4qYc>
Subject: Re: [Ietf-and-github] I-D Action: draft-ietf-git-using-github-01.txt
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2019 04:36:19 -0000

Looks good, thanks.

Regards
   Brian

On 22-Oct-19 11:59, Martin Thomson wrote:
> On Sun, Oct 13, 2019, at 06:37, Brian E Carpenter wrote:
>> Secondly, I think something like the following is needed, possibly in 
>> section 10 'GitHub Limitations':
>>
>> For practical reasons, some participants might access GitHub only via 
>> its web interface. The above recommendations still allow them to 
>> participate in discussions. If any participants have no access to 
>> GitHub for some reason, the Working Group chairs MUST ensure that their 
>> comments are taken into account.
> 
> Hi Brian,
> 
> There was already text in Section 7 that addressed this point.  I've sharpened it (major additions highlighted), as follows:
> 
> ~~~
> [...]  Participants who wish to limit this time commitment might
> follow GitHub activity selectively, either by following only specific issues or
> by occasionally reviewing the state of the document.  **Other participants might
> not use GitHub at all.**  Chairs are reminded that assessing consensus based on
> GitHub content alone cannot be assumed to reach all interested participants.
> 
> **Chairs MUST consider input from all discussion venues when assessing consensus
> including GitHub, mailing lists, and in-person meetings.  Each venue has
> different selection biases that might need to be considered.**
> 
> A Working Group chair MUST consult the Working Group mailing list for any issue
> that is potentially contentious. [...]
> ~~~
> 
> I've bundled this with the suggested unpacking of "session".
> 
> https://github.com/ietf-gitwg/using-github/pull/24
>