Re: [Ietf-and-github] Propose changing draft-ietf-git-using-github from BCP to Informational
Mark Nottingham <mnot@mnot.net> Fri, 13 March 2020 21:09 UTC
Return-Path: <mnot@mnot.net>
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 2B8DB3A1012; Fri, 13 Mar 2020 14:09:45 -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=mnot.net header.b=oGFhNzhV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=a3G760mG
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 gG-KK2XzZEmJ; Fri, 13 Mar 2020 14:09:43 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494533A100E; Fri, 13 Mar 2020 14:09:43 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1E57B22411; Fri, 13 Mar 2020 17:09:42 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 13 Mar 2020 17:09:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:content-transfer-encoding:from:mime-version:subject :date:message-id:references:cc:in-reply-to:to; s=fm2; bh=2Pxr0RF NJ62Wwrba5h1jTCpV8nVl/cz+esTjg8tklS8=; b=oGFhNzhVQmisKg0ErFfsJPW LGpUxofelmf18wKjhx49/K3Z2K3J/Aq2qIsbk2EA/fE6guf0UoZa/GkaKn4bJMgk 7lR1HX9wX3KNPTHqiK7OAQvHaaU30Mm7AATPoXXfbsImJZYeWr5oXeDfElZL7V0z nmnHv9PnN2QOmAMH1k+uFUgpnTqt8bofHf2tICpDy+PO9Rct+xb/YMSlZLE8Dc2I 9JscyLnB6HYxVwI1fI0+tJHh93Opw2INGk3VbI8EYwn2znPpqbXu5VyCzl2f2ltl 81sclkrHrBHQOLNDqwJZpXXXZXY4gWaEIeqbQUa207o+Q+ulKJ0C1cGrhCt/BAQ= =
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=2Pxr0RFNJ62Wwrba5h1jTCpV8nVl/cz+esTjg8tkl S8=; b=a3G760mGXRQ6SCSPkcRsj11yVSMeWI+s53CQNZsc1fQoYFuGpJyp+5LJR 38+oqIFVnhOzphhaw1nBf0kUJGBlx0oJxEeOXqPHUmu+bMcno7z9cC7aXxLSWSBP n2gZxDmGePdcnc67Uvh9aPT5ofpv/MU4OaWlhLDCFDFHgh3Vkhyj+007HWPAfFhF ZS5g8Ijx1d5qW10yhvGrJhYvPPsRn3LUzagGjgwoQHP+yEckDPFZlivgAnzT3HHD U+HS9SMMIfkeDy/iVIcFMdAFZtmBNL3QMk4m4l2JEXxC+uodTaOJd6183qIsxU6J EHa/wsoX/Vcvr2VuB3h6RSBs86C5A==
X-ME-Sender: <xms:lPZrXuqPvZwpZYSoiy6pG9_zm8NM7F7WFVc6h0c1lCk06aYjzwUVRQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvjedgudeghecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtgffhggfufffkfhgjvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepuddrudegfedrheekrddvgeejnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnh gvth
X-ME-Proxy: <xmx:lPZrXpXdnHPxa7HAvZVrD_IkMJAWB9HtUEcKUvXbgzaDV-UkX12sEQ> <xmx:lPZrXsSLpQC1F1zLrjSyvCR0IlW_QL_lWGOY8sy5lkiadkj_0cChYA> <xmx:lPZrXi7I9jTBw4HFpay6lWTUmvHTk0ao_6IA4k91K2E34CK3tiybtg> <xmx:lvZrXsURtKNzaUQa3ugZ5ECdsUkbE5bhCT90LmcexwYskF-q01IVEw>
Received: from [IPv6:2001:8004:cc3:43ce:912b:4894:eab2:df72] (unknown [1.143.58.247]) by mail.messagingengine.com (Postfix) with ESMTPA id 1FE4B306130A; Fri, 13 Mar 2020 17:09:40 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Mark Nottingham <mnot@mnot.net>
Mime-Version: 1.0 (1.0)
Date: Sat, 14 Mar 2020 08:09:36 +1100
Message-Id: <5645321C-A644-4A93-B43F-D23F680DDD7A@mnot.net>
References: <bc332990-114f-b063-da16-556d2c8715e4@gmail.com>
Cc: Christopher Wood <caw@heapingbits.net>, ietf-and-github@ietf.org, "draft-ietf-git-using-github@ietf.org" <draft-ietf-git-using-github@ietf.org>
In-Reply-To: <bc332990-114f-b063-da16-556d2c8715e4@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/Jh2XxtSh6IaOdb50oFoO8yeX4a4>
Subject: Re: [Ietf-and-github] Propose changing draft-ietf-git-using-github from BCP to Informational
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 21:09:45 -0000
Sent from my iPhone > On 14 Mar 2020, at 6:20 am, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > > Hi, > > I disagree that it is a minor or inconsequential change. It means that it is no longer a set of rules that a WG must follow if they choose to use GitHub. It just becomes some non-binding suggestions. That is what this group is chartered to produce. > > This has conseqences for the text, starting with the Abstract: > >> This document describes best practices ... > > needs to be something like > > This document describes suggested guidelines ... > > Then delete section 1.5 and lower-case all the RFC2119 keywords, to avoid confusion. That’s already started; see the editors’ copy. > More seriously, we would lose the normative value of this: > >> In addition to Working Group policies, notices on repositories MUST >> include citations for the IETF Note Well (https://www.ietf.org/about/ >> note-well/). > > which really should be mandatory. Also this: > >> All repositories for Working Group documents within the Working Group >> organization MUST be public. > > I haven't re-read the whole draft. There may be other things as well that are also important and not necessarily implied by RFC2418 already. So I do not agree to the change of proposed status. > > Regards > Brian Carpenter > >> On 14-Mar-20 02:48, Christopher Wood wrote: >> During last call, some folks suggested draft-ietf-git-using-github is better suited as an Informational rather than BCP document. This seems like a minor and inconsequential change, though I'd like to hear from the WG to understand if folks object. To that end, if you disagree with this change, can you please let us know why? >> >> Thanks! >> Chris >> >> _______________________________________________ >> Ietf-and-github mailing list >> Ietf-and-github@ietf.org >> https://www.ietf.org/mailman/listinfo/ietf-and-github >> > > _______________________________________________ > Ietf-and-github mailing list > Ietf-and-github@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-and-github
- [Ietf-and-github] Propose changing draft-ietf-git… Christopher Wood
- Re: [Ietf-and-github] Propose changing draft-ietf… Brian E Carpenter
- Re: [Ietf-and-github] Propose changing draft-ietf… Mark Nottingham
- Re: [Ietf-and-github] Propose changing draft-ietf… Christopher Wood
- Re: [Ietf-and-github] Propose changing draft-ietf… Warren Kumari