IETF Logo Mail Archive

Re: [Ietf-and-github] Propose changing draft-ietf-git-using-github from BCP to Informational

Christopher Wood <caw@heapingbits.net> Fri, 20 March 2020 14:36 UTC

Return-Path: <caw@heapingbits.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 160DB3A09F8; Fri, 20 Mar 2020 07:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 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, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=heapingbits.net header.b=plcsjbtI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QJl5g4xc
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 KUSs9vtyFE9O; Fri, 20 Mar 2020 07:36:49 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E45A3A0F17; Fri, 20 Mar 2020 07:34:34 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A35765C00EA; Fri, 20 Mar 2020 10:34:33 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute1.internal (MEProxy); Fri, 20 Mar 2020 10:34:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm3; bh=Py 8cArvAKAD3cuHEeRBstDyEQW5qKaHFUAaPHNr0Q7c=; b=plcsjbtIev8hhaNJDa s9pK16r47rpH9XH498ehlI1z3vYw8XpY66zTjhKwpgZ1/NYTe3fzF6Ne9hB8UvBG YGz21Rzsf7hmEgc6+6W7uc7cWQfuSoNsf2usPnyJWQBGIxJlxmSf6G0gbDd3V/6d T1VyhQB+HcYtoanvO9Ai2IE+6Kf9RJBwRM7KBjD6d13Idc7TFFHsgg+hqJd5Ufud 9TFYVlEkknAw/x3dDhoJR+Wv11xMtgszGopEVYZp/yIMeXrpRPv0mNaH4OaHltYD /+3I6247DRWsWC9bepzkHaaXR3nYgmRKqXaO7gduVf8DV+87Ik7pm3188TZPbcqN YE+w==
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=Py8cArvAKAD3cuHEeRBstDyEQW5qKaHFUAaPHNr0Q 7c=; b=QJl5g4xcg7auNoA47zTYfz34oTPZec0QoJT7yuhNrV9+wzQtaZo1vgOYG exN4KN4YO4kFShQzlMZO7aQul0O+kFdY0eH849XIJaw3oEMLvx2Cmhew6vwiYwHW yS9VecXTYg6gmuuOfAYH/ftsu48JtLQ2EYWPbfvDebrDFVcXSk943bGPeuwBpLWX PGFZTTDgzHPDV+m8ExQ4/c9sSHgcIbsB0LYGuTOK6n1xoc6PGhY62K/ov3tuVTwn rQbb1B5Qk2PO1FHtGX2ISOeRHbjsJx5BYg57H0GM5u8oia9EJx+OyRLGXYBwAKPU ruws9LKSU72ZAObFjVa1+HzibgvYA==
X-ME-Sender: <xms:eNR0XnbQ0BYp__2og-Co1xNmUpkfkKbUoi2DumcIJM7M381ES3MyCA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudeguddgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfvehh rhhishhtohhphhgvrhcuhghoohgufdcuoegtrgifsehhvggrphhinhhgsghithhsrdhnvg htqeenucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomheptggrfieshhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:eNR0XlLk3FvzRDWv2pMA6gZu26eBS5BdGzyCdBA0v5K3JsgmAfX3jA> <xmx:eNR0XphrJC81GazvvQshimwLQdEkCMhyWVcLso9c4k3YvkxTI1WTzQ> <xmx:eNR0Xn-lg2xcZz7yXTdiJl5jgw8vuKjlKTZ2D5CW2HlFU9IserkJVQ> <xmx:edR0XlY54UcPcQJrLB7hjFNX3sXVDjN16-bcc8R_K9qbJxihw7fsuw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 69CB73C00A1; Fri, 20 Mar 2020 10:34:32 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-1021-g152deaf-fmstable-20200319v1
Mime-Version: 1.0
Message-Id: <41b038cb-ca1f-43d7-975a-6efc72bb6e64@www.fastmail.com>
In-Reply-To: <5645321C-A644-4A93-B43F-D23F680DDD7A@mnot.net>
References: <bc332990-114f-b063-da16-556d2c8715e4@gmail.com> <5645321C-A644-4A93-B43F-D23F680DDD7A@mnot.net>
Date: Fri, 20 Mar 2020 07:34:12 -0700
From: Christopher Wood <caw@heapingbits.net>
To: Mark Nottingham <mnot@mnot.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf-and-github@ietf.org, "draft-ietf-git-using-github@ietf.org" <draft-ietf-git-using-github@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/xu4swrQQz5ieFgZ36-WcYCcDoqo>
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, 20 Mar 2020 14:37:00 -0000

Hearing little pushback, we're moving forward with this document as informational. We can always re-publish this as a BCP later on should that be deemed necessary.

Thanks,
Chris

On Fri, Mar 13, 2020, at 2:09 PM, Mark Nottingham wrote:
> 
> 
> 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
> 
>

v2.23.0 | Report a Bug | By Email