Re: [Ietf-and-github] Alvaro Retana's Discuss on draft-ietf-git-using-github-05: (with DISCUSS and COMMENT)

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 March 2020 19:16 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 D23DD3A105F; Thu, 12 Mar 2020 12:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 e1uKS3bWOd8k; Thu, 12 Mar 2020 12:16:32 -0700 (PDT)
Received: from mail-pg1-x542.google.com (mail-pg1-x542.google.com [IPv6:2607:f8b0:4864:20::542]) (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 BA0763A1063; Thu, 12 Mar 2020 12:16:31 -0700 (PDT)
Received: by mail-pg1-x542.google.com with SMTP id u12so3526525pgb.10; Thu, 12 Mar 2020 12:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=gm4ZqWPqcwFnzJrbi8sgYRQxopldHWySVGiZaBcYZWw=; b=n68tO7UFH5A+pT3jIpgkrW3hQpBzeD/ElFJOuWiPMfRRIAJ8Bv79F/zQyskppAOaeK ag0vVbKkQUZ6E9Q567QdIpTu1AP4TdNLbYwdTVkA71teO892ktBq7YEvzS+3oayl1lbN nICskNSNCgcdapeTV9/+FS+cy1aiKSaA1H20leJTjd8t928/9ZkUiDA1Fd6uuuDPzXCK sKYnY7zncqOaVcHlQNxZAYpdu5oGeOgN0U0IWn/3j5zCbur0eNeTrFO6ulM7uWaGM7ir +ez/a9LxGm5Bzm4DINyDjuNwEg7R0wHX0TBxBloPvTViWCvAg8vPx/oeV/vhpWJIc5EB 1R9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gm4ZqWPqcwFnzJrbi8sgYRQxopldHWySVGiZaBcYZWw=; b=KzMnagMLDYx2EVs8M0pso0iRdJHilk6yGB4xtuD2u0LfrTrP3I3JWZq4g6D9Aozs/3 hZYDQGbRh5l9V3kmoCVeui7T+y8N89Ki5SRU7l5GpCkfBirKOFrntkV8XOEZiA5hDTJ0 S3Oamvmww2ztVDlpdoQ5Orqp3YgvLZPPjSRQfIhCAugI3k0GdiMmW/3LvMcpnb1Ajoph PuNeqo6NNOHr3Jy8dl7cuWogb7juHUmEbhiO1aUzzr4z9YnuzzPRRgGfMlLc32TI7Cbd 3bj9rm9R1ab/LH5dflccyxEU/P9y7h035VZX3Z3mtpZvfOaVdejUlr8mtHoVW9nLy4Zc RwXQ==
X-Gm-Message-State: ANhLgQ366789/mRlCEjeRFurEqmnEO4ZyEa0U8WlUi8Nz9Rwqav3lgPs VFLrds1dmW0KQUBAMCtQcHw=
X-Google-Smtp-Source: ADFU+vswWSfHRn8oPzdswtnhuYX8eHnyonEgqTyzoSL95R4R66QIaKB+Kx8v+6ZqkIRucMsRegfNfA==
X-Received: by 2002:a65:6147:: with SMTP id o7mr9512768pgv.442.1584040591090; Thu, 12 Mar 2020 12:16:31 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id w9sm2186352pfd.94.2020.03.12.12.16.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Mar 2020 12:16:30 -0700 (PDT)
To: Alissa Cooper <alissa@cooperw.in>, Alvaro Retana <aretana.ietf@gmail.com>
Cc: IESG <iesg@ietf.org>, git-chairs@ietf.org, ietf-and-github@ietf.org, draft-ietf-git-using-github@ietf.org, Christopher Wood <caw@heapingbits.net>
References: <158395281137.1671.933778421064897517@ietfa.amsl.com> <03958aff-0e58-1fc6-8d50-ca38f8221ce6@gmail.com> <CAMMESszjUH86oJaX9QH_tU58DZX9PhSHbmUq=4anE9-iRO0tNg@mail.gmail.com> <B806BAE2-4B47-4BEF-AA3D-169B6B4A978C@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b554e854-585c-5709-0f5b-9c0d0a3b83e5@gmail.com>
Date: Fri, 13 Mar 2020 08:16:26 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <B806BAE2-4B47-4BEF-AA3D-169B6B4A978C@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/QIdfzYb4RFyMVPAdKowKb8uAyv8>
Subject: Re: [Ietf-and-github] Alvaro Retana's Discuss on draft-ietf-git-using-github-05: (with DISCUSS and COMMENT)
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: Thu, 12 Mar 2020 19:16:34 -0000

To be precise, my review said:

> Is this draft intended to become part of BCP25? I think it would be
> useful for the IESG to clarify this rather than leave it to the RFC Editor.

I intentionally didn't express an opinion.

   Brian
On 13-Mar-20 01:40, Alissa Cooper wrote:
> I am indifferent about this being part of BCP 25. Brian suggested it so I added the note. I’m happy to remove the note if necessary. 
> 
> Alissa
> 
> 
>> On Mar 11, 2020, at 4:39 PM, Alvaro Retana <aretana.ietf@gmail.com> wrote:
>>
>> On March 11, 2020 at 3:32:58 PM, Brian E Carpenter wrote:
>>
>>
>> Brian:
>>
>> Hi!
>>
>>
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>>
>>>> This is a process DISCUSS. I don't believe the status of this document as a
>>>> BCP belonging to BCP 25 was discussed in the WG or with the IETF community.
>>>>
>>>> The Charter for the git WG only explicitly mentions BCP 9:
>>>>
>>>> The documents produced by this group will not alter the Internet Standards
>>>> Process (BCP 9). They will describe how to work within it. Whether working
>>>> groups choose to use GitHub or the documented policies to support their
>>>> work will remain entirely at their discretion.
>>>>
>>>> However, including this document as a part of BCP 25 (IETF Working Group
>>>> Guidelines and Procedures) results in the interpretation that it represents
>>>> consensus on how WGs should proceed -- and not that the decision "to use
>>>> GitHub or the documented policies...[is]...entirely at their discretion.."
>>>
>>> Would a sentence to that effect in the Abstract and Introduction help?
>>
>> It wouldn't hurt, but it also doesn't help with my issue: having this
>> document be part of BCP 25.
>>
>>
>>
>> ....
>>>> IOW, both (1) the process of reaching the conclusion that this document
>>>> belongs in BCP 25, and (2) the concept that this document would be part of
>>>> BCP 25, are the subject of my DISCUSS. I would like for the IESG to discuss
>>>> this topic.
>>>
>>> Have things changed? In the old days this question (which BCP number?) was
>>> typically left to the discretion of the RFC Editor, possibly with a bit of
>>> discussion with the AD. I certainly don't object to community discussion, of
>>> course (and we did do that in the case of BCP 101 recently).
>>
>> No, I don't think things have changed.  In this case, the AD added a
>> note to the RFC Editor requesting them to "append this document to BCP
>> 25 at the time of publication."
>>
>> https://datatracker.ietf.org/doc/draft-ietf-git-using-github/writeup/
>>
>>
>> However, I believe that BCP 25 is a special case because it applies
>> directly to WG operation.  The intention of adding documents to it
>> should (at least) be clear and some discussion should exist.
>>
>>
>> Thanks!
>>
>> Alvaro.
>>
> 
> .
>