Re: [Ietf-and-github] Alvaro Retana's Discuss on draft-ietf-git-using-github-05: (with DISCUSS and COMMENT)
Alissa Cooper <alissa@cooperw.in> Fri, 13 March 2020 13:52 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 48D193A0820
for <ietf-and-github@ietfa.amsl.com>; Fri, 13 Mar 2020 06:52:26 -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=G7H+vZX4;
dkim=pass (2048-bit key)
header.d=messagingengine.com header.b=2sqNkpGd
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 rVWyFrksGUR8 for <ietf-and-github@ietfa.amsl.com>;
Fri, 13 Mar 2020 06:52:24 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com
[64.147.123.25])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 89D023A081C
for <ietf-and-github@ietf.org>; Fri, 13 Mar 2020 06:52:24 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
by mailout.west.internal (Postfix) with ESMTP id D120A74A
for <ietf-and-github@ietf.org>; Fri, 13 Mar 2020 09:52:23 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
by compute4.internal (MEProxy); Fri, 13 Mar 2020 09:52:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=
from:content-type:content-transfer-encoding:mime-version:subject
:date:references:to:in-reply-to:message-id; s=fm2; bh=G8dQg8YdWy
g4C2d0PGOWlVZyrK62oWV+FC5uQa0Q+wI=; b=G7H+vZX4BmBHDBPlCZT/gnJ2XY
bWltGDPsHLCsIHK23vifhtQVn/6yVfPMe7+CHLJIWhBZmBvefvF1Vr7k2nBhgcQN
iyXQeramw4xgKusNbbe2+eA+2VJNRUGNq46mrEG4aisAqsbPJb5zTKxy30JuRFg4
PGXtBd4N93z2/iiXCZVgiO2nIMvOg/3BDcd5JxWkB+wDl2O8NSDFZTmLTO49+mHd
zzp6wVXpsd7ZcfaCTPtvJLaroPRivSQiPQzMBM60hbC9gQnCkiW2og7tO/CCAqyq
j+CXHFXA1+wKKbHhfOEYjr+LlVw0KeRvSLZmZ+n/kOmqIxm4K2zhsv5He0cA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=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=G8dQg8YdWyg4C2d0PGOWlVZyrK62oWV+FC5uQa0Q+
wI=; b=2sqNkpGdp+ONRB7pPzgS7b7EIbWewmMHBNyih1WQz8/PNnOkdyarHymqw
Od5hg9bjwXrqS7it24DkDmmyopunXNdTDU5R9QKB0M04lcWjncX6EsXFnqrP0e+Y
A1XJTHPXiQPquihmSpk7K8wNe3QS/mEb3cN5gplh6bY3wyje4JvdaSrbYMys1Vdp
qPOiASBBUbrBaQGi67xeEPoYADgfsTPR/LUKCmK62D0RcPUKIReLXKdiSK8YpW8x
mA+sppQQzfXLJ2N+WXvJppWMATrq98kn+7AzesU0vP6rGL6GIeyOP0iSTWPbBarZ
mYgDuHv2bR1imAV5S1HLd1AxW4Pzw==
X-ME-Sender: <xms:F5BrXmP6yaOG4QhyZjK1AniiUEA__vAz_BW8nCOjVQmQt4-dLOfxig>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvjedgheekucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
uceurghilhhouhhtmecufedttdenucenucfjughrpefhtgfgggfuffhfvfgjkffosehtqh
hmtdhhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhsshgrsegt
ohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudejfe
drfeekrdduudejrdekieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr
ihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhn
X-ME-Proxy: <xmx:F5BrXmiKP6otCZJjkNuqu7JJP5hu7dYvSUysuQjDVqrHr3oOHyfy8A>
<xmx:F5BrXjlFE9PNSsha2qgmSQpvM00WBdyzGgu93xG_0qEannjdpGCzKg>
<xmx:F5BrXijol-FKAFx82tWf698XF0EJC2b6OrnIXZeECB3INpsjqqoKng>
<xmx:F5BrXqlb2E_0iYxhKYT4jeoqkbuYswadjF2woC8DmgRaZNK1P2R5cA>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.86])
by mail.messagingengine.com (Postfix) with ESMTPA id 339063061363
for <ietf-and-github@ietf.org>; Fri, 13 Mar 2020 09:52:23 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 13 Mar 2020 09:52:24 -0400
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>
<3B60E587-C8A5-4A2C-8D8F-33FAD96E21CE@cooperw.in>
To: ietf-and-github@ietf.org
In-Reply-To: <3B60E587-C8A5-4A2C-8D8F-33FAD96E21CE@cooperw.in>
Message-Id: <F18FC54C-01CC-4340-AF01-F0350528FD4E@cooperw.in>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/j7d9FXI1CXhXNMn4CFF-MKuN410>
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: Fri, 13 Mar 2020 13:52:33 -0000
Given the message from Chris about informational vs. BCP, I will wait on this. Alissa > On Mar 12, 2020, at 10:16 AM, Alissa Cooper <alissa@cooperw.in> wrote: > > WG: > > Based on discussion with Alvaro on the IESG telechat today, I said I would take out the RFC Editor note about BCP 25 tomorrow if no one from the WG objects. This document will then get its own BCP number when it is published. > > Alissa > > >> On Mar 12, 2020, at 8:40 AM, Alissa Cooper <alissa@cooperw.in> 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. >>> >> >> _______________________________________________ >> Ietf-and-github mailing list >> Ietf-and-github@ietf.org >> https://www.ietf.org/mailman/listinfo/ietf-and-github >
- [Ietf-and-github] Alvaro Retana's Discuss on draf… Alvaro Retana via Datatracker
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Brian E Carpenter
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alvaro Retana
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Martin Thomson
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alvaro Retana
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alissa Cooper
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alissa Cooper
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alexandre Petrescu
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Stewart Bryant
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alexandre Petrescu
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Erik Kline
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Salz, Rich
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alexandre Petrescu
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Brian E Carpenter
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alissa Cooper
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Alissa Cooper
- Re: [Ietf-and-github] Alvaro Retana's Discuss on … Eric Vyncke (evyncke)