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

Alissa Cooper <alissa@cooperw.in> Thu, 12 March 2020 12:40 UTC

Return-Path: <alissa@cooperw.in>
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 0344D3A0FF1; Thu, 12 Mar 2020 05:40:29 -0700 (PDT)
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 (2048-bit key) header.d=cooperw.in header.b=XrT8yV7q; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=tmn0Kerz
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 LFqvp69RGiQu; Thu, 12 Mar 2020 05:40:26 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4028F3A0FE4; Thu, 12 Mar 2020 05:40:25 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 388AC8B9; Thu, 12 Mar 2020 08:40:24 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 12 Mar 2020 08:40:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=G 9LzgTf6ZoRHeIgaiSz1jL+XoMSTfKJiLnitBjjqBgg=; b=XrT8yV7qLSjqyhK0d PLVdhsoxsgWQ4o6drUg33gy+v3XnFWne/Z2o3COVFj3sbL/Pl5YOOiYDQkFQGMOe Z0uUN0m32gV52+VNyXJi2l4gKTZBOJDjTir+YipPpES51f9/a/dKMv5bLsBDC9Ak /lmhHsRX2ctHA3htlmgpwttvxZrbmsto0lCrtwAR1w7eqLNOhIBfgWOolGdUQp28 yquGDAABWebEgpivSGS0u34jzC5s4GhUBAQTscmZTsan2ScFiUCptq5R8Pru/0BG 1SiRo8/1mkbfItsKoJPTVY2QOUSg+dIl907Tl6h40+/e+MqkZmo4H07A5ZJ3aY/D Z/yuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=G9LzgTf6ZoRHeIgaiSz1jL+XoMSTfKJiLnitBjjqB gg=; b=tmn0KerzhVjnJvOVRFjj+2ZDysZBC07+1psoiF8KRWrPFmF48qENT+go8 u0M+XQFzOf8QpjHASBBfAgkyZvQtxwmW/JJPY5mHEMNCnHAAqnHZFI6hEbD6rLbh MhhyjYfdymrgn0hLrLXB/whAKsq2P1zuVJ1pmalCbfQKZP8zdYnJ1gMvxZvHIUFw 08Tj0uquiVx58oGtlkF0fUwE7pj6AZeEsvlNYH9YBFjWOTMxOEWH7T6MIa/aMGq2 7TYriZr2pb8tPF2lfRW5T+fu4NXn0v/hR8TYieyJFRpo36SJy3rm8oulB4ZYeRg5 MNsr+auAL/QAiIf0ceHMljnl+9g1A==
X-ME-Sender: <xms:ty1qXk6UWlHJ4Ku_bRBfoYA0i3yjOqaWrl7G1GNXfrh2rFjVT89ZKw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvhedggeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrkeeinecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegtoh hophgvrhifrdhinh
X-ME-Proxy: <xmx:ty1qXut1d2sNnZrXOhdFtFjCXAarENKO4F4MLQBw63J6clmIqzEbrw> <xmx:ty1qXpyf2yeCOqV3DVjL2ldYmaR7HymsP3syTJiCAVp7yAgh0hucSA> <xmx:ty1qXvySRacBTtTUuJ7UV1FBXvpwbT0EJFFKnUvYlKZMt0wOWgVQag> <xmx:ty1qXsdTf3e6pD9lWf7erjVQRJ-PEPZB8FzVkJRiLxCnu6KeuxCtBg>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.86]) by mail.messagingengine.com (Postfix) with ESMTPA id 421CC3280063; Thu, 12 Mar 2020 08:40:23 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAMMESszjUH86oJaX9QH_tU58DZX9PhSHbmUq=4anE9-iRO0tNg@mail.gmail.com>
Date: Thu, 12 Mar 2020 08:40:23 -0400
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B806BAE2-4B47-4BEF-AA3D-169B6B4A978C@cooperw.in>
References: <158395281137.1671.933778421064897517@ietfa.amsl.com> <03958aff-0e58-1fc6-8d50-ca38f8221ce6@gmail.com> <CAMMESszjUH86oJaX9QH_tU58DZX9PhSHbmUq=4anE9-iRO0tNg@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/UV-VYCdM1f6MSbvWWiEskmFJ6DI>
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 12:40:29 -0000

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.
>